1

Closed

GTosPMU_App freezes when run in dd/mm/yyyy format regional time.

description

When system date is set to 12/5/2013 or 12/6/2013, on a system running in dd/mm/yyyy format regional date time.

http://www.youtube.com/watch?v=2h-9DPtNVNk&feature=youtu.be

Comment: The GTosPMU_App configuration and test software was developed using mm/dd/yyyy format regional date time. This is probably one or more problems related to software date conversion routines.
The GridTrak PMU sensor uses SOC and FRAC time so this is probably not firmware related.
Closed May 13, 2013 at 1:02 AM by ajstadlin
The new Timeout break in the Sync_To_PC procedure should prevent blocking the main app thread for more than 1 second. The design and implementation of the Sync_To_PC needs to be improved in a future release.

comments

ajstadlin wrote May 13, 2013 at 12:58 AM

GTosPMU_App Release 1.0.9.14 - Failsafe Timeout Break added to Sensor.Sync_To_PC wait loop.The wait loop will block the main processing thread for up to one second to send a signal to the PMU on the 1 second roll-over. This was originally intended to be performed once. The Sync_To_PC is only required for host synchronized mode in the GTosPMU_App software. The Sync_To_PC procedure is not used when operating in GPS Time source mode. However, various GTosPMU_App activities like CONNECT and PING will call the Sync_To_PC procedure to sync the PMU to the Host.

This issue does not affect IEEE C37.118 mode used by software like openPDC and PMUConnectionTester. The GridTrak PMU, when operating in Host Sync Mode, synchronizes to the time stamp in the C37.118 protocol messages sent from a IEEE C37.118 compliant PDC host.

The Sync_To_PC procedure needs to be re-designed to sync the PMU to the host a better way. This will be considered for future releases.