Questions
0
Under review
IVY 450C Device Time of 0?
We're using an IVY 450C Multiparameter Monitor, with a Device Adapter running on an Intel Edison. Any ideas why the Device Time reported for, for example, heart rate is 0 (the Epoch)?
The Monitor is connected to a Patient Simulator, and is reporting heart rate and blood pressure that look good, except that Device Time for all its values is reported as 0.
On a likely-related note, the OpenICE Supervisor shows what looks like a time-sync warning for the Multiparameter Monitor (and our other devices). Any idea what's going on here? What is required for a Device Adapter to properly time-sync?
Thanks,
Brad
Customer support service by UserEcho
It seems the Ivy 450C's DeviceClock is provided by whoever constructs the AnsarB (or AnsarBExt). I haven't yet found where the code is that constructs the DemoIvy450C's AnsarB. I'm suspecting that the Ivy 450C Device Adapter uses the default DeviceClock, which has no Device Time.
Any pointers would be very much appreciated. OpenICE's heavy use of Java Templates, delegates, Reflection, and Class hierarchy has made it difficult to find who constructs the Ivy 450C AnsarB/AnsarBExt.
Hey Brad,
One quick detail I need before diving in... is the clock on the Edison synced to the Supervisor's clock? Doesn't have to be precise (different NTP sources is fine but using NTP none the less). Obviously without an RTC chip onboard and no NTP the Edison will say Epoch time after reboot - this happens to our BeagleBones in the lab as well.
If the Edison's clock is time syncing appropriately we have a big problem I'm happy to dive into.
If the Edison's clock is not syncing, enable NTP. Your options are (but are not limited to):
- Providing most Linux OS' with internet access should do the trick with zero config.
- Using DHCP Option 42 is very handy for no-internet setups.
- I've had trouble in the past with setting up a standalone NTP server on a local network but that is the ideal solution.
Let me know and we'll proceed.
Thanks,
Jeff