On 2/19/2012 8:50 PM, Mark Wieder wrote:
Len-
Sunday, February 19, 2012, 5:25:32 PM, you wrote:
LC doesn't know from uints. Your best bet is to read them as chars (or
more precisely as bytes), as you're doing in your second example.
I thought this was true until I looked it up in the diction
Len-
Sunday, February 19, 2012, 5:25:32 PM, you wrote:
>> LC doesn't know from uints. Your best bet is to read them as chars (or
>> more precisely as bytes), as you're doing in your second example.
>>
> I thought this was true until I looked it up in the dictionary. It
> states that those are v
On 2/19/2012 6:29 PM, Mark Wieder wrote:
Len-
Sunday, February 19, 2012, 3:34:41 PM, you wrote:
I'm trying to read data from a socket. The data is Modbus/TCP. The
first routine I tried is
read from socket pSock for 3 uInt2s
LC doesn't know from uints. Your best bet is to read them as chars
Len-
Sunday, February 19, 2012, 3:34:41 PM, you wrote:
> I'm trying to read data from a socket. The data is Modbus/TCP. The
> first routine I tried is
> read from socket pSock for 3 uInt2s
LC doesn't know from uints. Your best bet is to read them as chars (or
more precisely as bytes), as you'
I'm trying to read data from a socket. The data is Modbus/TCP. The
first routine I tried is
read from socket pSock for 3 uInt2s
This gives me no data (both "it" and "the result" are empty). I know
the packet has been received and there is data after these 3 numbers.
If I change this
to:
