The timeout period is in mS (like most of the time values in leJOS). The docs need cleaning up for this...

I've tried to reproduce the problem but all of my tests work fine. Do you still see the problem with your code? If so can you add an extra drawString call immediately after the openAny call just to confirm that it is this call that is hanging.

It really is behaving unexplained at the moment. If I sit and wait for a timeout, it seems to go into never never land, not executing the code after the openAny, and not opening a remote console either. If I connect a remote console (within the time out period), the code following executes as expected.

Unfortunately for me, after 2 days, I've hit my first Java exception (after the expected initialization routine runs), and have gotten nowhere figuring out how to understand it. I see on the web page talk about using command lines, which I do not do, and I guess the IDE integration stuff has a ways to go. Is there even a way to set linker options in Eclipse? I haven't found them. And when I do, then what?

I love what you guys did with LeJOS (remember I even tried to copy it to C# one time but the regulator thread differences between Java and C# got too complicated for me and I gave up). But I wish the development experience was more in line with android, which is also a separate remote jvm. It may be just too complicated for me at this time as some health issues severely limit my patience. Again, at this moment, I'm ready to give up and go another direction, but to the best of my knowledge, I've already tried them all and they are just too archaic.

spiked3 wrote:I see on the web page talk about using command lines, which I do not do, and I guess the IDE integration stuff has a ways to go.

At the moment, nxjdebugtool (the command line tool) is the only way to fully decode exceptions such that you do not only get the name of the method but also the line at which the exception happened. What is that "which I do not do" part of your sentence about? Are you refusing to use the command line?

There is currently no support in Eclipse to decode Exceptions for you. However, nxjconsole support decoding them, if you enable the remote debug monitor.However, the debug monitor cannot be used in a program which already RConsole as far as I'm aware.

spiked3 wrote:Is there even a way to set linker options in Eclipse? I haven't found them. And when I do, then what?

Verbose linking will show a list of classes and methods and the number assigned to them. That way, you can decode which exception happened and in which method it happened, which method that method was called from etc.

spiked3 wrote:I love what you guys did with LeJOS (remember I even tried to copy it to C# one time but the regulator thread differences between Java and C# got too complicated for me and I gave up). But I wish the development experience was more in line with android, which is also a separate remote jvm.

Are you being serious!? Android is a project heavily pushed by a big company called Google. leJOS is an entirely community driven project. And the number of core developers, spending their free time on leJOS, is so low, you barely need the fingers of your second hand to count them. Also, a modern Smartphone and the NXT are two completely different platforms, which differ in so many way - you're really comparing apples and bananas here.The good news is, that a remote debugger based on JWDP has just been merged upstream. However, I can't tell you when IDE support will be available.

Yes, I am serious, I do not use punch card machines or command lines. If I did, I would run linux. I know many do, good for them, not for me, been there done that, NEVER going back. Most of you were probably in diapers in my command line days I'm too old for that now, I can barely remember where I left my reading glasses, never mind a cryptic command line.

I was just getting ready to be sure I had the latest plugin, glad to hear a new one is available. I had tried those 'enable verbose' options, but I saw nothing different as a result. I also tried the remote debugging monitor, but haven't had luck yet. Maybe I will with new plugin? There seems to be some timing order, as to when to run what and try to connect who - that usually lead to a locked brick I have to take the batteries out of.

I said "I wished the the development experience was more like android" not that I expected it to be. You guys do great for a small audience. Given time, I'm sure it is on everyone's wish list, no? Please do not take anything I say as a criticism, I am in awe of the work that's been done and freely distributed. It just does not fit ME, and again, somewhat from health issues. I don't expect my case to be typical.

http://lejos.sourceforge.net/nxt/nxj/tu ... ugging.htmsection: Remote Debugging"If you use the variant of open with a timeout, it waits the specified number of seconds and if the debug monitor has not connected, proceeds without debugging. If the timeout is zero, it waits indefinitely."

BlueCove version 2.1.0 on winsockunable to read reply packet lengthException in thread "AWT-EventQueue-0" java.lang.NullPointerException at lejos.pc.tools.NXJMonitor.actionPerformed(NXJMonitor.java:211) at javax.swing.Timer.fireActionPerformed(Timer.java:312) at javax.swing.Timer$DoPostEvent.run(Timer.java:244) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:705) at java.awt.EventQueue.access$000(EventQueue.java:101) at java.awt.EventQueue$3.run(EventQueue.java:666) at java.awt.EventQueue$3.run(EventQueue.java:664) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:675) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:211) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)

at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)

at java.awt.EventDispatchThread.run(EventDispatchThread.java:90)-------------------------------Is this just the result of running as not intended?

BlueCove version 2.1.0 on winsockunable to read reply packet lengthException in thread "AWT-EventQueue-0" java.lang.NullPointerException at lejos.pc.tools.NXJMonitor.actionPerformed(NXJMonitor.java:211)

That's most likely a consequence of NXJMonitor connecting to a NXT not running an LCP responder but RConsole instead.Someday, that will be fixed as well and there will be a nice "cannot connect to NXT" message.