Lutron module p5 117 stop working

adys
adys Junior Member
in NetLinx Studio
Hi all

I am having an existing home with huge huge Lutron (167 keypads) system that used to work with the duet module p5 version 117.

After the Lutron man came and update the controller, the module is not working.
I tried a lot of things, reveresed my code, get back to a 100% working code, nothing.
The problem is that he did firmware upgrade to the controller to from 1.32.1 to version 1.49.1.

I have ping to the controller, "amx, control" is defined as it should on link 9.
The Lutron program is working good with the controller.

Only the module stooped working, looks like there is not connection but its hard for me to debug it...

Any ideas before I am loosing my hair?

Thanks,

Ady.
· Share on FacebookShare on Twitter

Comments

  • ericmedley
    ericmedley Senior Member - 3709 Posts
    Did the password change on the Lutron controller?
    · Share on FacebookShare on Twitter
  • adys
    adys Junior Member
    ericmedley wrote: »
    Did the password change on the Lutron controller?

    Nope

    I can login with Telnet with "amx, control"

    in the module it goes
    SEND_COMMAND vdvLights, "'PROPERTY-Login,amx,control'"

    Been like that for 3 years
    · Share on FacebookShare on Twitter
  • ericmedley
    ericmedley Senior Member - 3709 Posts
    I'm still using the old skool rs232 module (non-duet) and have kinda built a work-around to get it to work with IP. it still works as far as I know. I don't have any angry clients standing outside my door with pitchforks and touches.
    · Share on FacebookShare on Twitter
  • DHawthorne
    DHawthorne Junior Member
    There haven't been any control changes in Lutron from v, 1.32 to v. 1.49; I've upgraded many without issue. Unless the Lutron guy deleted the login, there is no reason it should have stopped working. Did you do any AMX upgrades while you were at it? I've had that happen more times than I can count ... and AMX update breaking a Duet module.

    Another thought though ... did the IP address on the Lutron change? By default, they are DHCP, not static, and the update might have forced a new address. I'm thinking there is a real strong chance of this ....
    · Share on FacebookShare on Twitter
  • adys
    adys Junior Member
    DHawthorne wrote: »
    There haven't been any control changes in Lutron from v, 1.32 to v. 1.49; I've upgraded many without issue. Unless the Lutron guy deleted the login, there is no reason it should have stopped working. Did you do any AMX upgrades while you were at it? I've had that happen more times than I can count ... and AMX update breaking a Duet module.

    Another thought though ... did the IP address on the Lutron change? By default, they are DHCP, not static, and the update might have forced a new address. I'm thinking there is a real strong chance of this ....

    Thanks

    I have the same login as it was, he didn't delete it;
    The ip is the same.

    I just can't connect with the module, with Telnet its ok.
    · Share on FacebookShare on Twitter
  • DHawthorne
    DHawthorne Junior Member
    If you aren't talking to the module, it's almost certainly a NetLinx firmware incompatibility with the module. Telnet the master, and do a "show system" command. If you don't see any device numbers in the 40000 range, that's the problem. Unfortunately, there is no hard and fast solution except to make sure the master firmware and the module are completely up to date. I have had one or two cases where the module hadn't been updated by AMX and simply would not work with current firmware, and I had to make my own NetLinx version.
    · Share on FacebookShare on Twitter
  • ericmedley
    ericmedley Senior Member - 3709 Posts
    DHawthorne wrote: »
    If you aren't talking to the module, it's almost certainly a NetLinx firmware incompatibility with the module. Telnet the master, and do a "show system" command. If you don't see any device numbers in the 40000 range, that's the problem. Unfortunately, there is no hard and fast solution except to make sure the master firmware and the module are completely up to date. I have had one or two cases where the module hadn't been updated by AMX and simply would not work with current firmware, and I had to make my own NetLinx version.
    this has happened to me too with a pool controller module. I feel that if AMX is going to make a module, they should offer a Netlinx version for just this reason. If they are not going to keep the Duet modules up to date, then we're bound to hit these walls.
    · Share on FacebookShare on Twitter
  • adys
    adys Junior Member
    DHawthorne wrote: »
    If you aren't talking to the module, it's almost certainly a NetLinx firmware incompatibility with the module. Telnet the master, and do a "show system" command. If you don't see any device numbers in the 40000 range, that's the problem. Unfortunately, there is no hard and fast solution except to make sure the master firmware and the module are completely up to date. I have had one or two cases where the module hadn't been updated by AMX and simply would not work with current firmware, and I had to make my own NetLinx version.

    Sorry for the late response.

    This is the case, I don't see any devices in the 40000 range.

    After duet firmware update the module is working!

    I have few issues with updates, but better than before.

    Thanks
    · Share on FacebookShare on Twitter
  • ericmedley
    ericmedley Senior Member - 3709 Posts
    adys wrote: »
    Sorry for the late response.

    This is the case, I don't see any devices in the 40000 range!

    I will update everything and update the solution here

    Thanks
    I got bit by this the other day. I was making a few changes to an older system with a 4100 in it. I was adding our CCS module and a #*(&$&*#*@ duet module. Lo and behold, the 4X,XXX range didn't show up. I upgraded the firmware and all was well.
    · Share on FacebookShare on Twitter
  • adys
    adys Junior Member
    ericmedley wrote: »
    I got bit by this the other day. I was making a few changes to an older system with a 4100 in it. I was adding our CCS module and a #*(&$&*#*@ duet module. Lo and behold, the 4X,XXX range didn't show up. I upgraded the firmware and all was well.

    Yes..

    The problems is that this module is not something to begin with... I will have to rewrite it one day
    · Share on FacebookShare on Twitter
  • adys
    adys Junior Member
    Ok, all commands are working, but no notification from module, at all, nothing.... :(
    · Share on FacebookShare on Twitter
  • ericmedley
    ericmedley Senior Member - 3709 Posts
    adys wrote: »
    Ok, all commands are working, but no notification from module, at all, nothing.... :(

    No notifications in NS? This might be a NS version vs. NI Firmware version issue.
    · Share on FacebookShare on Twitter
  • adys
    adys Junior Member
    ericmedley wrote: »
    No notifications in NS? This might be a NS version vs. NI Firmware version issue.

    Ok back to life!

    I have update this firmware
    http://www.amx.com/techcenter/downloadConfirm.asp?fn=/assets/firmwareFiles/2105-04_NI-X100_Master_v3_50_439.zip

    and this
    http://www.amx.com/techcenter/downloadConfirm.asp?fn=/assets/firmwareFiles/SW2105_NI_X100_Device_v1_20_7.kit

    When ever I am uploading full source include the jar file, it stop working, so I needed to update firmware again...
    so now when I am loading I am only updating my code.

    thanks for all the support, you really saved me!

    I am not recommending this module to anyone!

    Ady.
    · Share on FacebookShare on Twitter
  • ericmedley
    ericmedley Senior Member - 3709 Posts
    adys wrote: »

    I am not recommending this module to anyone!

    Ady.
    Another satisfied duet customer!

    Glad you got it up and running.
    · Share on FacebookShare on Twitter

Categories