You need to translate the whole stacktrace into classes/methods.You might want to use the debug monitor, which does that automatically. I believe you must use nxjconsole via USB to see the converted stack trace.

Unfortunately, I can't really. I don't have a BT GPS device, and I assume that the parser isn't that well written, I guess.It would help to see a dump of all the data returned by the GPS device.

skoehler wrote:Unfortunately, I can't really. I don't have a BT GPS device, and I assume that the parser isn't that well written, I guess.It would help to see a dump of all the data returned by the GPS device.

I've repeated this three times, first time is the dump postedSecond (raised exception about 20 secs from execution) and third time (about 1min from execution) have the same results, changing the exception:

I can't get the same number exception (79), but in this mode is the NumberFormatException too, also in the same line

Why I use LCP over RAW??I use LCP because obtaining data from the gps via bluetooth to the NXT is faster than using RAW mode and for the 2º error i've changed by error and i didn't realiced that till you told me that i've posted a different exception

That is rubbish. A GPS device doesn't understand LCP and never will. Use RAW.

The rest of your posting is confusing. Are you seeing two errors (one on the LCD and one in the output of nxjconsole)?

Pgeorge wrote:Exception: 80string doesn't cat: 147:25....at: 54:281

First and last line of the stack trace is not enough! I need the number (and the corresponding class/method names) after 147:25

Also, the GPS device send a serious of text strings to the NXT. I need that text in order to see when/why the error happens!It might be easiest to connect the GPS device to the PC and somehow receive and log the data there. I assume the GPS device appears as a serial port? That should be easy to dump to a file.

skoehler wrote:That is rubbish. A GPS device doesn't understand LCP and never will. Use RAW.

I read api and api says the same........but it works better in LCP. Why?? I don't know

In LCP, sample code in BTGPS.java updates every second aprox. and the time, longitude and latitude are correctin RAW, same code updates when it wants (5 secs, 10secs, 1 min...)

skoehler wrote:The rest of your posting is confusing. Are you seeing two errors (one on the LCD and one in the output of nxjconsole)?

yes, if i use remote console debugging i get what i've posted in code tagsif i upload the program with eclipse to the nxt and executes normaly, i get the exception and then i uses nxjdebugtool as in the other code tag (i think that i am doing all the steps in right way)

skoehler wrote:First and last line of the stack trace is not enough! I need the number (and the corresponding class/method names) after 147:25

skoehler wrote:Also, the GPS device send a serious of text strings to the NXT. I need that text in order to see when/why the error happens!It might be easiest to connect the GPS device to the PC and somehow receive and log the data there.

I don't know the order the GPS send text to the NXTIf you expalin me how to log gps data into pc, i could do it

Bonus error: new error when doing another test with the remote console (twice)

What sort of GPS are you using? setting LCP mode on a Bluetooth connection means that we are expecting a two byte header in front of each packet, I'd be surprised if any GPS unit sends that header, but I suppose you never know... Certainly the Bluetooth GPS unit I have does not do this, and that actually works fine with the sample app...

skoehler wrote:That is rubbish. A GPS device doesn't understand LCP and never will. Use RAW.

I read api and api says the same........but it works better in LCP. Why?? I don't know

In LCP, sample code in BTGPS.java updates every second aprox. and the time, longitude and latitude are correctin RAW, same code updates when it wants (5 secs, 10secs, 1 min...)

Which device are you using? I want to take a look at the datasheet if there is any.

Pgeorge wrote:

skoehler wrote:The rest of your posting is confusing. Are you seeing two errors (one on the LCD and one in the output of nxjconsole)?

yes, if i use remote console debugging i get what i've posted in code tagsif i upload the program with eclipse to the nxt and executes normaly, i get the exception and then i uses nxjdebugtool as in the other code tag (i think that i am doing all the steps in right way)

weired!

Pgeorge wrote:

skoehler wrote:First and last line of the stack trace is not enough! I need the number (and the corresponding class/method names) after 147:25

I'm afraid, you have to translate those number for me, just to be safe. When I build/link the BTGPS sample, different numbers might be assigned to the classes etc.Also, the stack traces are pretty much the same, so it's the same error no matter whether you're using LCP or RAW.

Pgeorge wrote:

skoehler wrote:Also, the GPS device send a serious of text strings to the NXT. I need that text in order to see when/why the error happens!It might be easiest to connect the GPS device to the PC and somehow receive and log the data there.

I don't know the order the GPS send text to the NXTIf you expalin me how to log gps data into pc, i could do it

Pair the GPS device with your PC. As what kind of device does it appear in the device manager?

gloomyandy wrote:What sort of GPS are you using? setting LCP mode on a Bluetooth connection means that we are expecting a two byte header in front of each packet, I'd be surprised if any GPS unit sends that header, but I suppose you never know... Certainly the Bluetooth GPS unit I have does not do this, and that actually works fine with the sample app...

It might be the case, the two skipped characters don't matter that much in the beginning, since they are at the start of the line.However, it might still be the case that the parser might need some work (skipping lines which have the wrong format, etc.)

Can't find a useful data sheet which shows which kind of data that thing sending. However, it says that thing implements the serial port profile. So you have to pair it with your PC, then a serial port should occur, and you be able to use some terminal program (like hyperterminal, hterm, etc) to dump all the data that this box sends.