Forums, News and Articles

Sorry about the delay. Preoccupied. Got your more detailed emails as well. I'll reply there (and maybe put up a new version of tcpclient today if there's time.)

It seems that using addpacketstringN chr(128-142) excluding chr(129) and chr(141) dont work. Nor does chr(145-159) excluding chr(157). Very odd. Instead the udpclientcom sends chr(0) when any of those listed numbers are used in the string. All other numbers between 0 and 255 work perfectly. There are 27 numbers that will not send and generate 0`s in the packet payload instead. Any ideas?

So far i have noticed that the error only occurs in the listed ranges above, and those numbers begin with hex $8- or $9- where the - is variable. Some - numbers may work, while 27 do not.

Thanks for the help. I appreciate any advice that can be offered.

--Eric Shufro