Scanner Troubleshooting

Scanner Troubleshooting

Scanners Stuck In the scanning state

• If scan system state changes while scanning (or settings changed), the scan system can be compromised, restarting the application and if necessary scanner cabinet (to reboot the heads) may resolve the issue.

Carriage Scanner Reference Issue

• If power was lost, or scanner cabinet turned off, encoder position is lost and Referencing is required.

• CleereOpti Operator screen may display the error, 

• The log is not in the correct position on the carriage or not drawn on the carriage at all, data is filtered due to being placed outside the range of the knees.

• May need to show the operator the location of the Reference Video, 

  • D:\Docs\Carriage Reference Process.mp4

  • Walk them through the process, and verify it is done correctly.

  • If this does not work, go through the process, and talk them through it to verify no procedural errors occur.

• Ensure the encoder is counting, in the correct direction(negative towards the saw from load end), and that our IPC value is correct. Also check that the encoder is not slipping, which may result in the log length being wrong.

Scanners not connected or Missing

Joescan JS-50

• Can the head be seen on the network?

  • Use Joescan Tools, open FirmwareUpdate.exe(C:\Users\USER\OneDrive\Cleereman Controls\JoeScan\JS-50\joescan-version\tools\FirmwareUpdater\FirmwareUpdate.exe) and check to see what heads it can see on the network.

    • Head\s not on network

      • Do heads have power? Check light on the front/back.

        • If all heads off, check scanner cabinet power feed to heads(POE Switch).

        • If single heads are off, check cables between Head and Scanner Cabinet.

    • Head/s is on network

      • Verify port setting for scanners, should be set to DHCP

      • Verify correct ports on PC being used, ScannerNet and PLCNet

Joescan JS-25

• Can the head be seen on the network?

  • Use Joescan Tools, open C:\Users\kyle\OneDrive\Cleereman Controls\JoeScan\JS-25\JSUpdate13854.exe) and check to see what heads it can see on the network.

    • Head\s not on network

      • Do heads have power? Check light on the front/back.

        • If all heads off, check scanner cabinet power

        • If single heads are off, check cables between Head and Scanner Cabinet.

    • Head/s is on network

      • Verify port setting for scanners, Disable DHCP, set IPv4 IP to 192.168.20.200

      • Verify correct ports on PC are used, ScannerNet

Optimizer PC Not Connected

• Check Network Connections

• Replace ethernet cables

• Check Local Security Policy

Bad Data Used in model

When dealing with bad model data, checking the RawScan view after a scan or using the data validation tool for the head model can help determine the location and cause of the bad data being added to the scan profiles.

• Specular Data

Specular data is caused by Direct or reflected light sources of a similar wavelength as the laser being expected by the cameras (mainly full spectrum sunlight but artificial lights can cause issues)

• • Scanner calibration issues, cannot find a corner due to bad data.

  • Scanned log looks “fuzzy” or has spikes creating a bad model, abnormal from a standard log.

  • Log is lengthened, sometimes significantly if a log does not cover all knees.

  • Data in front of the log towards the skids being added causing scanning errors.

  • Scanning never finishes, as the scanners always see data being gathered on the last active laser.

• Head Reporting False Data or missing data

  • Data points that are always reported, or data points being missed is likely a sign that your scanner cameras have been damaged. A “Flashed” camera that was welded in front of or exposed to extremely bright light may be damaged in this manner.

Delayed scanning/long scanning times

There are several issues that can cause this, from operator errors to scan system issues.

Delayed Scan starting, Long “Scan wait for start sync” times

• Usually falls in the 0-150ms range, if time are often higher than 200ms, there is an issue.

• Reboot the scan system, turn off/on Scanner Cabinet and restart the Optimizer PC

Long Scanning times, Scan does not complete until timeout

• Encoder issue? Is the travel distance needed to finish scan being reached?

• If inconsistent check for networking issues, may need to use the Wireshark application to monitor traffic.