LabVIEW project crashing

[koo_04]

I am using the driver station.EXE on Developer. It is finding the robot and everything just perfectly fine.

My problem is that now when I try to debug the program I am using, the program crashes and just stops at a standstill. When I probe the wires and junk, it just shows no data going. Like it stopped it self. I had it working a few days ago without any problems. I have not changed the code at all since then.

The driver station says the code is there and working, but LabVIEW says otherwise... Please help!

[FLash_NI]

Hi koo_04,

Do you have the latest update of the driver station?

Do you see the same result when you run the basic 2010 Game Robot Project from the Getting Started screen from LabVIEW?

thanks
FLash

[koo_04]

Okay, so I went through some very long and tedious debugging.

I found out that it only crashes when I try to add anything that has to do with the analog stuff. I added 4 analog in's (With references) to the "Begin.VI," and some to the "Finish.VI."

I created a new project and restarted from scratch and ran every step I added something. When I added the analogs, it dies. Anywhere and any how I add them. Any clues why?

[StephBrierty]

You might want to call into NI support for this in case it is a bug we'll want to get it fixed ASAP and if its something solveable it'll be much easier to do over the phone. Number and times are below. Thanks!

[Alan Anderson]

Originally Posted by koo_04

When I added the analogs, it dies. Anywhere and any how I add them. Any clues why?

You haven't given us a lot of information to go on. Can you show us an example of where and how you added them? Maybe there's something you're doing that isn't how the analog library expects it to be done.

[kamocat]

Have you checked that the analog modules are completely plugged in?
Have the devrefs been opened with an "Analog Open" VI, not a constant?

[Greg McKaskle]

Just to add for the information requests, please define crash. If you have a dialog or message, what does it say, when did it come up. Sometimes a picture is very helpful. If no dialog, does the program go away, what do the buttons on the panel look like, etc.

Also, if you believe that it is Analog that is an issue, you may want to try an example that does analog.

Again, it may be best to contact support.

Greg McKaskle

[koo_04]

I am not getting any errors at all. That is my issue. This is the steps I take after adding the analog stuff.

Start driver station.exe

Temp Deploy code (press play at the top)

I probed some stuff to make sure it was working. It was.

I pressed enable on the DS.

All my probes then stopped working completely.

I also did the same thing in the debug watching thing. (The light bulb). It stopped running after the 2nd loop, after clicking "Enable." All the little dot indicator things (dots that run along the steps) just stopped moving. I get no error messages and I am still able to stop the program (Clicking stop at the top) and re-do it all over again. So it is not the LabVIEW program itself.

[Alan Anderson]

Originally Posted by koo_04

This is the steps I take after adding the analog stuff.
Start driver station.exe
Temp Deploy code (press play at the top)

Press play at the top of what, exactly?

You need to run the Robot Main vi in order for the program to execute properly. If you just run Teleop.vi, or anything other than Robot Main, it won't work.

[koo_04]

At the top of Labview. I will get pictures up when I can. We only work on the robot 3 days a week.

I am using Robot Main.

[kamocat]

Uploading the code itself would work as well.

[Greg McKaskle]

This is why I asked what the crash was. If you can still click on buttons in the LV editor, it is not crashed. If it responds and the code on the cRIO stops running, then it also was not crashed or hung.

If it repeatably stops doing what you want when the program reaches a certain point, perhaps you should inspect that code, post a picture and ask questions about it. If that code does something timed such as delay for 60 seconds, and if it does it during the teleop loop, that would explain your symptoms.

Greg McKaskle

[koo_04]

Okay, so after some frustration attempts, yelling, and asking the program to work. It still did not work... BUT I gave up and started from scratch with a new project and after a while it started working again.

For now, I believe the problem is solved. If I end up running into this problem again, I will be back with more details and such.

Thanks for the help, you guys are awesome.

I hope to be much better with labview at some point in time soI will be able to help the people who run into problems like this also.

Thanks again.