T3-oem wifi connection

Tstat10
1

HI Guys,

I have successfully written a program working fine on the T3-oem
But my next test is getting scada to communicate with the device as its a wifi version. I have the ip address and port as modbus tcp 502 register on the output to view register 7101 pulsing a 1 and 0 for now. But off the IP I am not getting a reading on my tag. I ping the device pings perfectly no loss.

over wifi I cant get the device to communicate is there any default connections to work with or troubleshooting I should do.

Thanks

Chris

2

I assume you have connected over RS485 and configured the DHCP and other IP settings there using the T3000 software, you could send a screen shot of what you have there if you’re having troubles.

Then disconnect the RS485 and scan again over Wifi using the T3000 software. If you are having troubles you can temporarily disable any extra connections in your network settings of the PC such as virtual machines, VPN’s and Bluetooth adapters if any.

THere are versions of the T3-OEM with no wifi, check around for a wifi module or ESP32 with the wifi connection. The on board antenna is not very powerful so get close to the router with the T3 device.

Check the lower left status line of T3000 which shows the communications health.

Send screen shots of communications parameters and communications health for any tests whcih are failing.

Only one active connection at a time to get started, so when testing wifi disconnect teh RS485 temporarily.

3

I have disconnected the rs485 makes no difference. The unit is working just fine on t3000 with the rs485 connected. I will make mention the leds dont pulse to show you transmission on the rx tx? they do work when I first plugin to the usb so leds work on the rs485dongle?. So I can get the values with t3000 and it works fine but in scada I have used two different scadas to see if it was my end and it was not. As both cannot get the values from the register 7103 which is the output/relay. with rs485 yes connection status is good.

4

I got it,

After I disconnected the rs485 I then decided to reboot and then off she went as it must of read the rs485 was disconnected in reboot.

But here is the next question how to I read from the rs485 say on a sensor and then use wifi will it not work again as the rs485 is connnected?

5

As I understand it, you can connect fine using T3000 over Wifi. The issue comes up when you are trying to communicate from the T3-OEM directly to your Scada. The tool to use for troubleshooting at this stage is wireshark. Connect over T3000, capture some packets and get an understanding of the data structure. Then do the same with communications between your scada and the T3 device.

You mentioned above that the LEDs were not operating as exepcted. These LEDs are a very useful tool in your troubleshooting. If the T3 device is sending out data on the RS485 you will see led activity. If it is receiving a packet for that particular ID, say your your T3 device is at Modbus RTU ID = 1, then the RX led will go on when there are packets going to RTU ID=1. It will not blink for packets destined for otther RTU ids on the same network segment.

Update: There arent any LEDS for the wifi connection so you’ll use T3000 and wireshark to dig into the Wifi connectivity between the T3 and your scada devices.