Pneumatic Code Issues

[BurningTigers]

This past weekend we were at the WPI regional and we were unable to
get our pneumatic grabber working. We'd like to figure out what was
wrong so that we can fix it at boston and have it functioning. We had
help from an inspector and a labview programmer from 177, but they
were unable to get it working.

The error we got was:

Watchdog Expiration: System 1, User 0
ERROR <Code> -44045 occurred at
WPI_SolenoidCache.vi>>WPI_SolenoidSetEnum.vi>>Tele op.vi>>Robot Main.vi
<time>16:37:42 03/12/2011
FRC: The solenoid index is invalid.
ERROR <Code> -44045 occurred at
WPI_SolenoidCache.vi>>WPI_SolenoidSetEnum.vi>>Tele op.vi>>Robot Main.vi
<time>16:37:32 03/12/2011
FRC: The solenoid index is invalid.
ERROR <Code> -44045 occurred at
WPI_SolenoidCache.vi>>WPI_SolenoidSetEnum.vi>>Tele op.vi>>Robot Main.vi
<time>16:37:22 03/12/2011
FRC: The solenoid index is invalid.
ERROR <Code> -44045 occurred at
WPI_SolenoidCache.vi>>WPI_SolenoidSetEnum.vi>>Tele op.vi>>Robot Main.vi
<time>16:37:12 03/12/2011
FRC: The solenoid index is invalid.
ERROR <Code> -44045 occurred at
WPI_SolenoidCache.vi>>WPI_SolenoidSetEnum.vi>>Tele op.vi>>Robot Main.vi
<time>16:37:02 03/12/2011
FRC: The solenoid index is invalid.
ERROR <Code> -44045 occurred at
WPI_SolenoidCache.vi>>WPI_SolenoidSetEnum.vi>>Tele op.vi>>Robot Main.vi
<time>16:36:52 03/12/2011
FRC: The solenoid index is invalid.
ERROR <Code> -44045 occurred at
WPI_SolenoidCache.vi>>WPI_SolenoidSetEnum.vi>>Tele op.vi>>Robot Main.vi
<time>16:36:42 03/12/2011
FRC: The solenoid index is invalid.
ERROR <Code> -44045 occurred at
WPI_SolenoidCache.vi>>WPI_SolenoidSetEnum.vi>>Tele op.vi>>Robot Main.vi
<time>16:36:32 03/12/2011
FRC: The solenoid index is invalid.
ERROR <Code> -44061 occurred at "Left and Right Motors" in the VI
path: Robot Main.vi
<time>16:35:51 03/12/2011
FRC: The loop that contains RobotDrive is not running fast enough.
This error can occur if the loop contains too much code, or if one or
more other loops are starving the RobotDrive loop.
No Change to Network Configuration: "Local Area Connection"<noNICConfig>
I/O unit not detected or not installed correctly.

We replaced the solenoid breakout with one from spare parts and it did
not fix the problem. They also tried a number of other things without
success. Any ideas or help would be greatly appreciated, we can send
you the code if that would help.

Thanks in advance for the help, Team 1973

[Mark McLeod]

Offhand it looks like you have the wrong enumeration type feeding your Solenoid vi's in Teleop.

It looks like a code problem rather than a hardware problem.

I didn't realize you were having problems at WPI or I would have taken a look, too.

If you would zip your LabVIEW project and post it, we can help you figure it out.

[Mark McLeod]

P.S.
I just saw the code and they had accidentally destroyed the library code within Solenoid Set RefNum and Get RefNum.

[WizenedEE]

That reminds me of this time I wanted to not square the inputs on the drive code (before I realized that option doesn't do anything for mecanum..) so I edited the open vi to have that option. Eight weeks later, we were trying to write some new autonomous code for a demonstration and since our programming laptop's battery was dead we used that same computer. In short, I had to reupload the old code

Why do so many functions say they've been modified when you use them and don't modify them at all? Is it an automatic update sort of thing?

[Mark McLeod]

Originally Posted by WizenedEE

Why do so many functions say they've been modified when you use them and don't modify them at all? Is it an automatic update sort of thing?

Sometimes it's because it was moved or copied to a new location, not that it changed, but that the path to it changed.