|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: [FTC]: Detect loss of comm with FCS...
We are using the current JoystickDriver.c and believe that it has incorporated most of the functionality of the TechnoGuards version from previous years.
1. There is a global variable, nNoMessageCounterLimit, it's default value is 750 and it determines how long it will take for the no new messages functionality to kick in. 2. There is another global variable, a boolean, bDisconnected, which if true means that you have lost connectivity for nNoMessageCounterLimit cycles. You can use this variable to decide when to stop all of your motors because you are disconnected. |
|
#2
|
|||
|
|||
|
Re: [FTC]: Detect loss of comm with FCS...
Great. Thank you very much.
Congratulations on all your team's accomplishments during the last three championships. We learned a lot from you in Kentucky. |
|
#3
|
|||||
|
|||||
|
Re: [FTC]: Detect loss of comm with FCS...
Our teams wrote something almost identical to your post here. Good job on posting it. I recommend all FTC teams use this.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|