Deploy not working.... Help please?

[domoarigato]

Okee... So we thought for a while that we just weren't writing the code correctly, but since it still wants to use all four jaguars that we have plugged in to PWMs 1,2,3, and 4... We think we were never uploading code correctly in the first place... > . >;;;; Uh hm... So now we need to know where exactly we are (Er... rather... where just I am) going wrong here.

So.
We configured the wireless linksys router a while ago, and that seems to work fine. We plug the little black box one up to the electrical board and it connects (flashes and all) in response to the bigger linksys thing that's connected to the driver station. Set the driver station to our team number (1208), updated the firmware/reimaged and all that jazz. Set the RT Compact RIO IP to 10.12.08.02 as was specified in the manual, as well as set the Laptop's Local Area Connection IP address to 10.12.08.06, subnet mask 255.0.0.0, and defalut gateway 10.12.08.04....

Using that orange ethernet cable, we tethered the laptop to the driver station thing and have been (trying) to upload code by building the project and then deploying. Problem is, after we build it, and go to deploy, we just get a screen that says 'Waiting for Real-Time target (RT CompactRIO Target) to respond.' and get a clickable button that says 'Stop Waiting and Disconnect'. Yeahhh. Hm. That just takes us back to the Labview Project Explorer.

Any insight as to where exactly we (I) went wrong? V , V;;;;

[domoarigato]

Hmrrrr.... do you suppose I could just plug the ethernet cable directly into the CRIO port instead of going through the wireless and it'll deploy correctly?

[TotalChaos]

Hmmm..

Whenever I connect my laptop to the DS I've always used just a regular Ethernet cord, not the orange one. (The orange one is the crossover I believe) I think the crossover cable is only needed fro connecting the camera. Try swapping out the orange cord for a regular one and see if that helps.

- Austin

[TotalChaos]

Hmrrrr.... do you suppose I could just plug the ethernet cable directly into the CRIO port instead of going through the wireless and it'll deploy correctly?

You could use a hard wired connection, yes.

- Austin

[domoarigato]

Okay... so I switched out the orange cord for a blue one we had. Disconnected the wireless black linksys box thing from the CRIO port one thing and plugged the blue ethernet cord into that slot. Turned on the electrical board and... after building, still got stuck at that one screen. ('Waiting for Real-Time target (RT CompactRIO Target) to respond.') Not sure why.... But it still doesn't want to let us deploy. V. V;;; And now mechanical's like "WE HAVE TO DRIVE BEFORE LUNCH etc etc" but it's still.... messed up... and I don't know why... > . > *sigh*

[TotalChaos]

Check page 6 of this: http://www.usfirst.org/uploadedFiles/5-FRC_Control_System-Configuration-0-5c.pdf. That's how the wiring should be set up. If it still doesn't work then you may just want to try resetting all the wireless components to factory defaults and reconfiguring them because it would likely be something in their settings that is messed up.

- Austin

EDIT - Oh and also, for the wire going to the wireless router, put it in one of the Ethernet slots, not the internet one.

[domoarigato]

Hrmrrr... Well what's odd is that the wireless router and linksys black box thing work in the way of driving the robot wirelessly when the laptop/DS/etc is hooked up as they specify, though when we (I) try to load code in this configuration, it never seems to have any effect and just likes to give us that one screen ('Waiting for Real-Time target (RT CompactRIO Target) to respond.).... which is why I was wondering if we could just bypass the wireless loading of code and just connect thye laptop directly to the port 1 on the cRIO and deploy that way...

Okay... so Mechanical just brought up a good point: on the cRIO thing... there are all these little white buttons on a blue 'background'... (Safe Mode, Console Out, etc) And all of them are switched 'on'. What do these do and could it be a problem if they are all switched on? Is there a certain way/configuration they should be set to?

[domoarigato]

Have read on (http://www.chiefdelphi.com/forums/showthread.php?t=71783&highlight=safe+mode+switch) that the Safe Mode and IP reset switches should be turned to 'off'...?

[TotalChaos]

I'm actually not sure how the buttons need to be set up, but I attached a pic of how ours are set up. (They all appear to be pressed down on the "off" side)

- Austin

[TotalChaos]

Also, double check your battery. It's happened to me more than once that the battery got so low that all the lights were on but I couldn't download or run anything.

- Austin

[domoarigato]

Rightyo. Tried to just put the blue-ethernet-cabley-thingy directly into the cRIO after messing with the DIPswitch (which sounds like an insulting name to me, haha...) and... still no luck... will try to change the battery; hopefully that will help...? It was getting pretty low. Any certain voltage we should keep the battery above so it works?

[TotalChaos]

Any certain voltage we should keep the battery above so it works?

I'm sure there is, but I'm not sure what it is lol :P

- Austin

[domoarigato]

Haha okee. Doesn't seem to want to work too well under nine volts, so... Probably will try and keep a battery higher than that in.

So it will drive wirelessly okay... So it's not a problem with the wireless that we can think of, as the wireless router is on and blinks and communicates and all, and the robot will respond to the joysticks... albeit we can't load our own modified code into the cRIO, so we can't get the conveyer belt that's on a motor that we want to attach to a jaguar to work, nor can we control the agitator which is connected to a spike (though when that spike is connected to a DIO thing via a PWM cable, it will run in constant reverse, which is fine for the moment, but... would like to be able to control that eventually... which we can't do... but yeah)

Driving practice now... hopefully this programming issue can be sorted out before we have to resort to resetting everything... > . >;;;;

[BLAQmx]

If you are still having trouble connecting to the cRIO from your laptop you may need to disable your firewall and your wireless network card. Windows defaults to the wireless NIC.

[domoarigato]

I have kept the wireless disabled, as yeah, it kept wanting to connect to the school's wireless. Pretty sure the Firewall is disabled as well, but I will check that.

Okay, totally killed the firewall. Dead. Gone.
Hooked up the blue-ethernet-cabley-thing to the driver station, connected that to the big linksys-router-thing, and the black-little-linksys-box to the cRIO in slot 1... and it responds and all.
But.
Still giving me that one screen when I went to deployyy.... ('Waiting for Real-Time target (RT CompactRIO Target) to respond.')

Really have no idea what else could be going wrong. It'll drive, which may satiate Mechanical for a while, but... I don't envision it being for too long...

[TotalChaos]

Hmm... This is just... weird lol. I'll sit down and think about it for a while, I'll let you know if I come up with anything. (For now I have to help my dad replace a busted water heater... The garage is soaked :ahh:)

- Austin

[domoarigato]

So.... you're going to die when you hear what was wrong.

So our team is 1208, right?

Ya.

So our IP address should have been 10.12.08.2.
Or should it have???

Tried 10.12.8.2.
It deployed.

[TotalChaos]

So our IP address should have been 10.12.08.2.
Or should it have???

Tried 10.12.8.2.
It deployed.

Ah. :P

So it was the IP huh? Hmm... Well, since I'm team 2837 I don't need to worry about those leading 0's, so I'm really not sure if you need them or not. (Plus I really don't know much about IP's or networking or anything like that..) If anyone else out there could explain if the leading 0's are significant or not it would be appreciated. :)

Anyway's, glad you got it working! Hope your mechanical team is happy now. :P

- Austin