cRIO test drive *OFB* problem....

[NetSkay]

we got the control stuff couple of weeks ago, and today i got around setting it all up, i followed the diagrams and manuals (which i would like to note are incompatible with what came and i also expected a bit more stuff to come in, like more cabling, proper PWM IO cables and etc.)...
when we turned the driver station, everything was tip top, it booted, then i followed the manual and put it in disabled and teleop and shut it off... then we started the cRIO and all components connected to the power board, and everything blinks and works as it should, just like the manual said...
then came the operational test... we started the driver station, then we connected the ethernet cable from the driver station to cRIO ethernet port #1, and started the cRIO and all components, joysticks were connected to driver station USB 1 and 2 also... when the cRIO started the ethernet LEDs started blinking, im guessing DHCP address allocation of some sort, we tried to move the joystick, but the jaguar PWMs just kept bilnking... the ethernet LEDs never idled, always blinked... and at the end no motor movement...

any ideas?!

also whats the deal with the split PWM cables for the jaguars? and no cable for the victor... *sign*

[ATannahill]

Did you enable your robot? Did you wait 30 seconds to a minute for it to resume functions?

[tdlrali]

"split PWM cables for the jaguars" - hmm? You should be using regular pwm cables. A bunch came with the control system, but you'll have to take off the cover on the female side and trim the tab on the male side.

You can also test if you're getting an output by connecting a servo to pwm 1 or 2, and adding a jumper next to the connector on the sidecar (for servo power).

Also, to go through the obvious things:
did you enable the robot with the switch?
what does the DS screen say?

[NetSkay]

u mean after everything is powered on and connected, ill have to wait 30 more seconds after i switch the toggle to enabled?!

im just trying to perform the benchtop tests, and this is the very first one after each of the components have been tested individually... the driver station is directly connected to cRIO on ethernet port #1

[NetSkay]

the screen said the normal stuff
TEAM: 0000000...
MODE: Teleoperational
System Disabled
Battery N/A
*OTB*

then i flick the toggle and system switches to Enabled, but nothing happens, the jaguars still blink, so do i have to wait for like a minute or something before i can try the OTB joystick test or....

[tdlrali]

It takes a while for the DS and cRIO to fully start up and sync after powering up, but if you're tethered it shouldn't take more than a minute.

After that, when you enable the robot, the system should respond almost immediately (+- a few secs).

If you're not getting a response from jags, try using servos in their place (don't forget the jumper!).