ALDL Logger Support Thread

[VL400]

It was the name of the listen to data command, looks like the A5 was missed when I changed to 'DataProcess' from 'ProcessData' to make it follow the same format as 'DataRequest'

Attached is the fixed one and shows your log ok

[kojab]

VL400 You saved the day again. I was looking for something simpler.

Thanks.

[kojab]

I'm trying to get the ALDL logger to work with a W74 Kalmker bin. It reads the 128k nvram ok but just can't get it to write to it. Logging is fine. I think it needs some code changes similar to the modified factory RT bins.

If you need the W74 bin let me know.

[VL400]

Its possibly just the ALDL mode in the ADX - can try 0x0A for 8 byte write (RT modded bins), 0x0B for 8 byte write on 12P or 0x0C for 128byte write on 12P. I think W74 is 0x0C which will be 128byte write in the logger - I doubt that the PCM will allow it

Its likely going to require a firmware update to support Kalmaker.

[kojab]

ALDL Logger read and write to NVRAM works perfect with CFZF_mod.bin (RT modded) in VT V8 PCM Service # 16234531

CJYM.W74 and std factory CFZF.bin will only read NVRAM. It goes through the process of writing but no changes occur to the NVRAM.

Can't find these bytes in the ADX "can try 0x0A for 8 byte write (RT modded bins), 0x0B for 8 byte write on 12P or 0x0C for 128byte write on 12P. I think W74 is 0x0C which will be 128byte write in the logger"

My feelings are if it works ok with CFZF_mod.bin then similar mods could be made to CJYM.W74

Your thoughts.

[Jayme]

hes talking about the packet offset in the "cal details" bitmask. older adx's have 0x0 but the newer ones at the start of this thread use it to set the aldl mode.
its not about modifying the kalmaker bin, as kalmaker just uses a different write mode to the other RT bins. the logger just needs to be told how to write to it properly. one of vl400's bult in modes might work, but if not, then to get it working a new firmware for th elogger will be required to get it working.

[VL400]

The write mode is in the CalDetails item - same one where you set the start/end address.

I think the issue will be the 128byte packets for mode 0x0C writes- it may spit it. 128byte writes are something I added in 12P using the NVRAM as a serial buffer and made it mode 0x0C. The VT and later PCMs have a 128byte buffer in RAM but thats the total packet without any overhead like the address. Might need to have a configurable item for write packet size to support Kalmaker if it does not work.

EDIT: Beat me too it!

[Jayme]

from what i understand from talking with antus, it probably wont work, as w74 uses mode 0x0C for write, but its max packet size is 16 bytes. so to get it wokring, as VL400 said, a new config item would need to be added so you can use mode 0x0C but with 16 byte packets.

[kojab]

Thanks VL400 and Jayme for your replies. The ALDL write mode was set originally to 0A which explains why the RT modded bin worked perfectly. I have tried 0C and 0B and both don't work.

I will have to continue updating the W74 bin using the eprom burner until new firmware comes along. Lol I have been doing it this way for over 20 years so a while longer won't hurt.

Thanks guys for your efforts, especially the quick responses.

[kojab]

Question, can the ALDL logger be also be powered by + 5 volts form pins 8 & 9 on the DB9 connector. I assume it can as mention to a "standard DB9-serial cable (not supplied) is used for 808 connection". I am considering attempting connecting the ALDL logger to a Kalmaker DB9 ECM. Just have to add + 5 volts to pins 8 & 9. Maybe add a 5 volt reg inside the kalmaker ECM.

Decided not to try the above without consulting the designer of this great little device. Thanks VL400