CONPROSYS use case : Collect PLC data and send to on premises server

Creating VTC

VTC file is attached in this post.

• X1:Y1
Set Wait component to generate 1 second interval.

• X1:Y2
Input data from Modbus register and set to TAG00~TAG15.
Set 0 to Fixed value (address) of Input Modbus property and address 0 is the same value that is set as Start Address of PLC configuration from WEB menu.
Set 16 to Fixed value (size) and this is the same value that is set as End Address(+1) of PLC configuration from WEB menu.

• X1:Y3
Logging component is used to write information to file. In this case, timestamp is written to a few columns of File00. DataTime(CDS) of Value property write timestamp as a format of "YYYYMMDD,HHMMSS,mmm".
We need to append Modbus data following timestamp so set Comma(,) for Append char property.

• X1~X8:Y4~Y5
According to the setting of Input Modbus component(X1:Y2), 16 data is stored to TAG00~TAG15. Each Logging components appends TAG data to File00.
Note: Last Logging component sets CR+LF instead of Comma(,) since TAG15 is the last data to write.

• X1:Y6
Determine component is used for conditional branching. LTAG(Local TAG)00 holds the cycle count of VTC and LTAG00>=59 means 60 lines of data are written in File00. If fomula is true, next sequence goes down(green arrow) and goes right(red arrow) if false.

• X1:Y7
File00 is ready to send so reset LTAG00 counter.

• X1:Y8
Send File00 to on premises server. Server URL is already specified from WEB menu.

• X2:Y8
You can delete File00 after sending file by Cloud component.
There is no problem even if it failed to send file because of some factors(cable disconnection, HTTP timeout, etc). In that case File00 is moved and stored in Re-send directory and CONPROSYS try to send this file again when next time of sending data call from VTC. Files in Re-send directory are renamed with timestamp so that overwriting does not occur.

• X1:Y5
In the middle of creating File00 so just increment LTAG00 counter.

Save and run the task, now processing starts.

Monitor Modbus data by Modbus Data View

CONPROSYS has Modbus Data View for monitoring Modbus Data.
Select Input Register and set Address to 2000HEX then you can monitor the current data from Modbus simulator.
Note: Input Register data from PLC is mapped starting from 2000HEX. 0~1999H is reserved for another data.

Monitor Modbus data by on premises server

On premises server has a simple web menu which can manage received data.
(Only Japanese language is supported but you can change by editing PHP file)

Access to 10.1.100 from your browser and enter serial number of CONPROSYS then all of transferred data is displayed.



Raw csv data is transferred to C:\Apache22\htdocs\tmp.

Create HMI for monitoring data by trend graph

HMI file is attached in this post.

How to use trend graph is very easy. Just drag & drop Trend component on the campus and assign signal source on property page.
1 trend graph supports up to 8 channels of input signal.