18R Error Codes
|
|
Er3 (Error 3) Stuck ButtonA button is pressed while the module was powering on. Make sure that no buttons are being pressed or stuck during the boot-up process. Restart the device. |
|
|
Lo + BatIf any device has an operational P battery level of P3 or lower, the device will tell the controller the battery is low and report this information by displaying the word “Lo” and “bAt” followed by the battery value, device address, and device channel. For example, "Lo", "Bat", "P2", "A01", "C02". In firmware versions, 3.0. or lower, only the device channel will display and not the channel.
|
Low + AntIf any device has a signal above -75, the device will tell the controller the signal is low and report this information by displaying the word “Lo” and “Ant” followed by the signal value, device address, and device channel. For example, "Lo", "Ant", "-75", "A01", "C02". In firmware versions, 3.0. or lower, only the device channel will display and not the address. |
18R2 Error Codes
Er3 (Error 3) Stuck ButtonA button is pressed while the module was powering on. Make sure that no buttons are being pressed or stuck during the boot-up process. Restart the device. Firmware 5.1.4, 6.0.7, and higher support stuck button identification and bypass. |
|
Er4 (Error 4) Error Uploading Script FileYour script upload failed / you don’t have the word “end” on the last line of your script file or you have a non-COBRA .csv file on your USB drive. Please make sure your USB drive has no other .csv files on it and that the COBRA script you are trying to load has the word end on the last line of the script.
|
|
Er6 (Error 6) - Transceiver firmware does not match processor firmwareThe 18R2 has two internal chips that require firmware updates. The first is the transceiver and the second is the processor. When performing a firmware update on the 18R2, it's normal to see Er6 when you update the firmware on the transceiver first. At this point in time, you would proceed to the next step and load the cobra.s19 file to your USB drive, place it into the 18R2 while off, then hold the SYNC button and power on the 18R2 at the same time. This will spin the LEDs and go fully green and then power off when complete. Re-start your 18R2 and the firmware version should be correct. |
|
Er50 (Error 50) - Maximum addresses reached |
The maximum amount of unique module addresses is met. In 5.0 and lower, there is a 200 device address limit. Once you exceed A199, this error will display. To fix this, you will need to Force Unsync your 18R2 at which time the address counter will reset to A00 and you re-sync your devices.
*Er will display on the upper 7-segment display and the number 50 will show on the lower display. |
Lo + BatIf any device has an operational P battery level of P3 or lower, the device will tell the controller the battery is low and report this information by displaying the word “Lo” and “bAt” followed by the battery value, device address, and device channel. For example, "Lo", "Bat", "P2", "A01", "C02". In firmware versions, 3.0. or lower, only the device channel will display and not the address. |
|
Lo + AntIf any device has a signal below -75, the device will tell the controller the signal is low and report this information by displaying the word “Lo” and “Ant” followed by the signal value, device address, and device channel. For example, "Lo", "Ant", "-75", "A01", "C02". In firmware versions 3.0. or lower, only the device channel will display and not the channel. |
18M Error Codes
Er1 (Error 1) or Er2 (Error 2) Power voltage issueEr1 or Er2 can display for a variety of reasons. Please perform the following to resolve the issue. Voltage Mode - The module voltage mode may be incorrect. To change the voltage mode, press TEST and CH+ or TEST and CH- to set to the desired voltage mode. For 9V batteries, the desired mode is 9.0. For the standard COBRA LiPo battery, the desired mode is 14.8. For more information on the voltage mode, see What is voltage mode? 2P Battery Orientation / Contacts / Power - If you are using 9V batteries and are seeing a normal 1P value, but the 2P value is 0, first check the 9V battery orientation to ensure the 2P batteries are both facing in the correct direction. Make sure each battery contact is pressing firmly against the battery tabs. If you still see 2P0, replace the two 9V batteries to see if this resolves the issue. Bad Cue - While rare, it's possible a cue is bad. This will typically display only when a cue is wired and 2P0 will display when powering up. If you remove all wires and the error code goes away, you can wire the module cue by cue and power up each time to determine the defective cue. |
|
|
|
Er3 (Error 3) - Stuck keypadA button is pressed while the module was powering on. Make sure that no buttons are being pressed or stuck during the boot-up process. Restart the device. |
|
|
Er5 (Error 5) - Module firmware does not match controllerThe firmware of the module does not match the controller. When synced, the module firmware must match the 18R2 firmware. When powering on the 18M and 18R2, the firmware is the first piece of information to display. For example, 5.0.2. In rare cases, Er5 can display incorrectly when syncing an 18M to an 18R Controller (currently discontinued). If this occurs, re-sync the 18M, and this error should go away. For more information on firmware versions, see Firmware Figured Out. |
|
|
Er7 (Error 7) – Calibration errorThe calibration value is outside of the accepted range. Please contact us at help@cobrafiringsystems.com for assistance. |
36M & 72M Error Codes
Er1 (Error 1) or Er2 (Error 2) Power voltage issueEr1 or Er2 can display for a variety of reasons. Please perform the following to resolve the issue. Voltage Mode - The module voltage mode may be incorrect. To change the voltage mode, press TEST and CH+ or TEST and CH- to set to the desired voltage mode. For 9V batteries, the desired mode is 9.0. For the standard COBRA LiPo battery, the desired mode is 14.8. For more information on the voltage mode, see What is voltage mode? 2P Battery Orientation / Contacts / Power - If you are using 9V batteries and are seeing a normal 1P value, but the 2P value is 0, first check the 9V battery orientation to ensure the 2P batteries are both facing in the correct direction. Make sure each battery contact is pressing firmly against the battery tabs. If you still see 2P0, replace the two 9V batteries to see if this resolves the issue. Bad Cue - While rare, it's possible a cue is bad. This will typically display only when a cue is wired and 2P0 will display when powering up. If you remove all wires and the error code goes away, you can wire the module cue by cue and power up each time to determine the defective cue. |
|
|
|
Er3 (Error 3) - Stuck keypadA button is pressed while the module was powering on. Make sure that no buttons are being pressed or stuck during the boot-up process. Restart the device |
|
|
Er5 (Error 5) - Module firmware does not match controllerThe firmware of the module does not match the controller. When synced, the module firmware must match the 18R2 firmware. When powering on the 18M and 18R2, the firmware is the first piece of information to display. For example, 5.0.2. For more information on firmware versions, see Firmware Figured Out. |
Er6 (Error 6) – Update did not completeThe 36M / 72M has two internal chips that require a firmware update. The first is the transceiver and the second is the processor. When performing a firmware update on the module, it's normal to see Er6 when you update the firmware on the transceiver first. At this point in time, you would proceed to the next step and load the 90m.s19 file to your USB drive, place it into the module while off, then hold the SYNC button and power on the 36M/72M at the same time. This will have the module chase the LEDs after which they will go all green and then power off when complete. Re-start your module and the firmware version should be correct. For more please see How do I update the firmware on my equipment? |
Audio Box Error Codes
To determine your Audio Box error code, count the number of blinks of the power button LED. This is the error code number.
Er5 (Error 5) – Audio Box firmware does not match firmware on the remote |
The firmware of the Audio Box does not match the controller. When synced, the module firmware must match the 18R2 firmware. When powering on the 18R2, the firmware is the first piece of information to display. For example, 5.0.2. Unfortunately with the Audio Box, the firmware does not display when powered on. Therefore, to correct this you will need to update the Audio Box firmware to match the 18R2 firmware version. For more information on firmware versions, see Firmware Figured Out. |
Er6 (Error 6) – Audio Box firmware does not match firmware on the remote |
The Audio Box has two internal chips that require a firmware update. The first is the transceiver and the second is the processor. When performing a firmware update on the Audio Boix, it's normal to see Er6 when you update the firmware on the transceiver first. At this point in time, you would proceed to the next step and load the 90m.s19 file to your USB drive, place it into the module while off, then hold the SYNC button and power on the 36M/72M at the same time. This will have the AudioBox SYNC LED blink until complete. Re-start your device and the firmware version should be correct. For more please see How do I update the firmware on my equipment? |
Er7 (Error 7) – Battery or USB error
|
The unit is experiencing a low power or USB communication error. Please try new batteries or try a different USB drive including the COBRA certified USB drive. |
18R2 Script Errors
Script errors are displayed with an ER on the upper display and the code number on the lower display. For more information on scripting, see Scripting.
# |
Description |
Resolution |
| 1 |
cobra.csv script file not found or multiple .csv files detected on USB drive |
In firmware versions 5.0.5 and lower, make sure the script filename is cobra.csv. In addition, Microsoft Windows sometimes will show "cobra" as the filename as the file type is recognized as a CSV file and the extension is not shown. If you see “cobra.csv”, you may have the extension added twice and by changing the filename to “cobra”, this will resolve the issue. In firmware versions 5.1 and higher, make sure a there is a single csv script file on your USB drive as mulitple csv files are not supported today. With firmware 5.1 and higher COBRA supports a .csv script files with any filename. |
| 2 |
Error erasing script sector |
There is likely a memory failure on the 18R2 flash chip. Contact us at help@cobrafiringsystems.com for assistance. |
| 3 |
Maximum scripts reached. Currently, the limit is 100 |
Reduce the number of scripts in your file to less than 100. |
| 4 |
Script header row found with no events |
Remove the script row that contains no events or add events to the script. |
| 5 |
Events found with no script header row |
Remove the event row that contains no script header row or add a script header row above the events. |
| 6 |
Maximum events reached (limit 1,800) for a single script |
Reduce the number of events to less than 1,800. |
| 7 |
Invalid event line format (couldn't find three or more arguments, i.e. two commas) |
See the Example Script worksheet for the accepted values. |
| 8 |
Invalid event time format |
See the Example Script worksheet for the accepted values. |
| 9 |
Invalid event hour format |
See the Example Script worksheet for the accepted values. |
| 10 |
Invalid event minute format |
See the Example Script worksheet for the accepted values. |
| 11 |
Invalid event second format |
See the Example Script worksheet for the accepted values. |
| 12 |
Invalid event channel format |
See the Example Script worksheet for the accepted values. |
| 13 |
Invalid script header row return to channel format |
See the Example Script worksheet for more information in defining header rows. |
| 14 |
Script header row trigger channel or event channel out of range |
The script event channel must be a number no less than 0 or greater than 99. |
| 15 |
Script header row return channel out of range |
The script return channel must be a number no less than 0 or greater than 99. |
| 16 |
Invalid event cue format |
See the Example Script worksheet for more information on the accepted values. |
| 17 |
Event cue out of range |
The script event cue must be a number no less than 1 or greater than 18. |
| 18 |
Missing script header row trigger button |
See the Example Script worksheet for more information in defining header rows. |
| 19 |
Invalid script header row trigger button format |
See the Example Script worksheet for more information in defining header rows. |
| 20 |
Invalid script header row trigger confirmation button format |
See the Example Script worksheet for more information in defining header rows. |
| 21 |
Script event out of order |
The event occurs earlier than a previously defined event. All event rows in the file must be in the order of time. |
| 22 |
More than two overlapping channels in 0.4s |
You are attempting to fire more than 2 channels in a 0.4s time period. You will need to add some delay between these events to ensure you are not violating this requirement. This error is only applicable to firmware versions 2.1 or lower. If your system this on firmware 3.0 or higher and you are seeing this error that is because you have multiple scripts on one CSV. On firmware 5.1.X and higher this will display at 'not 22' For additional help please contact us at help@cobrafiringsystems.com. |
| 23 |
Invalid event row description |
The event row description contains too many characters (max 540) or commas (max 10). |
| 24 |
Too many columns in event row |
The event row contains too many columns (max 20). This is likely due to too many commas in your event description. |
| 25 |
Premature end of file |
The word “END” is missing in the script. Please insert the word “END” on the last line of the script. |
| 26 |
Audio Box file name too long |
Reduce the size of the Audio Box file name to 12 characters or less excluding the .mp3 extension. For example, 123456789.mp3. In firmware version 5.1 or higher, an audio filename of up to 45 characters, not including the .mp3 extension is supported. |
| 27 |
Audio Box filename bad characters |
Remove any symbols from the Audio Box file name. |
| 28 |
Maximum number of alternate events reached |
Reduce the number of alternate events to 18 or less. |
| 29 |
Invalid Disable Firing Argument |
Make sure the Disable Firing button is a cue 1-18. Also, make sure the Deadman, Alternate, and Disable firing arguments are different buttons. |
| 30 |
Invalid Alternate firing button argument |
Make sure the Alternate Firing button is a cue 1-18. Also, make sure the Deadman, Alternate, and Disable firing arguments are different buttons. |
| 31 |
Invalid SMPTE argument |
Please check to ensure that the SMPTE argument within your script is timecode1 or timecode2. Any other text in this field will cause er |
| 32 |
Text in row E of the script file |
Row E of the COBRA script file is currently not used for scripting features. If your 18R2 is displaying ER32 then there is text in row E of your COBRA script file. This is often caused by a comma or a semicolon in your firework name. |
| 34 |
Issue accessing or downloading your script files from your USB drive |
Er34 occurs when the COBRA 18R2 controller has an issue accessing or downloading your script files from your USB drive. Please ensure your script file is not in any folder and is on the root drive of the USB device. Try loading the script files again or try another USB. *Er will display on the upper 7-segment display and the number 34 will show on the lower display. |
| 35 |
More than one script use the same trigger channel and button combination |
Er35 will occur when two or more scripts share the same trigger channel and trigger button. To remedy this error you must either change the trigger channel and/or button on one or more of the scripts or, use the COBRA Control panel to select the script you would like to fire. *Er will display on the upper 7-segment display and the number 35 will show on the lower display. |
| 36 |
Invalid Pulse Time Format |
Acceptable pulse time values are between 0 and 20s and can be down to 1/10th of a second. For example, 10.1s. |
| 40 |
Missing DMX Channel |
A DMX channel is missing from your script. |
| 41 |
Invalid DMX Channel |
Make sure your DMX channels are numerical values between 0-199. |
| 42 |
DMX Channel Out of Range |
Make sure your DMX channels are numerical values between 0-199. |
| 43 |
Missing DMX Value |
A DMX Value is missing from your script. Make sure a numerical value between 0-255 has been entered for each DMX event. |
| 44 |
Invalid DMX Value |
Make sure a numerical value between 0-255 has been entered for each DMX event. |
| 45 |
DMX Value Out of Range |
Make sure a numerical value between 0-255 has been entered for each DMX event. Values outside of this range will give this error. |
|
46 47 48 49 |
Invalid DMX Pulse Duration |
Make sure a valid pulse duration between 0 seconds and 10 minutes has been entered. Formated mm:ss.xx. |
|
50 |
Missing DMX Universe |
A DMX universe is missing from your script. |
| 51 |
Invalid DMX Universe |
An invalid DMX universe is in your script. Make sure each DMX event has a universe specified between 1-99. |
| 52 |
DMX Universe Out of Range |
An invalid DMX universe is in your script. Make sure each DMX event has a universe specified between 1-99. |
| 53 |
Maximum DMX Events In Script |
The maximum number of DMX events has been reached. Each script can contain 10,000 DMX events. |
| 54 |
Maximum Events On One Channel |
The maximum number of pyro events on one channel has been reached. Each channel can be fired 400 times in one script. |
| 55 |
Maximum DMX Events Per Universe |
The maximum number of DMX events for one universe has been reached. Each DMX universe can contain 3,000 DMX events. |
| 56 |
DMX Events in Non-Uploaded Script |
DMX events are only supported in the first script (uploaded). Remove DMX events from all non-uploaded scripts. |
| 57 |
STEP Events With Timecode |
STEP events are not supported when using Timecode within in your script. Remove Timecode or STEP events from script. |