gomsun2 / python-astm Goto Github PK

See attachment for protocol definition.

Instead of sending one record per message, there should be option to send all 
session records within single message to reduce communication overhead for 
large amount of transfer data.

See attachment for protocol definition.

While astm.codec supports split message to chunks, astm.Client lacks of this 
feature.

See attachment for protocol definition.

Add serial support via PySerial ( http://pypi.python.org/pypi/pyserial ) 
project.

See attachment for protocol description.

codec.encode() takes unicode input and returns unicode output with checksum 
value that depends on message bytes. After that result data get encoded by 
specified in constants encoding, making bounded checksum completely wrong. Epic 
fail (:

See attachment for protocol definition.

Hello,

My issue is not all that big, I am new to python programming and I have been 
assigned the task of retrieving data from a Roche PSM device, decode it and 
send some of it (like patient data and results) to the database using Python. 
The problem I have is using the ASTM package to do this especially making the 
connection between the PSM device and client and getting the data I need. 

I tried reading the documentation in 
http://python-astm.readthedocs.org/en/latest/index.html but it does not clearly 
define how handle server and client connections and sending the data from the 
server to the client and analysing it. Is there sample code that clearly shows 
this and if there is can you please point me in the right direction. Please help

Your assistance would be very helpful in this endeavour.

Thank you.

See: http://bugs.python.org/issue1641 for the implementation.

The issue may be described with following algorithm:

0. C open new connection to S
1. C -- ENQ --> S
2. S -- ACK --> C
3. C -- H record --> S
4. S -- ACK --> C
5. C closes connection
# no matter no many time have passed between these steps
6. C open new connection to S
7. C -- ENQ --> S # S never replies there
8. C -- ENQ --> S # only after second ENQ message S returns to neutral state

The Omnilab client will hangs on socket.recv() call awaiting ACK or any other 
response from server on step 7, but server counting ENQ request as invalid for 
transfer state and returns to neutral state without any notification. This 
might be a problem of incorrect Omnilab LabOnline server configuration. 
However, this is also problem of python-astm since we have to retry ENQ request 
after specified timeout.

See attachment for protocol definition.

See attachment for protocol description.

Add ability to convert ASTM data to XML and vice versa. This feature was found 
in Myla protocol definition.

See attachment for protocol definition.

Client session doesn't awaits for ACK response after Terminator record sent. 
This is not critical, but makes debugging harder since for each session round 
there would be one extra ACK within input queue that automatically will be used 
for next sent message without waiting for real response.

The ASTM spec says:

The frame number is an ASCII digit from 0 to 7. Its purpose is to permit the 
receiver to distinguish between new and re-transmitted frames. This single 
digit is sent immediately after the STX character. The frame number begins with 
1 when the transfer phase is initialized and increments by 1 each time a new 
frame is transmitted
and acknowledged. After 7, the frame number returns to 0 and repeats the above 
sequence.

Actual behaviour allows to increment frame number beyond of number 9 leading to 
rejection for such messages.

See attachment for protocol description.

While it' may take a while we'd got implemented specifications for various 
hardwares, it would be nice to have some generic client/server/records that 
would adapt for income/outcome data without need to define any specification 
constraints.

See attachment for protocol description.