neoVI FIRE & The device settings could not be read

[tysonite]

The below error sometimes happens with neoVI FIRE device. Not sure about the consequences of it. This happens on both master and checksum-failure-logging branches. However, most of the times, on checksum-failure-logging branch, interfaces didn't come up.

Jan 30 07:41:24 ptc_lab_collab3_node15 icsscand[30310]: The libicsneo SocketCAN Usermode Daemon
Jan 30 07:41:24 ptc_lab_collab3_node15 icsscand[30310]: Copyright Intrepid Control Systems, Inc. 2019
Jan 30 07:41:24 ptc_lab_collab3_node15 icsscand[30310]: Daemon v2.0.2 HEAD
Jan 30 07:41:24 ptc_lab_collab3_node15 icsscand[30310]: libicsneo v0.1.2 HEAD @
Jan 30 07:41:24 ptc_lab_collab3_node15 icsscand[30310]: Driver v2.0.4
Jan 30 07:41:24 ptc_lab_collab3_node15 icsscand[30310]: Waiting for connections...
Jan 30 07:41:30 ptc_lab_collab3_node15 icsscand[30310]: Creating network interface hscan_61777
Jan 30 07:41:30 ptc_lab_collab3_node15 icsscand[30310]: Created network interface hscan_61777
Jan 30 07:41:30 ptc_lab_collab3_node15 icsscand[30310]: Creating network interface mscan_61777
Jan 30 07:41:30 ptc_lab_collab3_node15 icsscand[30310]: Created network interface mscan_61777
Jan 30 07:41:30 ptc_lab_collab3_node15 icsscand[30310]: Creating network interface hscan2_61777
Jan 30 07:41:30 ptc_lab_collab3_node15 icsscand[30310]: Created network interface hscan2_61777
Jan 30 07:41:30 ptc_lab_collab3_node15 icsscand[30310]: Creating network interface hscan3_61777
Jan 30 07:41:30 ptc_lab_collab3_node15 icsscand[30310]: Created network interface hscan3_61777
Jan 30 07:41:30 ptc_lab_collab3_node15 icsscand[30310]: neoVI FIRE 61777 connected
Jan 30 07:41:31 ptc_lab_collab3_node15 icsscand[30310]: neoVI FIRE 61777 Error: The device settings could not be read.

Right after error above, restart of icsscand is succesful.

Jan 30 07:41:59 ptc_lab_collab3_node15 icsscand[30476]: The libicsneo SocketCAN Usermode Daemon
Jan 30 07:41:59 ptc_lab_collab3_node15 icsscand[30476]: Copyright Intrepid Control Systems, Inc. 2019
Jan 30 07:41:59 ptc_lab_collab3_node15 icsscand[30476]: Daemon v2.0.2 HEAD
Jan 30 07:41:59 ptc_lab_collab3_node15 icsscand[30476]: libicsneo v0.1.2 HEAD @
Jan 30 07:41:59 ptc_lab_collab3_node15 icsscand[30476]: Driver v2.0.4
Jan 30 07:42:00 ptc_lab_collab3_node15 icsscand[30476]: Waiting for connections...

neoVI FIRE runs latest firmware.

[hollinsky-intrepid]

The device settings could not be read.

This error will have no consequences for SocketCAN as the SocketCAN driver currently does not interact with the device settings. It's still something we will need to fix, of course.

However, most of the times, on checksum-failure-logging branch, interfaces didn't come up.

When you say this, do you mean no can0,can1,can2 interfaces are created? Or that they can't be started?

[tysonite]

I mean can0, can1, ... interfaces are not created. The error may look like that on checksum-failure-logging branch:

Feb 03 05:51:04 ptc_lab_collab3_node15 icsscand[1134]: Daemon v2.0.2 checksum-failure-logging
Feb 03 05:51:04 ptc_lab_collab3_node15 icsscand[1134]: libicsneo v0.2.0 HEAD @
Feb 03 05:51:04 ptc_lab_collab3_node15 icsscand[1134]: Driver v2.0.4
Feb 03 05:51:04 ptc_lab_collab3_node15 icsscand[1134]: Waiting for connections...
Feb 03 05:51:04 ptc_lab_collab3_node15 icsscand[1134]: neoVI FIRE 61777 failed to connect. Will keep trying...
Feb 03 05:51:04 ptc_lab_collab3_node15 icsscand[1134]: neoVI FIRE 61777 Error: The device is currently open.
Feb 03 05:51:06 ptc_lab_collab3_node15 icsscand[1134]: Discarding byte 00
Feb 03 05:51:06 ptc_lab_collab3_node15 icsscand[1134]: Discarding byte 00
Feb 03 05:51:06 ptc_lab_collab3_node15 icsscand[1134]: Discarding byte 00
Feb 03 05:51:06 ptc_lab_collab3_node15 icsscand[1134]: Discarding byte 00