Oshonsoft INTERRUPT test

[camerart]

Hi,
I have been having problems with the INTERRUPT section of a program, so had to have another go at improving it. I'm not a confident programmer, so would like anyone to test it on their simulator please.

It PARSEs out VARIABLES from these type of sentences, entered into the SEND STRING of the Hardware UART:

$GPRMC,123519,A,4807.038,N,01131.000,W,W*6A? [STRTIM, STRLAT, STRLON]
$QEIDEG,123,W [QEIDEG]
$REMOTE,12,20,50,W [remvolt,remalt,remdist],?

Cheers, Camerart.

 

[Ian Rogers]

Seems to work fine..

I tested all three sentences.. The strings seemed to hold the correct data.. It appears that the byte locations of the received data isn't filled..

ie remvolt, remalt.. etc... are not populated..

 

[Ian Rogers]

You are getting an error on the last character and the serial port is restarting... You'll need a way of clearing err as once set is always set..

 

[camerart]

Seems to work fine..

I tested all three sentences.. The strings seemed to hold the correct data.. It appears that the byte locations of the received data isn't filled..

ie remvolt, remalt.. etc... are not populated..

Hi I,
Thanks for testing.

A bit puzzling, as mine does fill the VARIABLES, see screen shot.

Can you describe the error that you're getting please. If you mean when the NMEA sentence is being READ, then that one does run on, but the relevant DATA has been READ by then.
C.

 

[Ian Rogers]

The strings are filled... But the byte locations are not... ( locations 70 71 and 72...)

 

[camerart]

The strings are filled... But the byte locations are not... ( locations 70 71 and 72...)

Hi I,
I can't remember what REMVOLT, REMALT and REMDIST are for I'll have to have a think and report back.

Can you explain the You are getting an error on the last character and the serial port is restarting... You'll need a way of clearing err as once set is always set. again please?
C.

 

[Ian Rogers]

I'll check it again.. But the OERR flag is set after transmission.. I think I had this before with Oshonsoft.. It still works okay but you cant send twiceuntill the err variable is cleared..

 

[camerart]

I'll check it again.. But the OERR flag is set after transmission.. I think I had this before with Oshonsoft.. It still works okay but you cant send twiceuntill the err variable is cleared..

Hi I,
REMVOLT, REMALT and REMDIST aren't necessary at this stage, as this is what the REMOTE might send. i,e, Battery voltage etc I'll remove the VARIABLES.

What happens is there's a DATA switch on the PCB, that switches beteen those 3x $Sentences, and set as they are each PARSED.
Actually all 3x messages will be queued up waiting to RX. Perhaps you could try to simulate that, by joining messages with errors in them, and some correct ones, and put them in the SEND STRING box. See if you get the same as I do.
If it looks ok, then I'll add the MAIN program to it. (I didn't notice the OERR problem.)

EDIT: when the OERR bit is set, do you get [ ERROR ] in the Harware UART?
Thanks,
C.

 

[Ian Rogers]

EDIT: when the OERR bit is set, do you get [ ERROR ] in the Harware UART?

Yes but you deal with it...… All I'm saying is.... Once there is an error.. You don't clear it..

If err = 1 Then Hserout "ERROR", CrLf
PIE1.RCIE = 0 'Switch off INTERRUPT

So when there is an error, its final...

 

[camerart]

Yes but you deal with it...… All I'm saying is.... Once there is an error.. You don't clear it..



So when there is an error, its final...

Hi I,
I don't get an error, and you say that it happened before, which is interesting.

I'll try to figure out how to clear it, thanks.
C.