|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: High Speed Encoder Problem
The periodic rate can be controlled either by a fixed value or follow the driver station. If it is set to follow the driver station, which is the default, then the period time will vary because of being a windows app. If you set the period to a specific value the cRIO will maintain a very precise periodic rate. This could also be a source of your problem.
-Hugh |
|
#2
|
||||
|
||||
|
Re: High Speed Encoder Problem
Quote:
|
|
#3
|
||||
|
||||
|
Re: High Speed Encoder Problem
Quote:
Does the FMS follow the user's DS, or is it designed to send TeleOp packets at 20ms ? And even if it is designed to send at 20ms (rather than following the user's DS), I guess the problem would still exist, albeit perhaps in a slightly different form, yes? no? still thinking about it. |
|
#4
|
|||||
|
|||||
|
Re: High Speed Encoder Problem
At competition the DS packets are still sent by the DS.
FMS only orders the DS to change modes, but the DS has to send that command to the robot. Any slow down in the DS PC will delay packets. One of the checks for slow or lost packets is the CPU utilization on the DS. (If in the Classmate Driver acct. use: CTRL-Shift-Esc -> Performance) A saturated netbook can be a cause of lost and delayed packets. I see that pretty often. Last edited by Mark McLeod : 23-02-2012 at 11:05. |
|
#5
|
||||
|
||||
|
Re: High Speed Encoder Problem
Quote:
So Hugh's comment about DS packet timing variations caused by Windows scheduling of the DS applies equally at home and at competition. Last edited by Ether : 23-02-2012 at 11:23. |
|
#6
|
|||||
|
|||||
|
Re: High Speed Encoder Problem
Quote:
We use C++. There is a configuration variable that sets the periodic rate. If it is zero then the rate will follow the driver station. If it is not zero then the value entered will be the periodic rate. I tell our programmers to ALWAYS set the rate. We have not settled on a value for this year yet. We use a scope to be sure all of our traffic on the CAN bus is complete. This is detailed in other threads as you know. As best I know FMS does not fiddle with this. Last year we used 100 msec and would show up on FMS as a long ping time. A few times the FTA would tell us about it, but it didn't seem to be a problem. I have some photos of the FMS screen showing this. I will try to find them and post here, but this season has been very busy, so don't hold your breath. :-) Maybe we should start a new thread about this? -Hugh |
|
#7
|
||||
|
||||
|
Re: High Speed Encoder Problem
Quote:
What is the class.method that you call to set this? Is it available in Java? |
|
#8
|
||||
|
||||
|
Re: High Speed Encoder Problem
Quote:
EDIT: Here's the link: http://www.chiefdelphi.com/forums/sh...d.php?t=103676 Last edited by Ether : 23-02-2012 at 11:39. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|