amp

Anyway, it is fixed only when change IP to 192.168.x.x

I have the same problem for the graph with wrong date displayed on bottom left corner. What do you really mean by "Copy the file "pegrp32a.dll" over top of the file "pegrc32a.dll" in your DAQFactory folder." ?

Where? I do not see where the application shows two ports. "TOUCHPRO" is device name, isn't it? . "Ethernet" is not a port. It is connection name or the type of the communication for device called "TOUCHPRO". I only have one device called "TOUCHPRO" in the application. Can you tell me where I can see that had two connections configured? I don't even know how to set up two connections on one device. I can not find where second connection is in the application. So what and where can I delete? Can you please post a screenshot to advise where I need to delete or set IP to 0.0.0.0? But your second suggestion works, all I have to do is changing to IP address like 192.168.xx. It fixed all problems talked about before without changing anything else. But this leaves me a question of why. I still don't understand why it doesn't work with IP address like 200.200.200.190, because it appears in Brazil? I also have tried other software to connect to this device over Ethernet port using IP address 200.200.200.190 . Does not have any issue. I am not using internet. Both PC and device are not connected to internet network. For security reason, all our customers would not allow any automation device to connect to internet. But they do use some unusual IP addresses sometime.

See the attached. Read Channel.ctl

Only one device and only one channel used. The Ethernet port connecting to PC. Ethernet comms light lights up normal so PC DAQFactory page reads values from the device correctly even when this error keeps appearing. communication seems working fine but still getting this errors. And I noticed while error is popping out to the alert windows, it does slow down reading speed of the channel a little bit but the vale still updates from the device to screen. I will put details as below: Configuration: a. PC with windows 10, no other software except DAQFactory 17.1 installed, Only one device connected to PC via Ethernet port using Modbus TCP protocol. b. Remote device is a HMI that has Ethernet port for data communication, only one Modbus RTU sensor connected via RS485 port. No other device or software connect to this HMI. c. PC set as Ethernet client IP: x.x.x.200 sub: 255.255.255.0 d. Device set as Ethernet server IP: x.x.x.100 sub: 255.255.255.0 (DHCP is not used anywhere) Operation: 1. Connect Ethernet cable between PC. Then open the application runtime file Read Channel.ctl which the same one as uploaded here previously. 2. Watch screen page and command/alert windows. The variable reading shown on the screen becomes normal and value updated from the device connected. Error as mentioned keeps popping into the alert windows and never stops. Ethernet port lights looks normal as ordinary. 3. At this stage, if I disconnect the Ethernet cable for a few seconds and then reconnect. After a few seconds, the error to the alert window stops. And I can the just right click to clear the alert window. Now everything works good. It runs perfect as I expected. 4. But If I close the DF runtime, then open the file again, it will do the same as above again, errors keep coming up. I can only stop this error by disconnecting Ethernet cable and reconnect it. I can not see where else I could have mistake in setting up just one channel read to screen. Please advise.

100% sure . There is no any other device connected to DAQFactory PC. The PC is brand new with only windows 10 and DAQFactory development 17.1 installed and no any other software. It is purely used for this one device communication, one software and one connection only. Would it be possible to simulate cable disconnecting and reconnecting process while cable is actually connected? I mean kind of like windows device management that you can disable a device then rescan to find it to reconnect.

This is what the problem is now: While Ethernet cable being connected, open the DF runtime application to start, it will not establish Modbus TCP communication over Ethernet cable. It keeps getting this Modbus TCP timeout error all the time. It will only establish good communication by unplug then plug back the cable. I also tried to use Device.Mydevice.InitComm(), it does not help. I can not tell customer that every time after you open to run the application, cable must be unplugged then plugged in to make it work. Is there any code to use to initiate port in the same way as restarting the comm port when cable is plugged in? What else should I try to stop this timeout error when open the runtime application?

keeps reappearing. right click clears errors in the window instantly but then error appears again and again one after the other. Cable is always plugged in. The errors only stops if you unplug and plug back cable.

When I disconnect and reconnect Ethernet cable, it stops the error after short time when connection establish. But with the cable being connected and If I close exit the runtime and then reopen the application runtime, the error comes up again. and will never stop in command/alert windows, but after short while the values and displays are all correct from channel reading and value also updates. Indicating connection is working but error still does not stop. Error stop only if I disconnect and reconnect the cable. Can you please advise any code to stop this error when start the runtime while cable is connected? Thanks, I am learner of DaqFactory and really feel frustrated about this Ethernet communication.

I have a variable that is a 32 bits integer. I want to convert it to a 32 bits binary value and displayed on screen using To.Bit() expression on a variable display component. But it returns only showing maximum 20 bits like {(0,0,1,0........}} . I also tried using From.Bit(B00,B01,B02, ........, B31), it failed. I can only use From.Bit(B01,B02,B03, ......B19) to convert maximum 20 bits only. I read the manual section 4.12.10 on page 74-76 regarding the Bit() conversion expressions. It mentioned to convert 32 bits variable. So why my expression can only convert for 20 bits value? How to convert to or from 32 bits variable?

Expression CH1.time[0] changes the value displayed., "p-Modbustcp 0010: Timeout" Error still keeps coming to "command/alert" window. CH1 value on screen does update correctly. But this "p-Modbustcp 0010: Timeout" error can not be cleared. It does not make sense to me that showing this alert when data communication is working fine. How can I get rid of this alert?

I tested with only one channel and checked again. Still keeps getting this timeout errors in the Command/Alert windows. Modbus ID and reading registers are all correct. The value read from the HMI is matching with no problem at all. Please see the attached screenshot and my test application. Tried also timing to 0 to reset but it does not semm to work. Once I put timing back to 1, timeout error pops up again. I am only test on desk so the cable is quite short. Can't think what else could cause this error? Read Channels.ctl

Hi, I am also using DaqFactory to communicate with HMI via Modbus TCP. Communication works fine and receiving data from HMI correctly and can not find anything is wrong but the error message "P-ModbusTCP 0010: Timeout" keeps displaying in the Command/Alert window. I checked channel settings, tried different timeout values but does not change. I can not figure out why getting this P-ModbusTCP timeout error while communication seems all fine. Please advise.