KDFtool/KFDshield timeout

[emanuel32804]

Hi all,

I have been burning for one of the KFDtools but since parts availability is zero, I haven't been able to get my hands on one until I found out about KFDshield. I purchased one, with the addition of the 3.5mm to hirose cable and an NTN8613C keyload adapter. I have tried it on an XTS5k and 2.5k so far and I have not had success with either. I downloaded the SW and FW from the KFDshield github and the software sees the shield just fine. The self test passes but the detect MR test and all other functions of the software fail with the error "Error -- timeout waiting for data". I have also noticed that the sense light never turns on but I do have power and activity staying on steady. Has anyone had any luck out there with these things? I hate to have wasted my money, but it seems like I've read good things about this product. If anything jumps out as wrong to anybody (like the steady activity light?) please let me know.

Thanks,
E

 

[wgbecks]

I have the original KFDTool along with the KFDShield that both work perfectly! Do either of your radios display "KEYLOADING" when attaching the keyload adpater to the radio while making sure that the Hirose cable is connectd to the KFDShield and that the KFDShield is connectd to your PC's USB port?

The "KEYLOADING" reponse should occurr immediately upon powering the KFDShield via the USB cable attachment to your PC. Conversely, it shoud go away upon disconnecting the USB cable from the PC. Failue to indicate "Keyloading" would be an indication that you may have cable issues, that the keyloading adapter is deffective, that the UCM in the radio is defective, or that the Secure Configuration in the radio's codplug is not optioned for "Secure Equipped" and/or the Secure Type isn't set to "Hardware".

The above are good first steps toward diagnosing the problem.

 

[WX4JCW]

Make sure you have the Correct Com port selected, you should be able to connect to the Arduino/KFDShield without the radio
generally I get this error if the Com Port is not correct

also make sure the Arduino itself is flashed with the proper KFDShield Firmware, it is different than KFDTool

 

[emanuel32804]

Excellent info here. I'll check the radio configs about those last two. I'll also meter out the cable/adapter to see if they're good. I do not get the keyloading message on the screen, which was a point of concern. Thanks guys

 

[WX4JCW]

It may be the Hirose as well, in my experiences at least with APX the radio should go into keyloading mode with the Hirose cable connected to the KFDShield even if the software isnt running, make sure you see the Blue and green leds are on the board as well

 

[Giddyuptd]

Be sure your radio adapters aren't cheap ebay stuff. You'll need the proper adapter for radio. Specially for the apx.

 

[emanuel32804]

Unfortunately I don't have an APX, wish I did though haha. I do see the green and blue leds on the board though. Still haven't had a chance to try the previous advice. Will update when I do. Thanks all

 

[Giddyuptd]

If your accessory connector are good (not the Hirose stuff the audio jack accessory adapter for radio) try reinstalling the kfd software. If it isn't reading and hardware has been ruled out its a driver issue or a setting on the syatem itself.

 

[emanuel32804]

Ok we got success! Hardware secure type was not selected and that was preventing this from working. Instantly pops up with "keyloading" now as it should. Thanks all!

 

[emanuel32804]

Actually I'm noticing now that while my first radio was able to be programmed, the rest (which are identical in HW and codeplug) are having some trouble. They go into keyloading mode but the software doesn't detect them when I do Detect MR. Can't read or write keys either

 

[mancow]

Are you checking to be sure the correct comport is selected? I noticed it will at times reset if power to the arduino glitches at all.

 

[emanuel32804]

Yeah the self test works just fine. It continues to work just fine on my first radio, just the rest it doesn't.

 

[kv5e]

I have found that if IDE is installed, the COM port is persistent. (WIN 7 and WIN10)

 

[efficacious]

Yeah the self test works just fine. It continues to work just fine on my first radio, just the rest it doesn't

I have the same issue, were you ever able to get this figured out?

 

[marcotor]

I have the same issue, were you ever able to get this figured out?

Did you try the suggestion to check the COM port? This is the #1 issue that people have, assuming the software/hardware automatically detects the proper port, which it does not. Check Device Manager.

 

[efficacious]

Did you try the suggestion to check the COM port? This is the #1 issue that people have, assuming the software/hardware automatically detects the proper port, which it does not. Check Device Manager.

I have a KFDshield, a hirose cable that came with it, and an NTN8613C keyload adapter. It detects the shield as an Arduino Uno on COM10 in Device Manager. The KFDtool software recognizes the shield, and the self test always passes. I have one XTS2500 that keyloads fine with no issues. My two other XTS2500s show KEYLOADING when plugged into the shield, but the software gives me a 'timeout waiting for response' error when I try to DETECT MR or load a key for both of them. I have checked and rechecked the security settings and the feature set on all three radios, and theyre the same. Both of the two radios that wont keyload have had keys loaded onto them before, and have fully updated UCM and firmware. I have also tried multiple versions of the KFDshield firmware and software.

 

[furdog58]

Does the UCM have the Encryption Algorithm loaded that your trying to load keys for. I ran into that with a key type mismatch.

 

[efficacious]

Does the UCM have the Encryption Algorithm loaded that your trying to load keys for. I ran into that with a key type mismatch.

Yes, both radios that are not keyloading now, have had aes-256 keys loaded on them previously. The service mode still shows KG1 AES-256.

 

[furdog58]

Also try, When you have everything hooked up and you try and load a key and you get the error again, cycle the power on the radio with the cable connected to the radio. then attempt to load the key again. I have had that issue before.

 

[efficacious]

Also try, When you have everything hooked up and you try and load a key and you get the error again, cycle the power on the radio with the cable connected to the radio. then attempt to load the key again. I have had that issue before.

I get the "Error -- timeout waiting for data" error, like I would get if no radio was plugged in. I get the same error when I try to "Detect MR" in the "Utility" tab. I tried the powercycling again, and I got the same error.

The two XTS2500s that wont keyload show "keyloading" on the LCD even when the KFDshield is unplugged. But the XTS2500 I have that will keyload successfully does not show "keyloading" on the LCD when the KFDshield is unplugged.

I also get "Error -- invalid response length" when the radios that wont keyload are powered off and I try to load a key.