If you (Yasemin) can log directly into the port the device is connected
to (you may have to turn off your IOC for that), if everything is
connected and set up correctly, you should be able to type a command
the device understands into it, and ^m and/or ^j. If you get the reply
you expect you're set up correct from the ethernet converter (or
terminal server) to the device. If you get no reply at all a breakout
box is your best way forward. If you get gibberish you can be pretty
sure that your cable is correct but one or more of the serial line
parameters isn't (as Emmanuel said).
Keep in mind that some devices are very configurable and some things
sometimes aren't quite as the manual says. E.g. we have 2 of the
same devices. You're supposed to be able to configure the parity,
yet one only speaks even parity and the other one only speaks odd.
Getting devices on serial lines to work sometimes is a bit like
banging your head against a wall.
Maren
On 08/19/13 14:47, Emmanuel Mayssat wrote:
Check the serial to ethernet converter. Is it RS232, RS422, or RS485?
(check physical switches on the converter)
Check the ethernet converter configuration to get the correct serial
parameters, baud rate, nb of stop bits, etc
Check the string terminator as well. The ethernet converter may append a
terminator which is not in the initial protocol.
If everything is configured correctly, changing interface from ethernet
to serial of a stream device should be seemless. (Of course, you changed
the physical connection, but also the asyn command from
drvAsynIPPortConfigure to drvAsynSerialPortConfigure, right?)
--
Emmanuel
------------------------------------------------------------------------
Date: Mon, 19 Aug 2013 16:30:07 +0300
Subject: Response Time
From: [email protected]
To: [email protected]
Hello,
I've been trying to connect to my machine by RS232.
I use streamDevice and Asyn Module.
When we send command "*IDN?", we expect to get "THERMO OK" from the
machine.
I try the same connection on TCP/IP. I used serial to ethernet converter
and communicated with the machine. No problem occured. But when I
eliminated the converter and directly connected to the PC on RS232 port,
I got the following error when I send the command.
I guess the problem is about response time. How can I configure the
response time? Or if it is not response time problem, how can I fix it?
ERROR:
"2013/08/19 16:23:15.340949 thermoConn IDN: No reply from device within
1000 ms"
- References:
- Response Time Yasemin Barutçu
- RE: Response Time Emmanuel Mayssat
- Navigate by Date:
- Prev:
RE: Response Time Emmanuel Mayssat
- Next:
Channel Acess Ganesh Jangir
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Response Time Emmanuel Mayssat
- Next:
asynPortDriver question Jörn Wüstenfeld
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·