X10 Community Forum
🖥️ActiveHome Pro => SDK => Topic started by: macrobob on November 05, 2010, 09:29:14 AM
-
Is it possible to clear the buffer on a CM19A or CM15A? I am using a CM19A now and it seems to lag behind my commands, After my program quits sending commands, the CM19A is still broadcasting for up to 60 seconds sometimes.
-
The CM19A has no internal memory.
Commands do queue up to be sent in the x10net service, but I don't believe we expose a way to flush that queue in the SDK.
-
The CM19A has no internal memory.
Commands do queue up to be sent in the x10net service, but I don't believe we expose a way to flush that queue in the SDK.
A way to flush the x10net service buffer would be very welcome, as well as a "transmission complete" and/or "buffer empty" event.
As long as we're wishing. :'
>!
-
A way to flush the x10net service buffer would be very welcome, as well as a "transmission complete" and/or "buffer empty" event.
Would stopping and restarting the x10nets service accomplish this?
-
A way to flush the x10net service buffer would be very welcome, as well as a "transmission complete" and/or "buffer empty" event.
Would stopping and restarting the x10nets service accomplish this?
It would probably clear the buffer anyway. Much in the same way a sledge hammer would probably work to turn off your computer. rofl
There needs to be a less destructive way, methinks.
>!
-
A way to flush the x10net service buffer would be very welcome, as well as a "transmission complete" and/or "buffer empty" event.
Would stopping and restarting the x10nets service accomplish this?
It would probably clear the buffer anyway. Much in the same way a sledge hammer would probably work to turn off your computer. rofl
There needs to be a less destructive way, methinks.
>!
You're right, Bill.
I was thinking of this as more of a one-off, troubleshooting type of action, not as a way to do it regularly when using the program.
-
Yeah. That's the problem. Sometimes the software just needs to be able to tell the service to clear the buffer without potentially crashing all other software that's depending on it.
>!