When sending messages over the COM interface from a RoboPro program (running on an RI) and receiving them on a PC (using ftlib or any other program), you will notice that what you send is not what you receive. The other direction is even more difficult because in RoboPro you have to know which command to expect.
First make sure that you have the hardwareId (00) and the SubId (09) correct, otherwise you won’t receive anything.
RoboPro sends the message value (which you enter as a binary value) directly in binary form (a 16 bit integer) but for the command a translation is used.
For user defined message commands RoboPro accepts strings of which only the first three characters are used. These three characters are encoded in base 40, using the following symbol set:
a-zA-Z -> 1-26 0-9 -> 27-36 + -> 37 - -> 38 ! -> 39
anything else maps to 0.
This means that the command found on the line is 1600 times the value of the first character plus 40 times the value of the second character plus the value of the third character. When there are less than three character, leading null value characters are assumed, so ‘A’ is taken as ‘__A’ (the underscore has value 0 just like space, period, hash etc.
For example the string ‘Ent’ will be encoded as 1600*5 + 40*14 + 20 = 8580, in hex this is 2184 the reserved code for ‘delete’. My guess is that the programmer made a mistake here because he moved all the other predefined commands outside the codespace of 0-63999.
Erstellt und hochgeladen von Ad.
Hochgeladen am 16.1.2008.
Hinweis: Wir vertrauen auf die Sachkunde und Sorgfalt unserer Nutzer. Trotzdem könnten sich Fehler eingeschlichen haben. Eine Haftung für die Richtigkeit der Inhalte können wir nicht übernehmen. Falls Du einen Fehler findest, kontaktiere bitte Ad oder uns.