Thanks Robert and Charlie for your input. To make a long story short, our lab folks bought some equipment but not the middleware that goes with it. The vendor claims that it’s possible to do an interface without the middleware. Middleware is $300K and management wants us to make our best effort. Here’s how the vendor says transactions will work. Haven’t been able to confirm due to lack of a workable client and limited availability of the equipment at the moment.
10:52:42 Sent to LIS :
10:52:42 Received from LIS:
10:52:42 Sent to LIS :
(Pipe delimited ASTM record here)
10:52:42 Received from LIS:
For our purposes, “LIS” is Cloverleaf.
As I said, I have been able to code a “basic-msg” in a PDL cloned from the mlp2_tcp.pdl code that reads and acks the one byte as a fixed length array. I can also code a “basic-msg” that reads and acks the variable length data record ending in . What I don’t know how to do is write a pdl that will try to match either one. So far I’ve only worked with the ” hci_pd_msg_style acknak” call found in mlp2_tcp.pdl. All of the examples of more complicatd PDL’s we have that were written by Cloverleaf folks are “async.” I haven’t spent the effort to dig deeply into the nuts and bolts of how they work without first exhausting what seemed like the far simpler model found in mlp2_tcp.pdl. I’ve read every scrap of documentation available in the Cloverleaf help file multiple times, but it’s sort of sparse and I’d appreciate any help you can offer with filling in the gaps.
Thanks again.
