4. Troubleshooting

4.1. Possible Problems and Solutions

Occasionally, a script can be built that may not function correctly with the device. Refer to the list below for potential issues and common fixes:

Problem: The script was pushed to the device, but does not seem to be running in Standalone mode

Solution: Make sure that the USB cable is unplugged from the neoOBD2-SIM when the device is ready to be used. If the USB is plugged in when the device is booted, the CoreMini script will not run. This is by design to prevent the device from loading any actively installed scripts.

Problem: Device LCD shows the Intrepid Control Systems logo, which blinks off and back on again. The device may seem unresponsive.

Solution: This is what’s referred to as a ‘boot loop.’ This means that a command somewhere in the file is causing the device to reset.

If the device is stuck in a boot loop, hold down the 1 and 4 buttons (the top two). Alternately, plug in USB. Powering up the device with these buttons pressed will purge the currently installed script. After the script is purged, the device should act normally again. Note, plugging in the USB only stops the script for that session; it does not purge the script. Boot loops need to be fixed in the function block code. This may require debug modifications and extensive troubleshooting.

If the device is still acting up after a script purge, hold down all 4 buttons and repower the device. This will send the device into bootloader, where it can be recovered by connecting to the device using neoVI Explorer.