USB datalogger

[PARUS]

deleted.

[Peter Florance]

Having a fair amount of experience with the logger and some with MSIII SD logger, I still feel this product is relevant. I might use one with MSIII even because I am not limited by the field count

[Wergilius]

A little upcomming bump, this weekend i'm about to start my engine after some winter work.
Will be very interesting to see how the logging of MS and Innovate AFR/EGT works in-car

[Peter Florance]

Huey
Are the boards still available?

Thanks!

[Wergilius]

After test on a running engine and minor adjustment to firmware it works perfect to import the frd logg with afr and egt



Will be a great tool this summer !

[Peter Florance]

Huey
Any idea as to whether this will datalog MS3?
The block size is 404; not sure if that overflows a variable or not

I tried to add the MS3 pre-1.1 beta 20 signature (MS3 Format 0233.003) to 0.1.1b but it didn't seem to log any data

Thanks

[Peter Florance]

Huey
Any idea as to whether this will datalog MS3?
The block size is 404; not sure if that overflows a variable or not

I tried to add the MS3 pre-1.1 beta 20 signature (MS3 Format 0233.003) to 0.1.1b but it didn't seem to log any data

Thanks

hmm looks like it does:

Code: Select all

byte ochBlockSize

[Huey]

So, I assume you got it working with MS3 ?

Huey

[Peter Florance]

So, I assume you got it working with MS3 ?

Huey

no, but I'm wondering if I can make that variable 16 bit?
I'm not much of a programmer; if I could have soldered something to it, it would have been working by now.

[Peter Florance]

Huey
Any idea as to whether this will datalog MS3?
The block size is 404; not sure if that overflows a variable or not

I tried to add the MS3 pre-1.1 beta 20 signature (MS3 Format 0233.003) to 0.1.1b but it didn't seem to log any data

Thanks

hmm looks like it does:

Code: Select all

byte ochBlockSize

if I say

Code: Select all

word ochBlockSize

will that work?

[Huey]

Should not be a problem just change the ochBlockSize byte to word in the VAR section. You will also need to change the buffsize constant and the databuff.byte[0] and databuff.byte[1] variables as well. If I had a MS3 sitting around I would be able to help more.

Try this:
line 76 buffsize = 504
line 103 word ochBlockSize
line 240 databuff.byte[0] := ochBlockSize.byte[0]
line 241 databuff.byte[1] := ochBlockSize.byte[1]



Huey

[Peter Florance]

Should not be a problem just change the ochBlockSize byte to word in the VAR section. You will also need to change the buffsize constant and the databuff.byte[0] and databuff.byte[1] variables as well. If I had a MS3 sitting around I would be able to help more.

Try this:
line 76 buffsize = 504
line 103 word ochBlockSize
line 240 databuff.byte[0] := ochBlockSize.byte[0]
line 241 databuff.byte[1] := ochBlockSize.byte[1]



Huey

Thanks!
I'll try it this morning!

[Peter Florance]

Should not be a problem just change the ochBlockSize byte to word in the VAR section. You will also need to change the buffsize constant and the databuff.byte[0] and databuff.byte[1] variables as well. If I had a MS3 sitting around I would be able to help more.

Try this:
line 76 buffsize = 504
line 103 word ochBlockSize
line 240 databuff.byte[0] := ochBlockSize.byte[0]
line 241 databuff.byte[1] := ochBlockSize.byte[1]



Huey

I tried that but there must be a user input variable that I haven't fixed
When I review the signatures I get this:

MS1/Extra format 029y3 *********R39
MSnS-extra format 029q *********R39
MS/Extra format hr_10 **********R39
MS/Extra format hr_11b *********R39
MS2Extra Ser GSv24 A174
MSII Rev 2.88500 A112
MSII Rev 2.88600 A112
MSII Rev 2.88900 A112
MSII Rev 2.89000 A112
MSII Rev 2.89100 A112
MS2Extra Rev 1.0.2 A114
MS2Extra Rel 2.0.0 A153
MS2Extra Rel 2.1.0pA145
MS2Extra Rel 3.0.3rA169
MS2Extra Serial330bA172
MS2Extra Rel 3.0.3sA169
MS2Extra Serial321 A169
MS3 Format 0233.003A148

The MS3 should have been MS3 Format 0233.003A404 and it differs by 256 (byte)
Any ideas?
Thanks!

[Huey]

Are you hard coding the new signature string at the end of the source code or entering it as a user signature string with the "E" command? I see a problem with the "E" command on line 776 and 808 where it says EEPROM.readByte and EEPROM.writeByte.

Huey

[Huey]

Oh, I see bigger problem the signature table is defined as "byte". I'll see if I can come up with a fix.

Huey

[Peter Florance]

Oh, I see bigger problem the signature table is defined as "byte". I'll see if I can come up with a fix.

Huey

Yes hard coding.
Thanks; this will come in very handy with MS3!

[Peter Florance]

Oh, I see bigger problem the signature table is defined as "byte". I'll see if I can come up with a fix.

Huey

Is it something I can change?
I don't mind looking and compiling

Thanks!

[Huey]

Sure, you have the source code. It would probably be best to split up the signature table and use the ID to offset into a new table defined as word that contains the byte count. By doing this I think it would require less reprogramming and save memory space because you are not defining the entire table as word. I have been meaning to work on it however, spring is here and I have so much to do. You can also change the ID numbering to something that makes more sense as a offset. Hope this helps.
Huey

[Vanhoe]

Hello

Glad to see this is still going on.
Are there any units sold to the vendors of MS in Europe?

Is it possible to change from RS232 connector to usb connection with the MS unit?
Does a a usb to RS232 cable work both way's?

Ivan

[Huey]

There are no vendors. You can buy them direct from me and I have sold several units out of the country. Just send me a private message with your address and I will give you the shipping cost.


The USB port only works in one direction.


Thanks, Huey