Support Forums
Setting up Modbus Compatible Driver

I've downloaded and installed VTScada 12.2.26. Once I got the training simulator application running. I wanted to start following along instructions from the Student Workbook: VTScada Operations & Configuration Course Guide on setting up the port and driver. It tells me to set the IP to 127.0.0.1 and the port to 501. Once I added a digital (pump running) I was expecting to see the values for the port and MCD tags showing a 0. It was instead showing a 770 error and a -10,061. I've installed VTScadaLight on my personal laptop using my home network. I read somewhere else that I would have to setup a server through thin client/server setup. I honestly do not know how to do so. The only luck I had with the tag browser showing a 0 value was by adding an authorization realm. I have had some luck in using OpenModSim as a modbus simulator to VTScada. I'm not entirely sure on how to properly use the app though, so still learning. What I'm wanting to do is try to set up an environment where I can learn VTScada more without using a licensed version of VTScada I use at work. I have also created an inbound rule that will open port 501. Is there any way to determine that the port is open to allow traffic ?

6a497d413ffd1
6a497d580eeaa
6a497d581ee14
6a497d5823753
6a497d5828039

I've downloaded and installed VTScada 12.2.26. Once I got the training simulator application running. I wanted to start following along instructions from the Student Workbook: VTScada Operations & Configuration Course Guide on setting up the port and driver. It tells me to set the IP to 127.0.0.1 and the port to 501. Once I added a digital (pump running) I was expecting to see the values for the port and MCD tags showing a 0. It was instead showing a 770 error and a -10,061. I've installed VTScadaLight on my personal laptop using my home network. I read somewhere else that I would have to setup a server through thin client/server setup. I honestly do not know how to do so. The only luck I had with the tag browser showing a 0 value was by adding an authorization realm. I have had some luck in using OpenModSim as a modbus simulator to VTScada. I'm not entirely sure on how to properly use the app though, so still learning. What I'm wanting to do is try to set up an environment where I can learn VTScada more without using a licensed version of VTScada I use at work. I have also created an inbound rule that will open port 501. Is there any way to determine that the port is open to allow traffic ? ![6a497d413ffd1](serve/attachment&path=6a497d413ffd1) ![6a497d580eeaa](serve/attachment&path=6a497d580eeaa) ![6a497d581ee14](serve/attachment&path=6a497d581ee14) ![6a497d5823753](serve/attachment&path=6a497d5823753) ![6a497d5828039](serve/attachment&path=6a497d5828039)

Electronics/Electrical Technician
Hilliard Fletcher Wastewater Treatment Plant

Hey Joseph,

No thin client connection required. Be sure that you are not setting up the connection inside the simulator app. You are meant to run the simulator as it's own app. If you look up the port in that app, you should see a TCP/IP port configured with no IP address and the port set to 502.

With that running, you create a NEW APPLICATION and follow along with the tutorial using the new application, rather than building on the simulator application. The port tag in the new application would be configured to the ip address 127.0.0.1 and the port to 502. This will cause the new application to connect to the simulator and will allow you to read Modbus addresses from the simulator from your new application.

Does that make sense. Note that you do not need to do anything with the thin client connection to get this working.

Hey Joseph, No thin client connection required. Be sure that you are not setting up the connection inside the simulator app. You are meant to run the simulator as it's own app. If you look up the port in that app, you should see a TCP/IP port configured with no IP address and the port set to 502. With that running, you create a NEW APPLICATION and follow along with the tutorial using the new application, rather than building on the simulator application. The port tag in the new application would be configured to the ip address 127.0.0.1 and the port to 502. This will cause the new application to connect to the simulator and will allow you to read Modbus addresses from the simulator from your new application. Does that make sense. Note that you do not need to do anything with the thin client connection to get this working.

Trihedral Engineering Ltd.

11
1
2
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft