Go to Post I would say that you are not an engineer until you've both obtained the aforementioned peice of paper AND done something with your tumescent engineers forebrain. - phrontist [more]
Home
Go Back   Chief Delphi > Technical > Control System
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #8   Spotlight this post!  
Unread 09-04-2014, 07:25
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Alternate viewer for Driver Station Logs (dslog)?

The log file is not written out in the high priority timed loop. I try to keep that loop lean. It is done where we receive the status packets. What is logged is mostly the status info anyway. I have characterized the control packet loop with high CPU, but not the status or logging loop. The statistics on packet loss and latency are going to lag a bit just because of how they are measured and reported. The events tend to be even more lagged because they are often timeouts. But I have never seen a file where I thought the CPU usage messed up the data. If the DS doesn't have data for a time period, it replicates the new packet to fill in the void. So I would suspect that high packet loss would have flat spots for everything else and high bars for the packets.

The new format has version 1 and the trace bits are shifted down. Earlier in this thread, it shows a simple diagram that indexes the bits from the i8. It throws away the first two bits. We thought we were going to add more info and I modified code to prep. The result of that was that the bits are now packed starting at bit 0.

The dsevents file has the same header and then each event/warning is a timestamp and a LVString. The LVString is not NULL terminated, but is an i32 count of bytes followed by the bytes. The strings are possibly encoded a bit with <> tags, depending on who is sending the data to the DS.

Greg McKaskle
Attached Thumbnails
Click image for larger version

Name:	From Clipboard 6.png
Views:	54
Size:	99.8 KB
ID:	16797  
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 00:35.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi