&H02 is ASCII for STX, a special char that for some protocols mean "start transmission". Some protocols frame their data payload between chars STX (&H02) and ETX(&H03). These also normally use some checksum mechanism either before or right after ETX.
Of course it could also be a misleading UTF8 header of some kind resulting from raw data to string conversion, but that I cannot tell for sure. You need a good protocol manual and check low-level comms frames. Regards, zxMarce. On May 15, 2017, 10:42, at 10:42, alexchernoff <alexchern...@hotmail.com> wrote: >Hmm eureka, it's 02 53 = 0x53 >Or 02 25 = 0x25... > >Where could that 02 be from? > >Cheers! > > > >-- >View this message in context: >http://gambas.8142.n7.nabble.com/Serial-I-O-with-byte-data-tp58933p58986.html >Sent from the gambas-user mailing list archive at Nabble.com. > >------------------------------------------------------------------------------ >Check out the vibrant tech community on one of the world's most >engaging tech sites, Slashdot.org! http://sdm.link/slashdot >_______________________________________________ >Gambas-user mailing list >Gambas-user@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/gambas-user ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
