|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Output signal failing problem fixed!
We don't get messages for every System Watchdog dropout, so it's the System count that might or might not match up.
The count in the error message isn't always sequential, implying that it can't always communicate back to the DS to tell us about them when they occur. |
|
#2
|
||||
|
||||
|
Re: Output signal failing problem fixed!
I installed the driver's station on my 64 bit 5 gig ram Windows Vista computer and ran the robot from it while we were graphing. We discovered that the flickering has nothing to do with the computer. There's something going on with the cRIO, or something else electronic, that we can't fix. We hooked up our E-Box to a robot today and ran it. We tested it before this, and the flickering was clearly there, but it didn't effect or make itself evident in the robot's driving. It's a problem without a fix which doesn't effect the robot noticeably.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| cRIO output problem | alex42 | FRC Control System | 1 | 27-01-2010 22:28 |
| Problem receiving console output from cRIO | Arborama | Programming | 7 | 15-02-2009 03:30 |
| I fixed the Codec problem | BuddyB309 | 3D Animation and Competition | 1 | 09-02-2006 00:12 |
| May have fixed the problem with blueprints... EVERYONE READ! | archiver | 2001 | 1 | 23-06-2002 23:01 |
| Forum Problem [fixed] | archiver | 2000 | 0 | 23-06-2002 22:54 |