Good evening everyone, new member looking for some information. I've scoured the depths of google and found zero answers. So here I am.
Here’s the short of it. I recently repowered my small cape horn with a 17’ df140a, it came with the c10 gauge and all connections, after installation everything has been running smooth until a dead short blew my 12v main fuse. Since that quick fix the c10 starts its boot sequence with a chirp then boots into a screen that simply says testing 1.2.3 as if its calibrating the display, if i then hold the “ok” button im taken to a screen with rows of options, everything from sound tests, button tests, ect. I can only assume this is the c10’s BIOS screen for set up and technical troubleshooting.
In the list of options, there is a “normal boot” choice, that takes me to the initial set up screen im used to seeing, and everything would seam to be fine from there. Unfortunately as soon as it turn off my battery switch this nightmare resets.
my question is, has anyone been into the BIOS of this device and knows what triggered it, and would the fix be a simple fresh firmware install or am I looking at needing a new gauge.
any help would be greatly appreciated.
Here’s the short of it. I recently repowered my small cape horn with a 17’ df140a, it came with the c10 gauge and all connections, after installation everything has been running smooth until a dead short blew my 12v main fuse. Since that quick fix the c10 starts its boot sequence with a chirp then boots into a screen that simply says testing 1.2.3 as if its calibrating the display, if i then hold the “ok” button im taken to a screen with rows of options, everything from sound tests, button tests, ect. I can only assume this is the c10’s BIOS screen for set up and technical troubleshooting.
In the list of options, there is a “normal boot” choice, that takes me to the initial set up screen im used to seeing, and everything would seam to be fine from there. Unfortunately as soon as it turn off my battery switch this nightmare resets.
my question is, has anyone been into the BIOS of this device and knows what triggered it, and would the fix be a simple fresh firmware install or am I looking at needing a new gauge.
any help would be greatly appreciated.
Comment