CORE X3 crashing when booting with scanner plugged in via USB

[danielsimila]

Hi, 

When booting ctrlX CORE X3 (imaged with latest version: X3 Systemimage 1.20.12), with handheld scanner "Datalogic Touch TD1120 90 Lite" (Datalogic Touch TD1120 90 Lite USB-Kit Black (TD1120-BK-90K1) | Dustin.se) plugged in via the USB-C port, the CORE stucks in the boot process and does not come alive until a power-cycle is performed with the scanner unplugged. 

If the scanner is plugged in during the boot process (after the light-bar has started blinking in blue) or after the CORE has booted, no problematic thing happens. The scanner can be used emulating RS232 serial communication and read via a COM-port using an implemention like i.e. Barcode scanner with Node-RED/PLC via ctrlX CORE using USB port (boschrexroth.com).

Any thoughts on the booting issue? Has anybody seen the same thing before and can guide me towards a fix for this problem? I have a theory that somehow, the CORE reads something on the scanner and thinks that it can boot from it or apply some setup-file from it, but then crashes. But if this is the case, how to get around it? 

I am trying to gets hand on an identical scanner from the customer to be able to test myself. 
Thank you for any input!
// Daniel

[danielsimila]

Update:
I have now access to a scanner myself. The scanner crashes also my CORE when booting. In the logbook, I cannot find any messages about this. 

Any inputs on how to proceed with the troubleshooting? 

[Sgilk]

I would suggest getting an ssh assertion and following the journalctl logs during boot.

journalctl -f

[CodeShepherd]

In addition to @Sgilk you could please create a system report and share with us, as there are more information about system crashes.

[danielsimila]

Thanks @Sgilk, will try this. 

I attach a system report here. If you find something, please let me know @CodeShepherd. 

// Daniel

[CodeShepherd]

Does the ctrlX CORE boot up after USB device is removed or is the power cycle really necessary? In first case please create system report after bootup.

In the second case could you please set logbook to persistent via the web UI of the ctrlX OS try to boot with USB devie plugged in, then power cycle and boot up without the device. Afterwards create the system report.

[danielsimila]

Hi, the latter case - power cycle nessecary. I attach the system report. 

With ssh I cannot follow the booting process as the network does not start. And if I try to access to old log using "journalctl --list-boots" / "journalctl --boot -1", no new log is created for the boot when it crashes. Unfortunatley. 

[CodeShepherd]

Thanks for the information we will have a look to this. 

[CodeShepherd · Accepted solution]

For everyone's information there is another topic with a similar problem "CtrlX and arduino startup issue".