On 02/12/12 08:18, Andrew Errington wrote:
On Sun, 12 Feb 2012 21:56:01 Andrew Errington wrote:
Ok, some partial success.
I know it's bad form to reply to one's own emails, but I ran VX2 Commander 3 more times. First time 95%, second time 99%, and last time 100%. Here's the short log from VX2 Commander:
Data Received. Length: 10 Data: 41 48 30 31 35 24 E8 01 00 24 First Block: [41 48 30 31 35 24 E8 01 00 24]
CPU: 01 00 USA Mod Setting: E8 (Freeband)
Sent: 06 Acknowledge... Data Received. Length: 9 Data: 06 E8 01 02 01 FF FF FF FF Second Block: [E8 01 02 01 FF FF FF FF] Sent: 06 Acknowledge... Data Received. Length: 32578 Data: 06 02 01 00 00 02 ... FF FF FF FF C9 FF 99 Third Block: [02 01 00 00 02 03 ... FF FF FF FF C9 FF 99] Time: 46.58594 seconds. Calculated Checksum: 99 Checksum OK. VX-2 data downloaded successfully! Port closed.
The progress bar was a little jerky. Should it be smooth? Also, it took almost a minute. Should it be faster?
Not nessesarily, but I've had about the same experiences running VX Commander in wine, it doesn't work well if at all. I actually gave up and made a windows XP VM to run it when I was using it.
My radio is still sitting showing 'TX' on the display. After cloning is it supposed to go to normal operation, or show 'DONE' or 'FINISH' or 'OK' or something? Or should I just turn it off?
I tried the cable *without* the diode, but it didn't work, so I'll keep it there for now.
Now that I have established communication I need to hack on chirp. Remember, so far, all I have done is copied the VX7 code to VX2r, and verified the baud rate. If I run it I get a progress bar (hooray!) then 31 seconds later an error: Checksum Failed [0592-0610 (@0611)]
All in all your work from here shouldn't be too hard. Set something in memory 1, and figure out how many blocks of data the radio actually sends (which can be done with VX2 Commander). Then dig into the file VX2 Commander makes with a hex editor and find the offset of the start of the memory locations. Then tell vx2.py how large the radio image is and the offset of the memory locations and give it a try. After that it's all bug fixing but the vx2 should be really close to the vx7 iirc.
-Rick WZ3RO
Progress.
73,
Andrew ZL3AME
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel