You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've have updated my X10 EXPRESS with the just released 1.5.0 nightly.
I was hoping DSMX telemetry received by the MultiProtocol Module would now be working.
Unfortunately the MPM has stopped working altogether with this firmware version.
The MPM Green LED is on solid but the Red LED is just flashing (.5s ON and .5s OFF) with no RF output from the Module.
According to the MPM troubleshooting page:
Slow blink(on=0.5s,off=0.5s): serial has been selected but no valid signal is being seen on the RX pin.
The MPM was working without telemetry on this same X10 EXPRESS with ETHOS v1.4.15
The text was updated successfully, but these errors were encountered:
Both of mine seem to be working -- I'm on an X10S Express, though this is likely inconsequential afaik. [Update: seemed, but do in fact not work.
I wonder whether enough info exists here (and maybe in the "API reference" site) to get it choochin' again, but if I had to bet, it's deeper than that.]
Have you seen this? I had to do this just yesterday to both modules since my X10S Express has been sitting collecting dust for years, and "silly me," I updated the internal module and that required me to mod my JP4in1 SE modules to get them working again.
I've have updated my X10 EXPRESS with the just released 1.5.0 nightly.
I was hoping DSMX telemetry received by the MultiProtocol Module would now be working.
Unfortunately the MPM has stopped working altogether with this firmware version.
The MPM Green LED is on solid but the Red LED is just flashing (.5s ON and .5s OFF) with no RF output from the Module.
According to the MPM troubleshooting page:
Slow blink(on=0.5s,off=0.5s): serial has been selected but no valid signal is being seen on the RX pin.
The MPM was working without telemetry on this same X10 EXPRESS with ETHOS v1.4.15
The text was updated successfully, but these errors were encountered: