RE: No reply from device within 1000 ms

[Mark Rivers <rivers@cars.uchicago.edu>]

You can see what is happening with the communication with the following commands:

asynSetTraceIOMask serial1 0 2
asynSetTraceMask serial1 0 9

where you would replace serial1 with the name of the asyn port for your serial port.

You can also get a report on the driver with

asynReport 10 serial1

If the hardware setup is the same as with cutecom, then it is probably either the baud rate or the terminators.

Mark


-----Original Message-----
From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Martin L. Smith
Sent: Thursday, September 05, 2013 9:19 AM
To: tech-talk@aps.anl.gov
Subject: Re: No reply from device within 1000 ms

Yasemin,

That typically means that the device is not responding to your command, at least
not within the default timeout of 1000 ms. Are you using the same serial cable
as you did with cutecom and the same comm port parameters?

If you have a serial analyzer that you can put between the device and the cable
that would at least tell you if the device is getting the command.

Marty

On 09/05/13 08:18, Yasemin Barutçu wrote:
> Hello,
>
> I've been trying to connect to power supply by RS232. When I try the connection
> with cutecom everythings work fine. But after creating an epics application and
> send the "*IDN?" command I get following warning and can't read anything.
>
> 2013/09/05 16:15:56.265500 serial IDN: No reply from device within 1000 ms
>
> Thanks,
> Yasemin Barutçu