No announcement yet.

Data Logging Possible???

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Just what's on the site. If you give me your values you want to log, I can create the log file that gets copied to the USB device and test it and email the file to you. Then you just copy the txt file to your thumb drive and it will start logging once you plug it in.


    • #17
      I stumbled across this today, which appears to do the same thing....

      A low cost PLC logger. Allows a customer to log data, downtime, reasons why machine is down, etc. to a MicroSD card in Excel format.


      • #18
        I had not seen that one. Looks good. Thanks pressgrove.


        • #19
          I've used the logger by interconnecting Automation for a few months now. It's great. You simply configure it with an easy to use tool plug it into the comm port on the plc and it logs to a micro sd card. Another nice feature is is that They placed how to videos onto the logger to help you configure it if needed. And you can't beat the price point!


          • #20
            The CLICK you have has 2EA. RS232 - RJ12 serial ports (Ports 1 & 2) and 1EA. terminal strip RS-485(port 3).

            The logger located at:

            PLC Logger/InterConnecting Automation Inc.

            Works on any of those CLICK PLC ports. It comes with a cable ready to plug into ports 1 & 2 - RJ12. it also powers up off of either of those ports so no external power supply is required.

            It is made to work with Automationdirect PLC's and Modbus PLC's and devices. The software tool used to configure it allows you to select the actual PLC addressing of the PLC that you are logging from when you use it to configure it.

            The software tool is on the logger when you receive it. There is no software to purchase, download or load on your pc. When you plug it into your pc using USB(cable included), it shows up as a mass storage device(hard drive) in your computer. The software tool is on the logger and runs over the USB cable. The tool allows you to select the model of PLC from Automationdirect, how you want to trigger the logging - be it continous, event(triggered from the PLC), or interval( 1 second, 4 seconds, 2hours and 3 seconds), and select up to 55 locations to log in the CLICK native format. This means if you want to log DF1, DS3, C11, X12, from your CLICK, you just use the pull down menus in the tool and select those addresses. You can also select when to create a new file be it day, week, month, or event or when you get X amount of rows in your CSV file. There is no Modbus etc. if you are logging from an Automationdirect PLC like CLICK. The tool allows you to configure the logger using the addresses of the Automationdirect PLC selected. It does do Modbus PLC's or devices but if you have a Automationdirect CLICK PLC, there is no need to know Modbus.

            If you go to:


            There are videos of how to configure it etc. The videos on that page are the actual how-to videos that are on the logger when you purchase it. There are videos specific to each model including the CLICK PLC and how to set it up to log from a CLICK. You can view them and see if you think it will work for you. The manual is on the page above also for you to review.

            You mentioned in your original post about code changes to feed the points to the device. In these types of situations, loggers, HMI's, SCADA software, it is a usually a master slave arrangement. The master(logger, HMI, SCADA, etc) polls the locations directly from the PLC communication ports and "usually" no code is necessary. We don't feed the points from the PLC to the master, the master requests the points directly and the slave(PLC) responds with the info the master requested.
            Last edited by icauto1; 02-21-2017, 03:38 PM.


            • #21
              I also had a hard time finding a reasonably priced logging program for Modbus RTU. So I made an application that I sell for a reasonable price on my website.