Read iSerial v.4 suddenly stopped
Posted: Mon Feb 28, 2022 10:48 am
Been reading water data (my own code, C) since 2014.
Linux, Ubuntu 20.04. All been working perfectly.
iSerial has a static IP on my local net. Ping to it works.
Omnimeter Pulse v.4
iSerial v.2
Since February 25 2022, 8:30AM (PST) writing a request to iserial
seems to still work, but read fails.
I switched to calling select() as an
experiment [because the code in
use for years hangs forever on read now] and that select() times out after the
timeout (I set to 5 seconds) returning 0 (the input fd is usually
6) so the iSerial is never 'ready'.
The code in use till the select() experiment just delayed one
second after the write and did a read...which used to work.
EKM Dash (installed latest 64bit version yesterday) says
it gets no response from the iSerial
Could iSerial have developed a fault? Lost some setting
in a power outage here (near San Francisco)? (the UPS
it takes power from is a few years old...).
Any hints? Suggestions for testing?
Thanks in advance.
David Anderson
Linux, Ubuntu 20.04. All been working perfectly.
iSerial has a static IP on my local net. Ping to it works.
Omnimeter Pulse v.4
iSerial v.2
Since February 25 2022, 8:30AM (PST) writing a request to iserial
seems to still work, but read fails.
I switched to calling select() as an
experiment [because the code in
use for years hangs forever on read now] and that select() times out after the
timeout (I set to 5 seconds) returning 0 (the input fd is usually
6) so the iSerial is never 'ready'.
The code in use till the select() experiment just delayed one
second after the write and did a read...which used to work.
EKM Dash (installed latest 64bit version yesterday) says
it gets no response from the iSerial
Could iSerial have developed a fault? Lost some setting
in a power outage here (near San Francisco)? (the UPS
it takes power from is a few years old...).
Any hints? Suggestions for testing?
Thanks in advance.
David Anderson