Error "START_FAIL" also DIV0 8011E966 on C1212 & E888 Setup
Posted: Mon Jun 03, 2024 4:02 am
Hi all,
I just performed a minor update to a TC sensor setting (connected to E888) in dash manager Post update, dash manager is now a) failing to connect, and b) displaying an error message on the display itself. The display is on a test bench with only power and Can1 connection to an E888. Power cycling the display does not change behavior, however if I remove the E888 (or disconnect CAN) then power cycle the display operation resumes as expected.
Failure to connect message:
The device has stopped operating due to an internal error. You should contact your MoTeC dealer for advice. Please quote the error code given below. "Halt Error Code: START_FAIL".
Dash error message (across top of screen in white font red background):
"DIV0 8011E966.
I'll be reaching out to my dealer when they come online later today, but in the interim if you have any insights you can share as to what may be going on I'd appreciate it. I'm also a little interested / concerned as to how it could have caused the setup to get into this state in the first place.
Thanks in advance,
Ben
I just performed a minor update to a TC sensor setting (connected to E888) in dash manager Post update, dash manager is now a) failing to connect, and b) displaying an error message on the display itself. The display is on a test bench with only power and Can1 connection to an E888. Power cycling the display does not change behavior, however if I remove the E888 (or disconnect CAN) then power cycle the display operation resumes as expected.
Failure to connect message:
The device has stopped operating due to an internal error. You should contact your MoTeC dealer for advice. Please quote the error code given below. "Halt Error Code: START_FAIL".
Dash error message (across top of screen in white font red background):
"DIV0 8011E966.
I'll be reaching out to my dealer when they come online later today, but in the interim if you have any insights you can share as to what may be going on I'd appreciate it. I'm also a little interested / concerned as to how it could have caused the setup to get into this state in the first place.
Thanks in advance,
Ben