Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Digital Matter Site
  • Contact Us

Integration - Common Issues

Written by Matthew Clark-Massera

Updated at January 25th, 2023

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Contact Support
  • Home
  • Device Manager (OEM Server)
  • Integration

Table of Contents

Why am I getting the date as 1/1/13? Can't parse the TCP data correctly - strange values - additional EFBFBD

Why am I getting the date as 1/1/13?

Time on Digital Matter devices is given as seconds since 01/01/2013. Before a device is powered on, it has no Real Time Clock (RTC) value. Once it comes online it will get a timestamp from the GPS or from the server. So if your device has had a hard reset - and not yet got a new GPS fix - the time sent in Field 0 will be 00:00 1/1/13. Any logs sent before the device has got a time from the server will also have this time. 

Can't parse the TCP data correctly - strange values - additional EFBFBD 

Your system might be encoding the TCP stream to a UTF-8 stream, rather than raw. 

issues integration 2013 time rtc gps

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Decode Cellular Uplink Payload using your Browser
  • Integration with the Azure IoT Hub
  • BigSmall Byte
  • Azure-IOT Hub Helper

Subscribe to Partner News

Subscribe to our mailing list to receive Digital Matter news, product and tehnical updates, and more.

Subscribe

Copyright © Digital Matter . All Rights Reserved.

Privacy Contact Support

Knowledge Base Software powered by Helpjuice

Expand