Official Firmware Versions

The COBRA 6.1.9 release includes the following features and fixes.

• Resolved a rare issue where cues from a previous script were not properly removed when loading a new script while modules were armed.
• 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:
  • Er3: Triggered if the CSV being loaded contains more than 32 scripts.
  • Er28: Triggered if more than 18 alternate events are used for Alternate 1 or Alternate 2 in the script being loaded.
  • Er54: Triggered if a script being loaded exceeds 400 events per channel.
  • Er12: Fixed an issue where non-ASCII characters in the cobra.csv file caused invalid errors.
• 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.
• 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).

• 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.
• The 18M now remembers channel changes immediately, even if powered off within 10 seconds.

• The 6M now remembers channel changes immediately, even if powered off within 10 seconds.

• 36M/72M units now properly send null values for all channels when the script is finished or when paused on a STEP event.
• Modules now always appear on the Control Panel after powering on, even if the 18R2 is already armed.

• Fixed a benign issue where the Control Panel might indicate a script was still running after it had ended.
• In some casesF 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.

• When manually firing cues when armed, the cue continuity would disappear from the channel. This issue is now fixed as the cue continuity remains and the proper firing statuses display.

• In some cases, multiple alternate events will fire when pressing the alternate 1 or 2 button.
• The 18R2 now changes channel and changes the cue LEDs to red on the remote display when firing. This functionality was removed in 6.1.4 and is now re-introduced in 6.1.6.

• Within an optimization change to 6.1.4, an issue was introduced where a script may not fire specific cues due to logic error in our firmware code. This was reported by one customer on Oct. 7th and would only occur in some cases of specific module and cue timing.

• 18R2 - High-intensity firing cadences combined with SMPTE may cause for a module to skip a cue in rare cases
• 18R2 - No longer changes channel while a script is running allowing for manual firing during a show (no longer in current release, coming in next patch release)
• 18R2 - Bug fix for pressing multiple cue firing buttons at the same time on the 18R2
• Audio Box - Optimized and fix some issues for audio alignment during SMPTE run scripts

• 36M/72M Hardware A only becomes inoperable in some cases due to flash memory configuration issue

• 18R2 / Control Panel - Jump to re-enabled in Control Panel for timed and STEP events
• 18R2 / Control Panel - Elapsed time showing incorrectly when jumping is performed
• 18R2 / Control Panel - Changing firing mode now supported from Control Panel
• Audio Box - Audio skipping may occur if SMPTE is used with 18R2 together with the Audio Box
• Control Panel Gen 2 - The UI may display a 36M or 72M’s key state momentarily in the wrong position. This only affects the 36M and 72M modules.
• 18M Hardware B - When initiating a STEP command from the 18R2 from a scripted show, if a module does not receive the STEP command, it’s possible an event may fire late and eventually re-align once the heartbeat from the 18R2 is received.

• 18R2 - STEP event may cause script to not fire

Minor New Improvements

• Total Events in COBRA Show Creator and Control Panel Consistency
• Audio Box Always Plays Single Audio File
• Audio Box Feature to Not Pause Audio with STEP Events
• Double Tapping TEST or ARM Displays Device Count
• Modules Indicating Communication Status
• Blank Lines in Script Now Ignored
• Script Loading Event Line Indicator on 18R2
• Jumping Forward and Backward in SMPTE Scripts Now Supported

Bug Fixes

• Audio Box Not Recognizing USB Drive
• 18M and 6M Not Firing Script if Power Cycled Mid-Show
• Module Powered On Mid-Script may Fire Previous STEP Event
• Script Error 16 Incorrectly Displayed as Error 54 on 18R2
• Control Panel Not Displaying Modules
• Events Between 0 and 1 second Not Appearing as Fired in Control Panel using SMPTE
• Quickplug 6-Cue Visualizer Now Works on 36M/72M for Showing Continuity
• Auto-Fire LEDs Displaying on 36M/72M in TEST Mode
• Modules Not Displaying in ARM Count on 18R2
• 18M May Not Turn Off Red Cue LED if Cue is Shorted and Fires
• Updating Firmware on 36M/72M May Change Voltage Mode
• Space Between Filename and .mp3 Extension Causing Playback Issues
• Module Not Firing Script
• Minor DMX Issues
• Manually Clearing Scripts Not Blinking SYNC LED or Displaying 00
• Changing Firing Mode (0.1s vs. 2.0s) While Module is Armed is Disabled on 36M/72M
• SMPTE Timecode Quality Displays 0 with Large DMX Scripts
• Last Event in SMPTE Driven Scripts May Not Fire

• Manually fire cues while the script is running
• Reinforced wireless security
• Fire multiple scripts without disarming
• Improvements to the ER3 stuck button error codes to allow full operation of the unit while only displaying which button was stuck, and disabling that button. 

Minor New Improvements

• Synchronization process change
• Audio accuracy
• 320k MP3 audio quality
• Sleep mode efficiency improved by 25%
• Manual AUTO-FIRE works past 12 seconds

Bug Fixes

• Sleep mode no longer displays backlight

Major New Improvements

• Universal compatibility
• 1P low battery level warning

18R2

• Addresses a rare situation (only reported once), whereby the 18R2 may pause while receiving a SMPTE feed and have no recovery other than re-starting the 18R2.
• Improved communication between the 18R2 and Control Panel, ensuring that all modules are displayed correctly as in some cases, a module may not appear.
• Improvements to the ER3 stuck button error codes to allow full operation of the unit while only displaying which button was stuck, and disabling that button. 

View Release Notes

The COBRA 7.1.8 release includes the following fixes and stability improvements.

• In rare cases when loading a new script to the 18R2, cues from a previous script were not properly removed causing inadvertent cues to fire. This only occurred if a new script was loaded while the modules were on and armed. This issue has been resolved.
• The Control Panel may not know if a script has stopped and would indicate the script was still running. This was a benign issue and is now resolved as the Control Panel now properly displays stopped when the script ends.
• If you have a deadman button configured on your script and are holding the deadman, you can now press ARM again to start the show without receiving SMPTE timecode input.
• In some cases the 36M or 72M may not appear on the Control Panel if you power the unit on while the 18R2 is armed. The 36M and 72M now always appear on the Control Panel after powering on when the 18R2 is armed.
• 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.
• Error 28 was added to the 18R2 for script importing to inform the user that there are more than 18 alternate events for ALTERNATE1 or ALTERNATE2 events.
• When firing a script that is configured for a deadman and SMPTE and you start the script with the deadman engaged, but no SMPTE is coming in, the 18R2 would change its channel to the channel of the first event in the script. This issue has been fixed as the channel no longer changes when the script starts in these specific conditions.
• If you attempt to import a script file with more than 32 scripts, error code 3 is now displayed on the 18R2.
• If you attempt to import a script with more than 400 events per channel, error code 54 is now displayed on the 18R2.
• When importing a script with more than 999 events, if an error is encountered past the 999th event, the line number displayed shows the thousands digit followed by the remaining digits.
• In some cases, importing a script file generated from Finale3D would generate an invalid error 18. This issue is now fixed.
• In some cases, DMX event times were displaying incorrectly in the Control Panel. This was a benign display-only issue and has been fixed.
• In rare cases, the 18R2 was sending an invalid pulse time to modules, causing firing at the default pulse time instead of the scripted value. This issue has been resolved.
• When changing security mode on the 18R2, the channel + or - button pressed during startup could become unresponsive until the controller was power cycled. This issue has been resolved.
• The 18R2 now displays error code 37 if more than 12 disable groups are loaded.
• After clearing scripts from the 18R2 and power cycling the 36M/72M while the 18R2 is powered on, the modules may have displayed invalid characters. This issue has been resolved.
• In rare cases, after upgrading from 7.0.x to 7.1.x and loading a new script, a module may not download the updated script. This issue has been resolved.
• If the 18R2 has an improper script identifier, it will now display Er7 and require the user to re-load the script.

• Hardware version (A or B) is now displayed during startup as HdA or HdB.
• In rare cases, the firing mode could reset to a null value after a firmware update. This issue has been resolved.
• Channel changes are now saved immediately, even if the unit is powered off within 10 seconds.

• Channel changes are now saved immediately, even if the unit is powered off within 10 seconds.

• The 36M and 72M now always send null values for all channels when the script is finished or the unit is in TEST mode.
• You can now change the voltage mode on the 36M/72M if an Er1 code is encountered.

• Fixed an issue where power cycling a 36M or 72M while armed caused the module to forget script events and not fire.

• When manually firing cues when armed, cue continuity would disappear from the channel. This issue has been fixed.

• In some cases, multiple alternate events would fire when pressing Alternate 1 or 2.
• Channel and cue LED behavior while firing has been restored on the 18R2.

• Resolved a critical issue where unintended cues could fire when using multi-script features.

• Fixed a logic issue introduced in 7.1.1 that could prevent specific cues from firing.

• High-intensity firing cadences combined with SMPTE could cause skipped cues in rare cases.
• Channel no longer changes while a script is running.
• Fixed pressing multiple cue buttons simultaneously.
• Audio Box alignment improvements for SMPTE scripts.