@ Brett -
Thanks very much for your reply.
Apparently, I must be working from the wrong version of the documentation. I followed the links from the Eval Kit’s product page through to https://www.ghielectronics.com/downloads/man/File_System_User_Manual.pdf . (The attached screen shot with highlights shows where I got the idea that I needed to place a K parameter after the colon.) Could you point me to the “P35” manual you’re referring to? I’d really like to be working from the correct documentation.
I see in your examples that you’re placing a colon after the I command character itself. I don’t see this in the documentation I have or in the behavior of the ALFAT Explorer for the storage initialization commands. I have been using only a space after the command character.
I have tried three completely generic USB keyboards, from three different manufacturers, and they all behave identically. None of them require any driver. They all appear, when attached to a PC, in Device Manager under Keyboards as “HID Keyboard Device”.
Based on your message and trying several different combinations, I have achieved partial success now. If I do NOT use the colon after the I command, and I USE the either the A or R parameter with NO intervening spaces after the last colon, I get a success code. Otherwise, I get the !02 error:
I K0:A works!
I K0:R works!
I K0: gets an !02 error (no A or R parameter)
I K0: A gets an !02 error (space before A)
I K0: R gets an !02 error (space before R)
I: K0: gets an !02 error (colon after I)
I: K0:A gets an !02 error (colon after I)
I: K0:R gets an !02 error (colon after I)
Ditto for K1.
So, thank you…I’m no longer blocked…I’ll just be sure to use the A or R parameter, no spaces before them, and I’m good to go.
I also wonder why using no parameter generates the error. Open to any ideas of what might be going on.
Incidentally, the V command reports v2.0.0.