Batboard

I have Syntor x9000 Vhf with HCN1033D control head when I program control head it show "verification error" what happen?

Too fast of a programming computer would be my guess, i always had that happen when i tried using my programming laptop at its faster speed.

The 486 laptop i had allowed you to switch between 25 and 50Mhz, at 50 it would fail the verify, at 25 it would program them night and day. I always forgot a couple times to switch it back to 25Mhz before doing a X9K and got that as a reminder.

How fast is your programming computer? It has to be SLOW for the X9K.

I might as well mention that you also need to be using a machine running in true DOS mode, not a windows machine with the DOS window open.

It's a picky radio, I've also ran into issues that required running the laptop off of real AC power instead of an inverter.

I just burned a 2m/70cm antenna in two with one of these radios. Pictures to come...

MDC1200 board also generate this error when programmed, but the board programs ok. Never could figure out why, but since everything worked..

every time i've programmed a x9000 for mdc and found out that the board wasn't installed it always gave me a fail code. or are you saying the board is defective?

One basic thing to keep in mind is the 1033D control head is normally equipped with a 2K eeprom. If you are trying to program more than 32 modes, then your efforts will fail because you need an 8K eeprom.

When you read the radio, did you receive eight blocks or 32 blocks?

George

I know it is 2K eeprom I can prog radio but for control head is not.I can read control head if I not change any thing I can prog it back to control head.but if I edit any thing in codeplug it dosn't work.

Keep in mind that the X9000 programming software writes data in the blind - that's why the verification stage is there. It blasts the data into the EEPROM, and then reads it back to see if what it blasted in is the same as what it gets back. If you read and immediately write with no changes, even if it didn't "write" anything verification should still pass. Since it fails when you're trying to write with changes, that could be a sign that the data is not indeed being written, or not correctly. Could be a bad EEPROM in the head, I've seen that happen before. You could also try swapping out a head if you have a spare. This will help to narrow down cable problems, etc.

akardam wrote:Keep in mind that the X9000 programming software writes data in the blind - that's why the verification stage is there. It blasts the data into the EEPROM, and then reads it back to see if what it blasted in is the same as what it gets back. If you read and immediately write with no changes, even if it didn't "write" anything verification should still pass. Since it fails when you're trying to write with changes, that could be a sign that the data is not indeed being written, or not correctly. Could be a bad EEPROM in the head, I've seen that happen before. You could also try swapping out a head if you have a spare. This will help to narrow down cable problems, etc.

That's really interesting to know because the radio I was trying to program from inverter wasn't verifying, but it did seem to take the programming on one attempt.

Make sure your programming cable and RIB work together to ground the microphone pin. This is required by both the radio and control head to be able to write to them. If mic hi pin is not grounded the blind write will appear to work, but the verify will fail and nothing gets changed.

http://www.open.org/~blenderm/syntorx9k/progx9.html

Mike B wrote:Make sure your programming cable and RIB work together to ground the microphone pin. This is required by both the radio and control head to be able to write to them. If mic hi pin is not grounded the blind write will appear to work, but the verify will fail and nothing gets changed.

No, the cable is grounded; I found that out the hard way when I noticed I could transmit but had no modulation when it was still living on the test bench.

akardam wrote:Keep in mind that the X9000 programming software writes data in the blind - that's why the verification stage is there. It blasts the data into the EEPROM, and then reads it back to see if what it blasted in is the same as what it gets back. If you read and immediately write with no changes, even if it didn't "write" anything verification should still pass. Since it fails when you're trying to write with changes, that could be a sign that the data is not indeed being written, or not correctly. Could be a bad EEPROM in the head, I've seen that happen before. You could also try swapping out a head if you have a spare. This will help to narrow down cable problems, etc.

So I change control head it can be program.How I can check what bad in old control head.

Sounds like that head just has a bad EEprom. Take the chip out of the control head that programmed correctly and put in the control head that wouldn't program. Then see if you can read it, make a small change like channel name or something, and write back to it. If it passes the verify cycle then it was just a bad EEProm.

Pretty common, i would get one or two out of each batch i worked on with a bad EEprom.

kb0nly wrote:Sounds like that head just has a bad EEprom. Take the chip out of the control head that programmed correctly and put in the control head that wouldn't program. Then see if you can read it, make a small change like channel name or something, and write back to it. If it passes the verify cycle then it was just a bad EEProm.

Pretty common, i would get one or two out of each batch i worked on with a bad EEprom.

EEprom is ok I think it will have something dead on boad I don't have service manual to check it.Long time ago I use Bad rib Try to Program it but it not work when I change rib control is dead