Overview
Each Nucleo block has a 2D barcode which uniquely identifies the block. Nucleo blocks are designed to be used more than once, and Rx-Universe will track each block, including the physical characteristics of the block (how many times it has been used, if it has been decentered, if it has been cribbed, etc.), and will work with the SatisLoh equipment to identify when blocks can no longer be used.
The SatisLoh equipment uses two different interface protocols with the re-use logic; the device communication is done using VCA, but the re-use logic is done using LDCS. Since both protocols are carried over TCP/IP, each protocol must use a different port, which requires two device sessions to be running on the Rx-Universe side. In addition, while the VCA protocol uses a defined port, 33512, for communication, no such standard exists for LDCS, so the port is configurable on both the equipment side and in Rx-Universe.
The sequence of communication between the Nucleo blocker and Rx-Universe is:
1) Rx-Universe will select the block base/diameter to use and print it on the work ticket.
2) The operator either selects blocks and places them in the tray, or the Nucleo will select blocks from the internal carousel.
3) The Nucleo requests job information from Rx-Universe using a standard VCA request.
4) The Nucleo scans the barcode on the block, and sends the block ID to Rx-Universe using LDCS, command 1100. Rx-Universe responds with data on the block, if it has been previously used, or with an identifier that this is a new block. It also sets the _BLKRU label to "1" if the block can be re-used, or "0" if it cannot be re-used. If the block cannot be re-used, the appropriate message is displayed on the blocker.
5) If the block is usable, the blocker then sends an LDCS command 1101, which identifies the job and eye being used for the blockpiece, allowing Rx-Universe to link the blockpiece to the job.
5) After blocking, the blocker sends information on the combined block and blank to Rx-Universe using standard VCA protocol.
Once blocked, the job will be generated; again, there are two communication sessions that take place between the generator and Rx-Universe; the standard device information is sent using VCA, and the blockpiece information needed for the re-use function is sent via LDCS.
1) Generator reads the tray, retrieves job information from Rx-Universe using a standard VCA packet.
2) After determining what will be done to the block (if it will be cribbed, etc.), the geometric data for the job is sent to Rx-Universe using LDCS.
After surfacing, if the block is removed using an automatic Nucleo de-blocker, the de-blocker will communicate with Rx-Universe using LDCS, to obtain the blockpiece information for the job being scanned, including _BLKRU indicating whether each block can be re-used or should be discarded.
Setting Up Rx-Universe for Re-Use
Under "Setup", "System Settings", on the "Devices" tab, the port number to be used for LDCS and the maximum number of times a Nucleo block can be re-used, must each be set. The default values are shown below:
Then, each of the re-use devices (blocker, generator, and de-blocker) must be set up with an LDCS interface in addition to the normal VCA interface.
Rx-Universe uses stations beginning with "T" to identify TCP/IP connections; similarly, it uses stations beginning with "L" to indicate an LDCS connection. This means that Rx-Universe will have TWO sessions running for each of the devices using re-use functionality - a VCA session using a workstation beginning with "T", and an LDCS session beginning with "L".
As an example, consider devices set up with the following IP addresses:
Rx-Universe Server - 192.168.168.1
Nucleo blocker - 192.168.168.100
Orbit Generator - 192.168.168.120
De-Blocker - 192.168.168.122
LDCS connections will use port 33520.
In Rx-Universe, 5 device sessions would be set up - 2 VCA connections for the Nucleo and Orbit, and 3 LDCS sessions, one for each of the blocker, generator and de-blocker, as follows:
The two Nucleo sessions would be set up as follows; note that each use the same IP address; the workstation ID is different; the T1 uses port 33512, the L1 uses port 33520. The L1 session should have the box "Use LDCS" checked.
The two Orbit sessions are, again, similar, using the same IP address, but the different workstation ID's indicate the two different protocols being used.
The de-blocker requires just an LDCS session for the re-use functionality, so only one session is needed for it:
With the device sessions set up, just make sure both the T1 and L1 device sessions are running on the device server (in this case, the computer with IP 192.168.168.1).
Setting Up Equipment Interfaces for Re-Use Server
Nucleo
The basic communication should be set up to use VCA (OMA), port 33512, and the IP of the Rx-Universe server (note, the "Host Upload" interface should also be set up this way):
On the setup screen under "Interfaces", set the blocker to use the re-use server:
Then, under "Interfaces" and then "block Reuse server interface", set up using protocol 29 with the IP address of the Rx-Universe server:
Orbit Generator
The generator will, similarly, be set up to use VCA protocol, port 33512, and the IP address of the Rx-Universe server:
Under "Manual mode", then "Machine Setup", then the "Workpiece reception" tab:
Then, in the interface setup screen, specify the reUse server protocol, the IP address of the Rx-Universe server, and the LDCS port number::
Re-Use Blocks in Rx-Universe
The data on the individual block pieces can be viewed in Rx-Universe, using the "Re-use blocks" option on the "Device" menu.
