HOME › Forums › Gateways › EZSrve › PLM Error: Please Check Device/Connection

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • Anonymous
    Inactive
    April 13, 2008 at 3:15 am
    Post count: 69
    #39920

    I’m getting the above error intermittently, I believe whenever it tries to execute a timer command.

    I set up a couple timers for sunrise/sunset operations, but none of them have worked. One is an X10 command, the other is Insteon. I left the SHN Utility running this time to try and capture any traffic, but nothing is in there. When I got home from dinner this evening, the two lights that should have turned on weren’t, and my EZServe browser window had the title error.

    … time passes …

    Okay, I think I figured out why I got the error, but this might help others having the same problem. My X10 address was House Code “O”, Unit Code “5”. I typed “O5” in the address field when adding the device. The EZServe complained saying the address was invalid. I then typed “O.5”, similar, I thought, to how it wanted the Insteon addresses. It took this without a problem. I could not control the device, however. I finally opened the manual (yes, shame on me) and saw from the example I should have typed “O05”. This allowed me to control the device. I’ll find out tomorrow if the timer worked.

    Which brings me to another point. Why can’t I edit a device’s address? To change the address, I must first delete device. To delete the device I must first delete any timers or area’s it is in. I then can re-add the device, recreate the timers, and re-add it to the area. All to change a device code. Seems a little heavy to me. The EZServe should be able to figure that out.[/quote]

    Anonymous
    Inactive
    April 14, 2008 at 12:46 pm
    Post count: 408
    #41625

    Which brings me to another point. Why can’t I edit a device’s address? To change the address, I must first delete device. To delete the device I must first delete any timers or area’s it is in. I then can re-add the device, recreate the timers, and re-add it to the area. All to change a device code. Seems a little heavy to me. The EZServe should be able to figure that out.

    We are going to be improving that, but the rational at the time of development was that a device is not it’s text name, but it’s address.

    However, this can be a pain if you want to replace a bad switch for instance… so yeah, I hear you, and we are working on it.[/quote]

    Anonymous
    Inactive
    April 16, 2008 at 3:40 am
    Post count: 69
    #41626

    Well, fixing the address hasn’t fixed the problem. I still occasionally get PLM errors, only when sending timed X10 commands, though. Unfortunately, I haven’t been able to get it to happen consistently. I’m keeping the SHN Utility up to capture a log of the timer events now. When I get the PLM error message, this is in the log.txt:

    Message : 7:29:24 PM Tuesday, April 15, 2008
    
:
    
:
    
 SndX10
    
0X2
    
0X63
    
0X41
    
0X00
    
0X6
    

    


    

    
Message : 7:29:24 PM Tuesday, April 15, 2008
    
:
    
:
    
PLMTimeout

    What’s more, I’ve never been able to get a timed X10 command to work properly. I can issue them successfully manually from the EZServe without a problem, but never from a timer.

    I think I see a difference in the log file from a manually initiated x10 command and a timed one as such:

    Manually issued on command:

    Message : 10:38:35 PM Tuesday, April 15, 2008
    
:
    
:
    
 SndX10
    
0X2
    
0X63
    
0X41
    
0X00
    
0X6
    

    


    

    
Message : 10:38:36 PM Tuesday, April 15, 2008
    
:
    
:
    
 SndX10
    
0X2
    
0X63
    
0X42
    
0X80
    
0X6

    Timer initiated on command to same device:

    Message : 10:28:18 PM Tuesday, April 15, 2008
    
:
    
:
    
 SndX10
    
0X2
    
0X63
    
0X41
    
0X00
    
0X6

    I don’t see the second message, and the light does not turn on.

    Thanks for any help.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.