5.0.2 Known Issues
We are currently aware of two issues. It is important to state that the issues below are uncommon and only display sometimes with larger module count shows. Please find a description of the issue below, along with how to resolve it in the field if encountered.
Symptom: This happens only to the 18M hardware version A. The 18M is in an unresponsive state when armed or being woke up by the remote. If this occurs, the 18R2 will NOT display the module as armed and alert the user of the channel and address of the unit with the issue.
How to Fix: The operator can simply power off and power on the 18M which will allow the module to report back correctly to the 18R2 and fire normally during the show. Once armed, the module has no risk of going back into this state.
Symptom: The 18R2 does not show a module in the ARM count on the 18R2 even though the module ARM LED is lit. In this situation, assuming the module key is in the ARM position, the module WILL fire both manually and also fire a script.
How to Fix: Power off the 18M and power back on. Alternatively, if you disarm the 18R2 and re-arm the 18R2, the modules should refresh to the ARM state assuming you don't see another module not appearing in the module ARM count. Note that even though the module is not showing in the ARM count, it's actually armed and will fire.
The following alert was sent out to customers that had the new hardware:
5.0.5 Patch Release Notes - 18R2 Critical Safety Alert
On July 24th 219, we discovered a critical safety issue affecting 18R2s w/ our new SM220 transceiver that was shipped shortly after July 4th, 2019. This issue would cause the remotes running 4.0.0 or greater to, in some cases, fire an unintended cue in manual firing mode only. For example, pressing cue #1 may fire cue #1 and cue #2. Also, in rarer cases, the act of arming the 18R2 may fire a cue unintentionally if the remote is on the same channel as the module used in the shoot.
The issue would only affect 18R2s that are both running firmware version 4.0.0 or greater, and shipped after July 4th. All customers affected have been contacted via e-mail or phone, If you are just now becoming aware of this issue, you are not affected. If you have a unit with the new SM220 transceiver, you will see U90-SM220 in the upper right of the faceplate. Additionally, the new transceiver is red, whereas the older transceiver is green.
We have fixed the issue and provided the following instructions:
- 1) Download the 4.0.1 or 5.0.5 cobra.s19 file from our website
- 2) Save this file to a USB drive. Do not place the file within a folder.
- 3) Place the USB drive into your 18R2.
- 4) Hold the SYNC button and power on the 18R2 at the same time.
- 5) The LEDs will circle around and the unit will power off. Note: If all red LEDs display in this step, please try a different USB drive.
- 6) Remove the USB drive
- 7) Power on the 18R2 and either 4.0.1 or 5.0.5 will display. Your unit is now updated.
**Don't worry, 5.0.5 on the 18R2 is fully compatible with 5.0.2 or 5.0.3 on the modules.
We have been in constant contact with those who purchased equipment during this period to ensure those individuals were aware of our findings. Any affected clients will also receive communication from us with the steps required to upgrade their remotes to the new firmware.
We would like to thank the COBRA community for their understanding as we worked tirelessly to ensure a complete and thorough resolution was developed, fully tested, and rolled out.
Please do not hesitate to reach out to us at firstname.lastname@example.org with any questions or concerns.