New in LIMS

« Back to Previous Page
Tags:
0
0

Please to read the entire article.

Marked as spam
Posted by Amel Benmesbah (Discussions: 1, Comments: 3)
Replied on February 11, 2019 10:19 am
95 views
0
Private comment

Hi Amel, we use Nodered to interface to clinical instruments. If you post links to the technical documentation on all the instruments you want to interface, I am sure we can share with you some code in Nodered that will help you.

Marked as spam
Posted by John Jones (Discussions: 368, Comments: 3065)
Replied on February 11, 2019 10:24 am
0
Private comment

Hi John,

Thank you for you answer. You willa find above the C111 manual link:

https://wetransfer.com/downloads/50afe2c9d332cf2bddc566504ef2ff9a20190212112417/fa79d81af34c739e5f370101da02011f20190212112417/a1f159

I don’t really understand in wich format the machines send their results in hexa ??
I’ve made a connection with an USB-DB9 cable, I’ve opened the port com and listened it, the machine sent me a little square !!!.

Thank you for your help.

Marked as spam
Posted by Amel Benmesbah (Discussions: 1, Comments: 3)
Replied on February 12, 2019 6:29 am
0
Private comment

I am sure we have a Nodered configuration that will talk to the c111. I will get Bob Walters to post a download link to download the ASTM flow for Nodered. That will be a great starting point for you.

In terms of physical connectivity, you will need something like this: https://www.amazon.com/gp/product/B00425S1H8/ref=ppx_yo_dt_b_asin_title_o09__o00_s01?ie=UTF8&psc=1

That would then be plugged into the instrument and to the computer that should be running Nodered: https://nodered.org/

The language for Nodered is 100% javascript.

Marked as spam
Posted by John Jones (Discussions: 368, Comments: 3065)
Replied on February 12, 2019 8:33 am
1
Private comment

My recommendation is to use a raspberry pi with the NOOBS OS. Nodered comes preinstalled. We use this for all of our interfaces and it works great.

Marked as spam
Posted by John Jones (Discussions: 368, Comments: 3065)
Replied on February 12, 2019 8:34 am
0
Private comment

I have the same adapter but I’ve never heard about Nodered until now, If I can have examples I’ll try to use it.

Marked as spam
Posted by Amel Benmesbah (Discussions: 1, Comments: 3)
Replied on February 12, 2019 8:44 am
0
Private comment

I think you will like Nodered as much as we have. It is very, very flexible and well supported. It was developed by IBM and it is free and Open Source. There are a lot of on-line education resources for it. We stopped using our own .net developed interface in favor of Nodered. Bob will post a link to some example astm flows that you can import into your own instance of nodered. Once you create your interface for the C111, please post it back here. We try to share everything between fellow developers.

Marked as spam
Posted by John Jones (Discussions: 368, Comments: 3065)
Replied on February 12, 2019 9:00 am
0
Private comment

Amel, reading through the interface documentation now. I think the issue you are seeing is the instrument is indeed transmitting Non-printable characters like ASCII 5 (ENQ). For investigation, there are serial port communications apps (like RealTerm) that will automatically convert those non-printable characters to “tokens” like [ENQ], [STX], {EOT], etc. If you are not familiar with them, here is an example like to ASCII codes: https://ascii.cl/control-characters.htm.

Marked as spam
Posted by Robert Walters (Discussions: 0, Comments: 4)
Replied on February 12, 2019 9:23 am

Bob, can you post a download link for a nodered flow that comes closest to what the C111 looks like. I think that will give Amel a bit of a head start working in Nodered.

(John Jones at February 14, 2019 1:07 pm)
0
Private comment

Hi Robert,

Thank you for your answer. I’ve downloaded the tool and I’ll try it tomorrow in the laboratory, I’ll also learn more about Nodered.

Marked as spam
Posted by Amel Benmesbah (Discussions: 1, Comments: 3)
Replied on February 13, 2019 5:02 am
0
Private comment

https://lablynx.scicloud.net/s/a7qLkjXwn5RmBbW

Amel,

Here is a link to an ASTM flow that we are using. This flow is a work-in-progress so you will probably find some things in here that are no longer used that I have not cleaned out yet.

Additionally what I am sharing here has been modified some to remove sensitive details. We use a proprietary web service to get and post data to the client’s database so you will see references to the web service that are not complete. Use this flow just as a way of getting ideas on how to build your flow. It is provided as-is but you are free to make use of anything you can learn from it.

This was built to run on a Linux system so the comm ports and folder references are uniquely different than what they would be for a MS Windows installation.

This instrument is a query based bi-directional instrument, so queries come in from the instrument, when the is received, the message is parsed and the GetOrders process is run and a response of orders is assembled and returned to the instrument.

Results take a slightly different path and are sent to the web service using the ExecSQL process. Both paths make use of a file-based queuing system that provides for orderly processing and capture of the data in files in case anything happens in which case the files can be re-run without having to re-process on the instrument.

Of course, in a bidirectional system like this with only one communication path, the possibility exists for contention where the instrument is trying to send another query while the host interface is trying to send orders from a previous query. Some instruments are more patient than others but if this does occur, the ASTM standard defines that the instrument’s communication always take priority over the “host” system. You will see references in the flow to “contention” handling.

Hope this helps get you started on Node-RED. I really like working with it.

Marked as spam
Posted by Robert Walters (Discussions: 0, Comments: 4)
Replied on February 14, 2019 1:55 pm
The post stripped some detail out… in the fourth paragraph, it should read … when the EOT is received.
(Robert Walters at February 14, 2019 1:57 pm)
« Back to Previous Page