Re: Debugging Techniques
 

I do not know if this will solve your problem, but for me the cRIO will only outputs to the compiler or debugs if it has a static ip address. (Windows has a dynamic ip address by default) When using a dynamic ip address, our computers never get past the "Waiting for cRIO to reboot (##s)"

Info on setting up static ip address

You should set your ip address to: 10.XX.YY.ZZ
(XX.YY is team number [123 -> 01.23] ; change ZZ so that no two computers on the network share the same address)

Re: Debugging Techniques
 

we have been able to deploy code so that means our ip address should be set up correctly. also, as i mentioned i CAN run the debugger via an ethernet cable, just not wirelessly.

i was watching the java 101 kickoff workshop video recently (posted on the first website) and in the powerpoint presentation, the speaker mentioned that they were having problems getting the wireless debugger to work. maybe it's an issue with first that's not been solved yet??

Re: Debugging Techniques
 

I guess I wasn't clear on what I was saying for what happens (at least for me) when using wireless: You can still deploy with a dynamic ip address, but you need a static ip address for println() and debugging.

Re: Debugging Techniques
 

I'm not sure what you are basing this claim on, but it's not accurate. It is the case that for debugging you need to configure the IP address (regardless of how it is assigned) in the target connection to debug.

-Joe

Re: Debugging Techniques
 

As I said in my posts: from my own experience deploying/debugging.

Could you please explain this more completely? (Specifically how to do this without a static ip address)

Re: Debugging Techniques
 

Our wireless solution is a 100 foot Ethernet cable. :D

Re: Debugging Techniques
 

NetConsole (the basis of prints) broadcasts, so the IP doesn't matter.