Experimental Physics and
Industrial Control System

"Mark Rivers" <[email protected]> · Wed, 28 Mar 2007 21:06:38 -0500

David,

"... queueRequest Priority 1 not lockholder...", 

The messages you are seeing are normal, they do not indicate an error.  I think we should change the messages so that they look less like errors.

Here is the output of a serial device that is working normally, with all asynTrace flags set to 1.

2007/03/28 19:54:24.184 serial1 addr -1 queueRequest priority 0 not lockHolder
2007/03/28 19:54:24.184 serial1 schedule queueRequest timeout
2007/03/28 19:54:24.184 serial1 callback
2007/03/28 19:54:24.184 13BMA:ip1_serial: asynCallbackProcess, state=3
2007/03/28 19:54:24.217 serial1 flush2007/03/28 19:54:24.267 serial1 flush
2007/03/28 19:54:24.300 13BMA:ip1_serial flush
2007/03/28 19:54:24.350 serial1 write.
2007/03/28 19:54:24.384 serial1 write 3 RD\r
2007/03/28 19:54:24.434 serial1 write RD\r
2007/03/28 19:54:24.467 13BMA:ip1_serial: nwrite=2, status=0, nawt=2, data=RD
2007/03/28 19:54:24.550 serial1 read.
2007/03/28 19:54:24.600 serial1 read 36 RD\023\n\r19 09:38 5400V 8.2E-5I H---23\n\r
2007/03/28 19:54:24.684 serial1 read RD\023\n\r19 09:38 5400V 8.2E-5I H---23\n\r
2007/03/28 19:54:24.767 serial1 read.
2007/03/28 19:54:24.867 serial1 read 1 \021
2007/03/28 19:54:24.867 serial1 read \021
2007/03/28 19:54:24.900 13BMA:ip1_serial: inlen=40, status=0, ninp=37, data=RD\023\n\r19 09:38 5400V 8.2E-5I H---23\n\r\021
2007/03/28 19:54:25.034 13BMA:ip1_serial: inlen=37, nbytesTransfered=37, ntranslate=47 

By the  way, you said you are working on a Modbus driver.  Is this serial, or  Modbus TCP?  I am just about to release a package for Modbus TCP that uses asyn for the TCP I/O, and asyyn device support.  I hope to release it by  thee end of the week.  I'l send a note to tech-talk when its ready.

Mark

________________________________

From: David Dudley [mailto:[email protected]]
Sent: Wed 3/28/2007 2:29 PM
To: [email protected]
Subject: ASYN Octet driver question

I'm trying to solve a problem with the ASYN Octet package in my Modbus
driver.  When I have tracing turned on, I get exceptions every time I
try to write or read something, that say "... queueRequest Priority 1
not lockholder...", and then "...queueRequest timeout...".
However, the requests still get processed (most of the time....).

Trying to track down what this "...not lockholder..." message is from.
I look through my code, and I don't see anything where I'm calling the
"asynManager->registerPort" routine, nor do I see anything that
references it.  Would that cause this problem?

David Dudley

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System