[motorhead1991]

I've read the documentation a handful of times, so I get the gist of it, but there are a couple things I'm stuck on:

This command specifically has me stumped:

Code: Select all

'J'+'R'+n+MMSB+MSB+LSB+CS

J and R are ASCII values, obviously, but no notes are given for 'n', MSB or LSB. MMSB has a note, saying that it should be between 0 and 3, which is what 'n' is in the previous command.

Any clues, hints or tips?

[jsa]

EDIT, REREAD PROTOCOL INFO and chaged my opinion.

Most most significant byte, most significant byte, least significant byte and checksum all bundled together in that order.

[motorhead1991]

n is the number of bytes of data to follow in the range of 1 to 3.

Most most significant byte, most significant byte, least significant byte and checksum all bundled together in that order. Leaveing out M and MM for n=2 and 1.

And you lost me again

[jsa]

Edit; new interpretation of protocol doc below.

[motorhead1991]

Each byte is a hexadecimal number.
N=03
xx xx xx cs
N=02
xx xx cs
N=01
xx cs

I think I see... So I had the command partially correct:

Code: Select all

4a 52 31 33 
J  R  1  3

MSB and LSB are where I get stuck.

[jsa]

Hmm plenty of scope for misunderstanding that protocol doc.

MSB and LSB must be a word address of a chosen bank to read from.

Either n or MMSB must be the bank number and inversly MMSB or n must be how many bytes to read.

Edited above posts, let us know which way works.

[jsa]

I reckon set n as 00, mmsb as 00, msb as 00 and lsb as 00 followed by cs. That should get 256 bytes from the begining of one of the eecv banks.

[sailorbob]

My understanding of it is:

n = number of bytes to read (starting from the address defined by MMSB, MSB, LSB)
MMSB = bank ( 0, 1, 2 or 3)
MSB = high byte of address
LSB = low byte if address

It will probably baulk if you try to read more bytes than there are between the start address and the end of the bank.