View Single Post
  #12   Spotlight this post!  
Unread 09-04-2010, 20:52
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,101
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: runtime data collection

Quote:
Originally Posted by gvarndell View Post
Wind River already has it, now if we can just figure out a way to get them to include it for the FRC teams.
It's called data monitor (used to be called StethoScope).
Very easy to set and enable/disable monitor points, configure the sample frequency, set the buffer size, upload to host and (are you ready for this?) graph the data in Workbench.
This is exactly the kind of thing one hates to see programmers reinventing.
But if Wind River won't let you use it, and you need it, then you probably will end up doing it.
Yes, it will be fruitful/
This is exactly what I want. And no, I'd rather not re-invent it.

Teams with "overheating CIMs" could gain great insight using a tool like this, I would think, especially if they glued a small temperature sensor to each CIM. (Or if they were capturing motor current and voltage and speed, they could calculate winding resistance whenever the motors were stalled).


~

Last edited by Ether : 09-04-2010 at 20:55.