Differences between the JS-20/25 and the JS-50 Scanning Systems¶
The JS-50 product line was designed to improve on the user experience in mills and maximize technical capabilities. The differences between the JS-25 and JS-50 systems are described in the summary table below with further details following.
| Feature | JS-20 / JS-25 | JS-50 |
|---|---|---|
| Calibration | param.dat |
Pinchot API functions |
| Configuration | param.dat |
Pinchot API functions |
| Phasing | param.dat |
Pinchot API functions |
| IP Address Management | manually assigned | automatically assigned link-local |
| Power and Signal Cables | separate | single PoE cable |
| Encoder Inputs | input routed to all ScanHeads | ScanSync distributes over network |
| Scanning Modes | encoder, time, synchronization pulse | time only |
| Client Computer | API single-threaded | API multi-threaded |
| Ethernet Connection | 100Mbit | 1Gbit or 10Gbit |
| Software and Firmware Versioning | non-uniform | semantic |
| X6B/Z8 | two mainboards | one mainboard |
Calibration / Alignment¶
Calibration for the JS-50 is referred to as Alignment. Unlike JS-20/JS-25 ScanHeads, which used the param.dat file, the JS-50 models use function calls provided by the Pinchot API to define the alignment. Furthermore, these settings do not persist in memory on the ScanHead or the API, but rather are only applied while the user's application, using the Pinchot API, is connected to a given JS-50.
Configuration¶
A param.dat file is no longer used to configure ScanHeads. Instead, Configuration is done using functions provided by the Pinchot API that persist only while the user's application is connected to the JS-50. The configuration values passed into the functions can either be hard-coded or dynamically set through software or user input.
Phasing¶
With the JS-25 ScanHeads, a discrete phase was assigned in the param.dat file. Now that param.dat is not used in the JS-50 software, phasing is instead accomplished using the Phase Table functionality of the Pinchot API .
IP Address Management¶
Instead of needing to assigning IP addresses manually for each ScanHead, JS-50 ScanHeads make use of Zeroconf networking in order to automatically negotiate a unique link-local IP address on the network. Additionally, further changes were made in the JS-50 Pinchot API to remove the need for developers to know the IP address of ScanHeads; all that is needed to be known in the developer's software is the serial number of the JS-50.
Power and Signal Cables¶
For the JS-20/25, the power, encoder, and synchronization signals were provided over two separate cables. To speed up installation, ease cable management, and improve reliability, only a single X-Coded M12 to RJ45 ethernet cable is needed for a JS-50. This cable provides power to the ScanHead along with routing data to and from the ScanHead.
Encoder Inputs¶
With a JS-20/25 system, encoder inputs were distributed in parallel to all the ScanHeads in the system. With the JS-50, an encoder is connected to a single ScanSync module which then distributes the encoder location along with timing synchronization over Ethernet to all JS-50 scanners on the network.
More information can be found in the ScanSync article.
Scanning Modes¶
The JS-20/25 supported a number of synchronized scanning modes, based on encoder input, time, or synchronization pulses (EncoderSyncMode,PulseSyncMode,TimeSyncMode). The JS-50 only supports time synchronized scanning. After the ScanHeads have been added to the system and assigned phases in the Phase Table, function calls are used to start and stop scanning.
Client Computer¶
The JS-50 family of scanners is capable of generating scan data at density and rates exceeding that of the JS-20/25 family. To manage collecting all of this data, the Pinchot API makes heavy use of parallel processing and multithreading code. Due to the amount of data and computing requirements, it is recommended that the client computer used to manage scanning with the JS-50s be either a larger workstation or a server class machine with at least 8 cores.
Ethernet Connection¶
With the higher data rates and scan resolutions of the JS-50, an Ethernet connection speed greater than 100Mbit is required1. The JS-50 features a gigabit Ethernet connection and should be utilized at least with a gigabit Ethernet switch and a gigabit ethernet connection on the client computer. For high performance systems with high data rates and a large number of ScanHeads a 10Gbit network switch and 10Gbit network connection on the client computer should be used.
The Ethernet switch also needs to be IEEE 802.3 Power over Ethernet (PoE) capable in order supply power to the JS-50 ScanHeads.
Software and Firmware Versioning¶
Semantic versioning is used for versioning of the Pinchot API and the JS-50 firmware. This versioning scheme helps to simplify expectations regarding compatibility. Major revisions of the API and firmware are guaranteed to be interoperable with each other. Minor revisions will introduce changes that do not impact compatibility and do not require any changes to client code interfacing with the Pinchot API and JS-50. Patch revisions are generally bug fixes and other internal changes that are not visible to client code.
X6B / Z8¶
The JS-50 X6B features changes and improvements that distinguish it from the JS-25 X6B. Unlike the JS-25 X6B, which has two mainboards internal to the design (that require their own power and data connections), the JS-50 X6B has only one; eliminating the duplicated connections. The removal of the second mainboard also changes how the individual lasers are numbered. The laser numbers are printed on the housing of the X6B/Z8 models.
-
Technically, JS-50 can operate over a 100MBit connection. This will only work for very low data rates and is not recommended for production environment. ↩