pombreda / python-astm Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/python-astm
License: Other
Automatically exported from code.google.com/p/python-astm
License: Other
Python implementation of ASTM E1381/1394 data protocol. This project aims to solve three tasks: 1. Provide decoder ASTM data to Python objects and encode them back to valid ASTM messages. 2. Provide ability to create your own ASTM client and server applications followed by common specification routines. 3. Provide ready-to-use "drivers" for various ASTM-driven analysers, middlewares and other software or hardware solutions. Depending on your needs you may use this project in one of these ways. Currently, all communication routines are implemented for TCP/IP protocol driven by a bit improved standard asynclib. Read the docs for more info: http://python-astm.readthedocs.org
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 (:
Original issue reported on code.google.com by kxepal
on 28 Jan 2013 at 7:08
See attachment for protocol description.
Original issue reported on code.google.com by kxepal
on 22 Feb 2013 at 6:06
Attachments:
See attachment for protocol definition.
Original issue reported on code.google.com by kxepal
on 12 Dec 2012 at 9:29
Attachments:
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.
Original issue reported on code.google.com by kxepal
on 7 Feb 2013 at 8:33
See attachment for protocol definition.
Original issue reported on code.google.com by kxepal
on 12 Dec 2012 at 9:32
Attachments:
Add serial support via PySerial ( http://pypi.python.org/pypi/pyserial )
project.
Original issue reported on code.google.com by kxepal
on 10 Jan 2013 at 8:18
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.
Original issue reported on code.google.com by kxepal
on 2 Mar 2013 at 7:59
See attachment for protocol definition.
Original issue reported on code.google.com by kxepal
on 12 Dec 2012 at 9:47
Attachments:
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.
Original issue reported on code.google.com by [email protected]
on 20 Feb 2015 at 2:06
See: http://bugs.python.org/issue1641 for the implementation.
Original issue reported on code.google.com by kxepal
on 16 Jan 2013 at 10:57
See attachment for protocol definition.
Original issue reported on code.google.com by kxepal
on 12 Dec 2012 at 9:19
Attachments:
See attachment for protocol definition.
Original issue reported on code.google.com by kxepal
on 12 Dec 2012 at 9:27
Attachments:
See attachment for protocol description.
Original issue reported on code.google.com by kxepal
on 22 Feb 2013 at 6:02
Attachments:
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.
Original issue reported on code.google.com by kxepal
on 9 Jan 2013 at 3:11
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.
Original issue reported on code.google.com by kxepal
on 7 Feb 2013 at 8:38
See attachment for protocol description.
Original issue reported on code.google.com by kxepal
on 22 Feb 2013 at 6:03
Attachments:
See attachment for protocol description.
Original issue reported on code.google.com by kxepal
on 20 Feb 2013 at 7:07
Attachments:
See attachment for protocol definition.
Original issue reported on code.google.com by kxepal
on 12 Dec 2012 at 9:21
Attachments:
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.
Original issue reported on code.google.com by kxepal
on 7 Feb 2013 at 6:48
While astm.codec supports split message to chunks, astm.Client lacks of this
feature.
Original issue reported on code.google.com by kxepal
on 7 Feb 2013 at 8:34
Add ability to convert ASTM data to XML and vice versa. This feature was found
in Myla protocol definition.
Original issue reported on code.google.com by kxepal
on 12 Dec 2012 at 9:56
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.