pgmfi.org

i have my serial communication setup only i tried to communicate with the burn1 for example to get the version but no response i want to know what are the commands to communicate? maybe some example code..

did u check the port setting in device manger and did u install the right diver

Right on the website...
http://www.moates.net/zips/firmware/pro ... %20v19.zip

i do have that file for protocols only i send data to the burn2 and i get back ????? not the version... on that file it says to send 'V'+'V' so i don't know if i literally send 'V'+'V' or what does it send or even how to send it....i haven't done serial communication before so don't know how the protocol works exactly...if someone can chime in with some example or even some code..would be great help

i do have that file for protocols only i send data to the burn2 and i get back "?????" not the version... on that file it says to send 'V'+'V' so i don't know if i literally send 'V'+'V' or what do I send or even how to send it, i mean i send in a char array containing that "string" or what?....i haven't done serial communication before so don't know how the protocol works exactly...if someone can chime in with some example or even some code..would be great help

just to make it extra confusing...

RTPComm.Output = Chr(CByte(HextoLong("56"))) & Chr(CByte(HextoLong("56")))

basically output the string "VV" and wait for a response...which should be a 3 byte array; 5, ?, B where ? is the firmware version.

The Protocol guide tells you exactly what to send and exactly what to expect back. Like stated, sending 'V'+'V' or 0x5656 retrieves the three byte version of the product.

thanks guys i finally got it, im doing it on c#, fastcrxsi90's post actually helped me didn't confuse me at all lol

It is very good collection of c#, fastcrxsi90's post. I am doing two project in this topic and it is very useful for me. I can't thank you enough, it is very needed tutorial because of it I am very much appreciate to you.

If you write a routine to send the command byte and the checksum, the checksum for V (char 0x56) is V (char 0x56).

Thats why it sends VV. Saves you writing a routine for writing commands with checksum and one without [+]

good point...V for version which yields V as the checksum.

Yup - it would probably have been clearer if i had mentioned V for version.

It's mentioned in the Moates Hardware Protocols document linked above.