FUDforum
My FUDforum

Home »  » DeviceMaster RTS, Pro and Serial Hub » RTS-8P question (Rookie application request)
RTS-8P question [message #1165] Tue, 06 August 2019 10:53 Go to next message
Fes1234 is currently offline  Fes1234
Messages: 8
Registered: August 2019
Member
Good Morning,

Working at a site with several RTS-8P's that need to be converted from using the windows comm port mode used by Foreseer to Socket mode which we need for the new Tridium BMS being installed. The RTS-8's fairly old but seem to be working fine and are running NS-Link 8.0 firmware

Questions:

1. I tried switching one port to socket mode for testing but the connection is refused. Can the RTS-8 support Comport and Socket modes at the same time?

Downloaded the devicemaster_1206_package.zip file but would like to have a better understand of the switch before I start downloading firmware.

Thanks

Ken
Re: RTS-8P question [message #1166 is a reply to message #1165] Tue, 06 August 2019 10:57 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Hi Ken,

To do Socket Mode, you'll need to go into the DeviceMaster's web page and go to Port Configuration.
Make sure the "Enable TCP Connection" is check marked.

Next, your application will need to connect to the DeviceMaster's IP Address and socket number.

By default, port 1 is 8000, port 2 is 8001 and so on. This is configurable on the Port Configuration page.

You can't use a Com Port communication and Socket communication to the same port at the same time.
You can mix them up with different ports each with either com or socket and you can use Com and Socket on the same port (Only if one is active at a time).

I hope that clears things up. If not, let me know.

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control

[Updated on: Tue, 06 August 2019 10:58]

Report message to a moderator

Re: RTS-8P question [message #1167 is a reply to message #1166] Tue, 06 August 2019 11:14 Go to previous messageGo to next message
Fes1234 is currently offline  Fes1234
Messages: 8
Registered: August 2019
Member
Hi Kurt,

Under TCP Configuration I checked the listen mode only since the connection is initiated from the remote device. Reading the docs it sounded like checking TCP enable would make the RTS connect to my controller using the IP and to/from ports under the configuration.

Re: RTS-8P question [message #1168 is a reply to message #1167] Tue, 06 August 2019 11:17 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Hi Ken,

It can be a little more user friendly. You will need to check mark the Enable in order to connect to the port.
The rest of the fields should be at the defaults. They are used for virtual serial tunneling.

In short, Listen and Enable must be check marked.

Thanks,
Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: RTS-8P question [message #1169 is a reply to message #1168] Tue, 06 August 2019 11:48 Go to previous messageGo to next message
Fes1234 is currently offline  Fes1234
Messages: 8
Registered: August 2019
Member
Kurt,

Enabled the TCP connection, rebooted the RTS-8 and my connection request is still refused.

Both the Windows Comm Server, my new device, and the RTS-8 are all connected to the same switch so confident this is not a network issue.
Re: RTS-8P question [message #1170 is a reply to message #1169] Tue, 06 August 2019 11:59 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Hi Ken,

Make sure there isn't anything accessing the port. If you go into the Port Overview via web page, you'll see either 'open' or a blank depending if there is something connected.
Try another port with your application, port 2 for instance.

If you still have an issue, email me your contact info and I will call you and see what's going on.

Kurt






Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: RTS-8P question [message #1171 is a reply to message #1170] Tue, 06 August 2019 12:55 Go to previous messageGo to next message
Fes1234 is currently offline  Fes1234
Messages: 8
Registered: August 2019
Member
Looking at the Windows Server setup I see all 8 ports are configured even though port 5 is not used and is the port I am using to test. Don't see a way to disable it but pretty sure Foreseer is not trying to open it.
Re: RTS-8P question [message #1172 is a reply to message #1171] Tue, 06 August 2019 12:58 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Hi Ken,

It would be good if I can call you, would that be possible?
I have your number from a previous email

Kurt



Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: RTS-8P question [message #1173 is a reply to message #1172] Tue, 06 August 2019 13:36 Go to previous messageGo to next message
Fes1234 is currently offline  Fes1234
Messages: 8
Registered: August 2019
Member
Looking at the Windows Device Manager under Serial Ports, I see Comm49 (Port 5 on the RTS) is enabled and looks ok. Should I disable the port or will that mess up the NLink driver?
Re: RTS-8P question [message #1174 is a reply to message #1172] Tue, 06 August 2019 16:02 Go to previous messageGo to next message
Fes1234 is currently offline  Fes1234
Messages: 8
Registered: August 2019
Member
Connecting with my socket driver is interesting

S-TcpAccept4 TCP Port 8004 ready for connection
SS-TcpAccept4 incoming socket connection from 10.100.14.71
SS-TcpAccept4 serial port 4 connected to IP: 10.100.14.71 TCP Port: 65421 This should be 8004 ???
SS-TcpRx4 semaphore received, socket open
3220: idle=3740 0000 0000 Indicates port is open
SS-TcpRx4 connection closed
SS-TcpRx4 waiting on semaphore
SS-TcpTx4 closing socket

This keeps repeating as driver tries to reconnect
Re: RTS-8P question [message #1175 is a reply to message #1174] Tue, 06 August 2019 16:30 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User

Hi Ken,

Port 65421 is a non reserved port on the other side of the socket connection. That is normal.

The 0000 0000 indicates all 8 ports are in use.

Are you connecting to a port that is already open? If so, it will fail.

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: RTS-8P question [message #1177 is a reply to message #1173] Thu, 08 August 2019 10:22 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Hi,

Please try and not use the Windows Device Manager, it can create issues if used incorrectly. To circumvent potential problems, we have a Comtrol Driver Management Console located in this location:

Start Menu -> Comtrol -> RocketPort -> Comtrol Driver Management Console.

You should deactivate ports within the console with less of a chance of having issues.

Thanks,
Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: RTS-8P question [message #1179 is a reply to message #1177] Thu, 08 August 2019 11:21 Go to previous messageGo to next message
Fes1234 is currently offline  Fes1234
Messages: 8
Registered: August 2019
Member


Don't see this under Comtrol menu:

Start Menu -> Comtrol -> RocketPort -> Comtrol Driver Management Console.

This is what I have:

Start Menu -> Comtrol -> DeviceMaster -> Driver Installation Wizard

Fairly certain the RTS is working. Looks like our driver is shutting down the port because its not getting the proper response from the device.

Is there a way to capture the serial data on a port?

Thanks
Re: RTS-8P question [message #1180 is a reply to message #1179] Thu, 08 August 2019 12:01 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User

There is a way to monitor serial port data.
Please see this document here:
http://downloads.comtrol.com/contribs/devicemaster/help_file s/tracing/monitor_serial_data_in_devicemaster_using_putty_to _log_file.pdf

What driver version and firmware version are you running?

Thanks,
Kurt


Fes1234 wrote on Thu, 08 August 2019 11:21


Don't see this under Comtrol menu:

Start Menu -> Comtrol -> RocketPort -> Comtrol Driver Management Console.

This is what I have:

Start Menu -> Comtrol -> DeviceMaster -> Driver Installation Wizard

Fairly certain the RTS is working. Looks like our driver is shutting down the port because its not getting the proper response from the device.

Is there a way to capture the serial data on a port?

Thanks



Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: RTS-8P question [message #1181 is a reply to message #1180] Thu, 08 August 2019 12:37 Go to previous message
Fes1234 is currently offline  Fes1234
Messages: 8
Registered: August 2019
Member
Only software/firmware version is NS-Link 8.0. Equipment was installed around 2011.
Previous Topic: Connecting to 1-port DeviceMaster RTS When IP Address Unknown
Next Topic: Byte count acknowledgement lag
Goto Forum:
  


Current Time: Sun May 16 04:20:14 CDT 2021

Total time taken to generate the page: 0.01246 seconds