NI firmware update needed
DHawthorne
Junior Member
in AMX Hardware
It's been several weeks since this issue was raised, but having to deal with it on a constant basis is getting to me.
The 'SP' command for IR ports on NI units has been broken since the release of the last firmware (The previous firmware worked, and this release was supposed to fix other IR problems which I personally never ran up against).
The problem is that the command queue locks up, causing IR pulses to fail. It's not particularly consistent - it can behave for a long time, then suddenly lock for no apparent reason. I know the problem is in the queuing, because if you send just one 'CP' command, it unlocks the port. I've gotten in the habit of using CP whenever I am sending a single pulse, and then trapping commands that need to be queued (like a multi-digit channel command) by starting with a CP and finishing off with subsequent SP's, and hoping it doesn't lock up in the middle of the sequence. This pretty much means overriding the CH command. All that said, it does nothing for the cases where you can't predict how fast an IR pulse sequence will come in (like a customer mashing channel buttons). NXI's are not affected, it is strictly an NI problem with firmware 1.00.118 (not the master firmware, but the device).
In any case, this needs to get back on the radar.
The 'SP' command for IR ports on NI units has been broken since the release of the last firmware (The previous firmware worked, and this release was supposed to fix other IR problems which I personally never ran up against).
The problem is that the command queue locks up, causing IR pulses to fail. It's not particularly consistent - it can behave for a long time, then suddenly lock for no apparent reason. I know the problem is in the queuing, because if you send just one 'CP' command, it unlocks the port. I've gotten in the habit of using CP whenever I am sending a single pulse, and then trapping commands that need to be queued (like a multi-digit channel command) by starting with a CP and finishing off with subsequent SP's, and hoping it doesn't lock up in the middle of the sequence. This pretty much means overriding the CH command. All that said, it does nothing for the cases where you can't predict how fast an IR pulse sequence will come in (like a customer mashing channel buttons). NXI's are not affected, it is strictly an NI problem with firmware 1.00.118 (not the master firmware, but the device).
In any case, this needs to get back on the radar.
Leave a Comment
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums