The CRTD timestamps should be unix julian time (not uptime). Produced by this:

  sprintf(m_buf,"%ld.%06ld %sR%s %0*X",
    time->tv_sec, time->tv_usec,
    busnumber,
    (frame->FIR.B.FF == CAN_frame_std) ? "11":"29",
    (frame->FIR.B.FF == CAN_frame_std) ? 3 : 8,
    frame->MsgID);

Once module gets time from the vehicle (or gps), it should show the correct timestamps.

Regards, Mark.

On 5 Jun 2019, at 1:15 AM, Stephen Casner <casner@acm.org> wrote:

Thanks.  I filtered out the 20MB that were relevant.

If you did not delete the file from /sd yet, please tell me the
timestamp of that file so I can correlate the uptime-based timestamps
in the log to wallclock time.

Or, Mark or Michael, is there a better way to associate these
timestamps?  Perhaps a way to ask what the boot time was
(corresponding to uptime 0)?

                                                       -- Steve

On Tue, 4 Jun 2019, Greg D. wrote:

200mb of logs sent to Steve for analysis....

Greg


Stephen Casner wrote:
Thanks.  For me, today's log was much quieter.  The maximum excursion
was 115 meters and it was roughly coincident with loss of lock.

                                                       -- Steve

On Fri, 31 May 2019, Greg D wrote:

Ok.  I'll let it run for a few days and see what happens. Not planning to drive the car until next week.

Greg


On May 31, 2019 2:11:31 PM PDT, Stephen Casner <casner@acm.org> wrote:
On Fri, 31 May 2019, Greg D. wrote:

Tried this, and am not getting anything written to the file system
(vfs
ls /sd shows zero bytes in gps.crtd).  Did I miss some sort of setup
step?

Nothing gets written (or at least the file size as reported is not
updated) until the recording is stopped with "can log off".

                                                      -- Steve
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev
--
This space for rent...
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev


_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev