X10 lockup

[Outlet]

Hello,

I have noticed that if you send a fair number of X10 commands in succesison, the X10 module will stop sending commands until you unplug/replug it.  Is this caused by the X10 device, or the ioBridge?  I am currently using the PSC04.

Thanks!

[whitehexagon]

What do you call a fair number? I'm sendiong quite a few around and not had this problem so far.  Are you sending the command programatically very fast or something?

[Outlet]

Probably 1-2 per second (click on a button several times quickly), will usually do it.

[whitehexagon]

I can confirm that I have the same issue here, but running with the Marmitek XM10 module.  Disconnecting and reconnecting the X10 interface board seems to fix things.  It repeatable just by clicking an on off switch quickly for a few seconds.

[jason]

My guess is that sending commands in quick succession is over-running the X10 boards buffer.  X10 commands are surprisingly slow.  There are a few layers of redundancy built into the protocol, making a simple "turn on this lamp" longer then you might expect.  X10 waits for an AC zero-crossing to send each individual bit.  The theoretical maximum throughput for X10 on a North American grid is 60 bits/seconds (even lower on European, 50Hz electrical grids).

If the X10 board is locking up because to many commands are being thrown at it, my suggestion is to slow down the rate at which commands are sent.


   

[whitehexagon]

Do you know if this is still an issue with newer X10 modules? ie is the command rate now being limited/throttled on your side?  Your last response seemed to indicate it would have to be an end user managed situation.  But I'm wondering if that is practical especially if a widget is shared (on the web) and receives many distributed hits.

If not, do you know a sensible rate that doesn't cause the lockups?  I'm working on a X10 Dimmer control which involves sending many requests to adjust brightness...