COBRA Firmware Version 6.1.9 Release

The COBRA 6.1.9 release includes critical fixes for script memory management, power-cycle behavior, and DMX stability. Note: This release requires updating firmware files specific to each hardware type (.s19 or .spy, depending on the device) for the 18R2, 36M/72M, 18M, and 6M.

Key Improvements & Fixes

18R2 Remote Control

• Resolved a rare issue where a module might fire events from a previous script still in memory if the new script did not use those specific channels.
• If a script is configured with a Deadman button, you can now bypass SMPTE input by pressing ARM again while holding the Deadman button to start the show.
• New Error Reporting: The following error codes are displayed during script loading and validation unless otherwise noted.
  • Er3: Triggered if the CSV contains more than 32 scripts.
  • Er28: Triggered if a script exceeds 18 alternate events for Alternate 1 or 2.
  • Er37: Triggered if more than 12 disable groups are loaded.
  • Er54: Triggered if a script exceeds 400 events per channel.
  • Er7: Now displays during boot-up if an invalid script ID is detected. Re-import the script to clear.
• 18R2 Rev 2 LiPo Compatibility: Added support for the new 1S LiPo battery and adapter kit, allowing the 18R2 to accurately calculate and display battery voltage (P-values).
• Fixed an issue where non-ASCII characters in the cobra.csv file caused invalid errors. In some cases, invalid non-ASCII characters following the # comment character in the cobra.csv file would cause an invalid error 12. This issue is fixed as non-ASCII characters are now ignored.
• When importing a script with over 999 events, if an error occurs after the 999th event, the 18R2 shows the error line number by displaying the thousands digit on the top 7-segment display, followed by the remaining digits. For example, for line 1,345, it shows "1" and then "345".
• In some cases, importing a script file generated from Finale3D would generate an invalid error 18. This issue is now fixed.
• When changing security mode on the 18R2, the channel + or - button pressed during startup becomes unresponsive until the controller is power cycled. This issue has been resolved.
• In rare cases, only after upgrading a remote from 6.1 to 7.1 and clearing the scripts off the 18R2, after loading a new script to the 18R2, a module may not download the new script. This issue has been resolved.

Modules (18M, 6M, 36M/72M)

• Modules now remember channel changes immediately, even if powered off within 10 seconds.
• Fixed an issue where 36M/72M units would display "illegible characters" on the DMX screen after clearing scripts from the remote.
• Resolved an issue where the firing mode could reset to a null value after an update, causing only the first cue to fire in manual mode.
• DMX data now properly sends a stop command when a show is paused or the remote is moved to TEST mode.
• 18M units now display "HdA" or "HdB" during the startup sequence to identify hardware versions.
• Resolved an issue where the firing mode could reset to a null value after an update, causing only the first cue to fire. In rare cases, the 18M firing mode (0.1s or 2.0s firing time) was set to a null value after a firmware update, causing the 18M to only fire the first cue, and no subsequent cues. This issue is resolved as the firing mode is now properly set during upgrade.
• In some cases, when the 36M/72M Er1 (Low Driver) code is present, you were not able to change the module's voltage mode; this has been resolved.
• In some cases, the 36M or 72M may not send null values within a combined timed / STEP script when the 18R2 is paused on a STEP event. This issue has been resolved as null values are now sent from the 36M and 72M when a STEP event is encountered.
• Resolved a rare issue where a module might fire events from a previous script still in memory if the new script did not use those specific channels.

Control Panel Gen 2

• Fixed a benign issue where the Control Panel might indicate a script was still running after it had ended.
• In some cases, DMX event times were displaying incorrectly in the Control Panel. This was a display-only issue, as the DMX events were firing at the correct time but were displayed incorrectly in the Control Panel event list UI. This issue has been fixed.
• In some cases with larger scripts, the Control Panel may fail when importing the script. This issue has been resolved.

Installation Instructions

To update your equipment, please ensure you are using the correct files and method for your specific hardware:

• 36M / 72M: Download both the 90M.s19 and 90MB.s19 files.

• COBRA 18R2, 18M, and 6M: These devices must be updated using the COBRA Reprogramming Software to install the required .spy files and s19 as required.

For a comprehensive walkthrough, please see: How to Upgrade COBRA Firmware.

Update Steps (USB Devices)

1. Place the downloaded firmware files into the root directory of a compatible USB drive.

2. Ensure the device is powered OFF, then insert the USB drive.

3. Hold the SYNC button while powering the unit ON. The LEDs will circle to indicate the update is in progress.

4. Once complete, the unit will automatically restart and display 6.1.9. You may now remove the USB drive.

5. Restart the unit one final time to confirm the version number appears correctly on the startup sequence.