Whenever Reaper isn’t responding Edge reports the following error:
GET http://192.168.98.228:8085/_/GET/TRACK/0/SEND/0;TRANSPORT;BEATPOS;TRACK;GET/40364;GET/1157; net::ERR_CONNECTION_REFUSED
We can introduce a try/catch statement in the send code that lights up an indicator light when Reaper isn’t responding. Or maybe an event handling object?
Whenever Reaper isn’t responding Edge reports the following error:
GET http://192.168.98.228:8085/_/GET/TRACK/0/SEND/0;TRANSPORT;BEATPOS;TRACK;GET/40364;GET/1157; net::ERR_CONNECTION_REFUSED
We can introduce a try/catch statement in the send code that lights up an indicator light when Reaper isn’t responding. Or maybe an event handling object?