|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Reading log files of current
The reader for the .pdplog hasn't been released yet.
|
|
#2
|
|||
|
|||
|
Re: Reading log files of current
Well that's a bummer. I thought the ability to log current was one of the big marketing points about this new roboRIO and PDP? [quote]If you instantiate a PowerDistributionPanel object ... you can access the current of individual channels as well as the total current in real time. /QUOTE] We use labview - our programmer's able to display the individual currents in real time - didn't know we could display total current? I'd considered asking him to sum all the individual together or something like that and display the sum but if there's an easier way that's inherent to labview - can anyone advise on that? Looking at instantaneous current values is better than nothing, but it'll really be nice to be able to look at a log after the fact. Any advice? |
|
#3
|
||||
|
||||
|
Re: Reading log files of current
You might consider saving the current values to your own log file every couple second or milliseconds. Probably best to use a csv or tab delimited format, then you could put it into a spreadsheet program and possibly graph the data there.
|
|
#4
|
||||
|
||||
|
Re: Reading log files of current
have your programmers read the current during the match and write a file on the roboRIO?
|
|
#5
|
||||
|
||||
|
Re: Reading log files of current
My understanding is that the log viewer will be released after week 1.
|
|
#6
|
||||
|
||||
|
Re: Reading log files of current
Has the spec for the .pdplog file format been released?
|
|
#7
|
||||
|
||||
|
Re: Reading log files of current
Is the file human-readable?
|
|
#8
|
||||
|
||||
|
Re: Reading log files of current
It would appear that it isn't, but I haven't tried too much.
Here's a link to one of ours https://drive.google.com/file/d/0Bzf...ew?usp=sharing Can logging be disabled? It's quite useless as it is now, and we end up in a bad state if we enable and disable quickly, which I believe is the log file being sent over. |
|
#9
|
|||||
|
|||||
|
Re: Reading log files of current
The PDP firmware update (1.40) addresses this bug.
|
|
#10
|
||||
|
||||
|
Re: Reading log files of current
Uh yeah. Here's all the text extracted:
Xn Wn Vn Un Tn Sn Rn Qn Pn On Nn Mn Ln Kn Jn In Hn Gn Fn En Dn Cn Bn An AD AE |
|
#11
|
||||
|
||||
|
Re: Reading log files of current
For fun, I started reverse engineering the file to see what I can see. Here's a snippet of the file displayed as hex:
(exported from frhed, and trimming off the first 0x14 bytes on a hunch (I think it's the header)) Code:
4bb98a019cf804b3030243545741540011776c0100000000000000000000000000621d27 4ca99d01000000000008300080030000c04003278cd0400403ae0000000000000000d55e 4da9b001000000000008000080030000c040031a4480810d03a70000000000000000f8b9 4ea9c301000000000008000080030000c04003100070451403a7000000000000000064cd 4fa9d601000000000008300080030000c040030f0020c20803ad0000000000000000a323 50a9e901000000000008300080030000c040032ea030010503ae0000000000000000b0f6 51b9eb019cf884b3030243545741540011776b0100000000000000000000000000623726 52b906009cf884b3030443545741540011776b0100000000000000000000000000621b26 53a90600000000000008000080034f005046030f0020810603a900000000000000000126 54a91a00000000000000000080031900c0410334a800030b03a100000000000000008830 55a92d00000000000008000080031b00b04103133030031303a50000000000000000fa0d 56a94000000000000008000080031b00b041030f0070030b03a9000000000000000016d6 57a95300000000000008000080033500b042030f0020030e03a40000000000000000e826 018ab94b 019da94c 01b0a94d I've also been looking for floating point numbers (put a 4 byte likely candidate into an IEEE-754 calculator to see if it's a meaningful number). My guess is that it's recording low resolution data quickly, or it's higher resolution data very quickly and they are multiplexing the current sensing. I'm still trying to make sense of it. It would be super helpful to have a file from a robot under known conditions. Something like Code:
power up disabled for 30s start teleop, but do nothing for 10s run a motor on channel 1 forward and back in 5s intervals for 30s run a motor on channel 2 forward for 5s ch3 for 5s, etc disabled power off I know the OP wasn't looking for a research project, but this is an interesting type of problem that can be solved with a little testing. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|