Help please (OHIO)

[Robohobo]

Would anyone be able to help our rookie team out? Our school is about an hour south east of Columbus. We are having massive issues programming with labview. We haven't been able to even get the motors to work. We need someone with Labview experience. We don't have any mentors, and no one here has ever used it before. We usually work 230-730.

[Hadi379]

If you message me your information, I can put you in contact with one of our students that is our lead programmer for our team. Our team is just outside of Youngstown, OH, team 379.

[Dave Campbell]

Looks like you're in very capable hands with 379. You can always contact Jimmy Nichols - Ohio Senior Mentor at jnichols@usfirst.org. He also reads CD and will likely contact you. If you have specific questions - you can PM me here, and among all of your great neighbors, we'll certainly get you the help you need.

[arizonafoxx]

The first place that may help you out is:
http://www.frcmastery.com/

That is how I taught myself how to code in labview. The 2011 videos are close enough to use this year and are a good place to start. After that I would look on:
http://team358.org/files/programming...2009-/LabVIEW/

Team 358 has been generous enough to provide examples galore to help everyone out. This is the second place I look if I need help. If neither of these help you with a specific problem, the CD community is the best resource as you are already finding out.

We are here to help and want you to succeed.

[mathking]

We are located in Dublin on the NW side of Columbus. I think that Dave Campbell is correct, you are in capable hands if 379 helps you out. If you need some more help we can help you out. I don't know about getting someone down there in the next week though. We are already committed to visiting several other teams' sites this week. We would be happy to help via phone or skype w/screen share and you would be welcome to bring your bot up here if you wanted and we could help you trouble shoot.

From what you said, it looks like you were able to get the Classmate set up and to put the Labview image on the cRIO? Are you at the stage of trying to get the default code to work?

[matthewdenny]

I'm the mentor for team 4165 (the original poster is one of my students).

I really appreciate everyones help in this. It is our first year, and right now it is just me and one other teacher, and the software is raking us over the coals. Perhaps I should explain the problem. We have imaged the CRio, we have set up the camera, bridge, and Kinect. We can ping the robot from the development computer, so I think the connection is good. We open LabView, and the default Robot Main .VI. we click run, and then nothing happens. We move joysticks, but no go. The Jaguars continue to blink yellow, and don't go red or green, and the motors are stationary. We have already re-made the DB37 cable. We are getting messages about a "Watchdog", but I don't know if this is the problem or not. Even if we can fix this, I still think we need someone to help us get started, because after looking at the code for four hours yesterday all we have really established is that we don't understand LabView. (But thank you very much for the resources you have provided, we will work on them)

Mr. King we may be taking up your offer and stopping by. What times would be best for your team?

[mathking]

Mr. King we may be taking up your offer and stopping by. What times would be best for your team?

We work Monday and Thursday evenings (6:30 - 9:00) and Tuesday and Wednesday after school (3:00 - 5:00) and Saturday (9:00 - 4:00). Any of these times would be OK. But we could probably arrange to do any day after school if it works for you. If you let us know when you could make it we can arrange to have someone with LabView experience here. (We are using Java, but one of my lead programmers has is experienced with LabView and a couple of the mentors are as well. I just need to make sure they are here and not off with another team.) If it is a watchdog issue we ought to be able to clear it up pretty quickly.

I will send you a PM with my contact info.

[Mark McLeod]

Originally Posted by matthewdenny

We have imaged the CRio, we have set up the camera, bridge, and Kinect. We can ping the robot from the development computer, so I think the connection is good. We open LabView, and the default Robot Main .VI. we click run, and then nothing happens. We move joysticks, but no go. The Jaguars continue to blink yellow, and don't go red or green, and the motors are stationary.

Did you also start the Driver Station application and Enable the robot?

[Hadi379]

matthewdenny,

Take a look at what Mark Mcleod posted and can you confirm that the driverstation is open and you have enabled the robot through the driverstation?

[Jimmy Nichols]

Matthew,

Looks like Columbus would be the nearest teams to you. Greg and his team would be an excellent resource for you. If you are unable to get connected with Greg, schedules etc. Please let me know ASAP, I can get you in touch my labview guy. He is a certified LabVIEW Developer and has been mentoring our Team for a while. I also have some connections in Columbus with certified LabVIEW developers. Please let me know either way so I know your issues have been taken care of.

I also see you are attending the Buckeye event, please join us down at the Queen City event and bring your team. It would be another opportunity for them to see somr FRC action.

[j.cole]

What I'd start with is making sure that the cRIO has been imaged properly.
1. Connect the robot to the development PC through port 1 on the cRIO.
2. Make sure to turn all other NIC's on the development PC off. (wireless cards, other ethernet ports)
3. Turn your robot on.
4. Open the Driver Station
5. Click the diagnostic tab on the Driver Station window.
6. Wait for the cRIO to connect.
7. The DS version should be 11.30.11.00
8. The cRIO version should be FRC_2012_xx.zip
9. If thats all good post back.

[rsisk]

Also, make sure you have fixed your DB37 cable (wide ribbon cable from cRIO to Digital Side Car) per the instructions linked below. The symptoms you describe seem to fit this problem.


DB37 Fix

Be sure to flip the male end of the cable, not the female end as per the instructions. Less chance of damage to the connector.