Page History

...

In practice is has been shown that a well-designed threading model on the readout loop is reliably able to keep up even at high scan speeds if the processing of profiles is offloaded from the readout loop itself. The Developers Kit documentation has examples of how to de-couple acquisition and processing. 

My scanner shows up in JSConfig, but not in JSDiag. What's wrong?

Most likely, you have an IP address conflict: two devices on this subnet are assigned the same IP address. JSConfig will warn you if two scan heads have the same IP address, but it can not detect if another device or the control computer have an IP address assigned to a scan head. This can lead to unstable behavior, with heads disappearing randomly or connections dropping. JoeScan recommends isolating the problem. Make sure the scan head in question is powered up and has a network connection (see