Driver starts logging after round hour (ws-28xx driver)

[GoogleCodeExporter]

When starting wfrog with the WS28xx driver, I need to wait until a round hour 
when the current-wfrog.xml is created. 10 minutes later the CSV file is 
generated as normal.

Starting wfrog for example at 8:23, logging starts at 9:00. After this moment, 
it keeps functioning correctly, but again not after a restart of wfrog.

What steps will reproduce the problem?
1. Start wfrog
2. No current xml and wfrog.csv file is created
3. At a round hour (7:00, 8:00,9:00, etc.) the files are created and logging 
starts

What is the expected output? What do you see instead?
Logging should start immediately after starting wfrog

What version of the product are you using? On what operating system?
Wfrog 0.8.2 SVN (version r936)

Please provide any additional information below.
According to the developer of the WS28xx, this is caused by the way wfrog 
works. See: https://github.com/dpeddi/ws-28xx/issues/1

Original issue reported on code.google.com by hiljolod...@gmail.com on 12 Feb 2013 at 4:59

[GoogleCodeExporter]

2013/2/13 Hiljo <hiljolodewijk88@gmail.com>
> BTW: Eddi thinks the 'waiting' until a round hour is behaviour 
> of wfrog. Can you confirm this? It's not a big problem, but if 
> i would need to restart the machine, one hour is lost of data, 
> instead of 3-4 minutes. Thanks for help in advance!

To my best knowledge, wfrog does not wait until a round hour to start saving 
data. wfrog starts saving data until the first period (usually 10 min. but 
might be modified through config files) is elapsed to write a record. If no 
events are received during a period no data is written.

I've never run before into this issue before and since all reports of this 
issue are related to the ws-28xx I would point to something related with this 
driver or the way that software interacts with wfrog.  

Original comment by jordi.pu...@gmail.com on 13 Feb 2013 at 3:27

• Changed title: Driver starts logging after round hour (ws-28xx driver)

[GoogleCodeExporter]

Thank you for the response. This is also what my first thought was. Hope the 
ws28xx driver developer can sort this out.

Original comment by hiljolod...@gmail.com on 13 Feb 2013 at 4:04

[GoogleCodeExporter]

Pressing the SET button on the display, seems to restore the connection and 
logging again. Workaround for this problem is thus identified.

Would be better of course if this wasn't necessary.

Original comment by hiljolod...@gmail.com on 14 Feb 2013 at 7:59

[GoogleCodeExporter]

It seems that no action required on wfrog, therefore the issue can be closed.

Original comment by jordi.pu...@gmail.com on 27 Mar 2013 at 2:39

• Changed state: WontFix