...
Conveyers are required to communicate with OMICS Rx-Universe via the OMA device interface. The conveyer will initiate an Initialization session with OMICS to establish a connection. Once the communication is established, the conveyer will request what job and decision point it needs information for, it will pass the OMICS Rx-Universe tray or Job number and a 2 digit decision point to the OMA process, OMICS Rx-Universe will take this information and find the correct job, and then the decision point request will be prefixed with the “#” to get the correct decision point station record, the OMA process will then analyze the conveyer rules for this decision point and return either a 0 or 1 back to the conveyer, based on the settings of the conveyer rules and the job being requested.
The labels used are user-defined labels _DP and _DECISION.
_DP is the decision point identifier (each decision point must be separately identified on the conveyor system) and corresponds to the job track station in Rx-Universe. For example, the first decision point on the conveyor system would be 01, and identified by _DP=01, corresponding to job track station "#01" in Rx-Universe.
_DECISION indicates whether the tray should be diverted or not - _DECISION=1 means don't divert the tray, _DECISION=2 means divert the tray. A special setting of _DECISION=99 means Rx-Universe could not find the job requested (bad code).
A sample communication session might look as follows; the conveyor has previously initialized with Rx-Universe and received a packet ID of 1234; the conveyor is requesting whether to divert job 6789 for decision point 5. Rx-Universe responds with a confirmation the tray should be diverted.
Conveyor Request
<fs>REQ=1234<cr><lf>
JOB=6789<cr><lf>
_DP=05<cr><lf>
_DECISION=0<cr><lf>
<rs><gs>
Rx-Universe Response
<ack>
<fs>ANS=1234<cr><lf>
JOB=6789<cr><lf>
_DP=05<cr><lf>
_DECISION=2<cr><lf>
<rs><gs>
Conveyor response
<ack>
Setting up the User defined job flow labels
...