Sure, my software sends a serial command to BS1 then polls for·responses to different tasks.· Obviously, it's easy to know when the BSI stops sending data back to the software, but how do I detect in the BS! firmware code·that the software has stopped sending data to the BSI.· I guess I needed·watch dog like code that will detect no activity (like a computer crash) and then take an action like trip a relay.· Make sense?
Sounds like a plan. It would work best if the PC sends something every cycle even if it does not need changes. Then if the bs1 misses say four in a row it considers the connection broken.
Thanks Chris, but I think I'm just up against the·BS1's inability to timeout or wait for serial input.··Simply disbaling the the SERIN line allows the program to cycle and update the counter.· As long as Serin is not commented and no serial connection is made things freeze on it.· I will redesign to use the BS2 and make my life easier :-)
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- Stephen
Chuck
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- Stephen
Chuck
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Engineering
Chuck