500i/5200i Firmware 2.86.53 level bug

PHSJason
PHSJason Junior Member
in AMX Technical Discussion
I was onsite yesterday and updated several panels (2 x 500i and 2 x 5200i) to the latest version due to slow performance/lock-ups (what this version was supposed to fix).
After updating, my panels with display levels where the values range from -700 to 100 would no longer respond to negative values. If I changed the value to a purely positive range, it would work fine.
As a test, I changed the values of one of the levels to range from -100 to 100. Sending a value of 100 set the level to the top as expected. Sending a value of 0 set it to the middle as expected, but sending a value of -100 also set the level to the top (opposite of expected behavior.).
Also these were level codes 9, 13, and 19 that I tested. This may not effect levels up to 8. Sending the SET_VIRTUAL_LEVEL_COUNT command did not help and the levels did exist and respond, they would just react incorrectly when values were sent to them.
I have 3 panels on site and updated 2 of them and one had older 2.82.52 firmware. Older firmware did not have this bug.

Important! Downgrading to 2.82.52 Firmware left this bug in place!!! After I found this bug, downgrading did not fix it. I had to tweak my code to only send positive values. In this case, not a huge deal, but in a system with a lot of levels this could be a major pain.
· Share on FacebookShare on Twitter

Comments

  • kennethk
    kennethk Junior Member
    I've noticed some treads regarding issues where latest firmware doesnt work as expected if program is created/downloaded with old Software(both TPD4 & NS).
    If you haven't, maybe try updating software, recompile and download again.

    BTW. I havent seen this issues yet my self...

    Just wanted to share my thoughts ;)


    Kenneth K
    · Share on FacebookShare on Twitter
  • John Nagy
    John Nagy CineTouch Product Manager
    Also be sure it isn't TPDesign4 that has changed the behavior. We've seen significant font handling and other effects of TPD4 on existing stable projects. I suggest this since you mention that downgrading the firmware didn't undo the deed... it is possible you reloaded the project with TPD4 and got a different result.
    · Share on FacebookShare on Twitter
  • PHSJason
    PHSJason Junior Member
    I verified that all AMX software was up to date prior to any loading. The bug that popped up happened with just a FW transfer to the panel, no panel file transfer either via NLS or TPD4. Once bug manifested, panel file was re-sent and tested. From this point, sending negative values to level 10001:3:13 worked as described above. Both from code and via control/emulate device.
    · Share on FacebookShare on Twitter
  • PHSJason
    PHSJason Junior Member
    kennethk wrote: »
    BTW. I havent seen this issues yet my self...

    Just wanted to share my thoughts ;)


    Kenneth K

    I hadn't seen it prior to yesterday either..... I did a system with the same code and an Ipad/MVP8400 a couple days before and no level issues.
    · Share on FacebookShare on Twitter
  • rfletcher
    rfletcher Junior Member
    I've also had this issue, and I'm kicking myself because I can't remember what panel type it was on or what fixed it. :o If you get the port status in NS you'll notice that the levels that aren't working right don't show sinteger (or anything other than integer iirc) as a valid type.

    Sorry I can't remember anything actually helpful, I'll post again if any of it comes back to me.

    -Ryan
    · Share on FacebookShare on Twitter
  • PHSJason
    PHSJason Junior Member
    AMX Tech confirmed the bug.
    · Share on FacebookShare on Twitter
  • felixmoldovan
    felixmoldovan Junior Member
    As a connected heads-up, it seems that AMX also decided to change the range of level 0:81 (Wifi Signal Level) from 0-100 to 0-5. (Probably others as well, just didn't notice them yet).
    Therefore, if updating, remember to change the span otherwise the clients will probably call you and share the "magic" of the panel working with nearly zero wireless signal. Why, oh, why???
    · Share on FacebookShare on Twitter

Categories