|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Looking for Last Minute Fixes on a Possible "Comm" Error
That's really weird. Your light never goes solid yellow, so you're not losing comm. I think the frequency of the interruption is too high for it to be the old Autodesk Updater problem. Are you getting Motor Safety Helper errors in your Driver Station logs? That'd be a good clue to something bogging down your teleop loop. The timing of the motor movements seems about right for that.
EDIT: If you physically have the Driver Station available, you can pull up the Driver Station Log Viewer from the start menu and look through the logs. Help on all that here. I'm about to hit the sack, so I won't be more help tonight. Last edited by Kevin Sevcik : 01-04-2016 at 23:51. |
|
#2
|
|||
|
|||
|
Re: Looking for Last Minute Fixes on a Possible "Comm" Error
I guess that we're fairly sure we've ruled out motor safety issues, but we simplified some of the programming to test tomorrow.
|
|
#3
|
|||||
|
|||||
|
Re: Looking for Last Minute Fixes on a Possible "Comm" Error
Motor Safety is absolutely what you're going to see if you have "complex" code that's bogging down the roboRIO. The Motor Safety helper objects are like watchdogs for each motor controller. If you're not sending a command value often enough to a controller, you'll get a motor safety error and the controller will be disabled till you set it again.
|
|
#4
|
|||
|
|||
|
Re: Looking for Last Minute Fixes on a Possible "Comm" Error
Quote:
|
|
#5
|
|||
|
|||
|
Re: Looking for Last Minute Fixes on a Possible "Comm" Error
Just for kicks, check that your radio is wired into the 12V2A socket, and nothing is plugged into the other 12v2A socket.
They are supposed to check for it during inspection, but it is easily missed. |
|
#6
|
||||
|
||||
|
Re: Looking for Last Minute Fixes on a Possible "Comm" Error
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|