Thread: CAN reliability
View Single Post
  #26   Spotlight this post!  
Unread 14-07-2010, 15:53
kamocat's Avatar
kamocat kamocat is offline
Test Engineer
AKA: Marshal Horn
FRC #3213 (Thunder Tech)
Team Role: Mentor
 
Join Date: May 2008
Rookie Year: 2008
Location: Tacoma
Posts: 894
kamocat is just really nicekamocat is just really nicekamocat is just really nicekamocat is just really nicekamocat is just really nice
Send a message via AIM to kamocat Send a message via MSN to kamocat
Re: CAN reliability

The "Clear Ack" VI seems to be taking 16 miliseconds, where as the "send" and "recieve" take 1 or 2.
I'm going to try out the Execution Trace toolkit, and see if I can dig in deeper.

EDIT:
Here's some data collected with the Execution Trace toolkit:
CAN Send takes around 600 microseconds with a message, 10 microseconds without.
CAN Receive takes around 2 miliseconds with a message, 20 microseconds without.
Clear Ack only takes about 15 microseconds.

I guess I'll try changing those DLL calls to directly reference "FRC_BlackJagBridgePlugin.out"

EDIT2: To be honest, it didn't make much difference. I think I'll change it back, however, because I think otherwise it won't let my motors be enabled.

Something that's not quite making sense about this execution trace toolkit is that subVIs are sometimes shown as executing for longer than their owning VI. Does it simply time how long the processor spends on each task, regardless of the VI hierarchy?
__________________
-- Marshal Horn

Last edited by kamocat : 14-07-2010 at 16:41.
Reply With Quote