Netlinx stops sending UDP data at $00 (hex)

MorgoZMorgoZ Junior MemberPosts: 116
Hello,

i´m trying to send a hexadecimal command through UDP port with Netlinx, and it seems that Netlinx stops sending data when it reaches a $00

For example:
I open the UDP port:
ip_client_open(dvCamaraVisca.PORT,'192.168.1.54',52381,IP_UDP_2WAY)

and then send the string
send_string dvCamaraVisca,"$01,$00,$00,$06,$00,$00,$00,$01,$81,$01,$04,$00,$03,$FF"

At the "Diagnostics" i can see that the master just sends $01
And if i try with other command like "$81,$09,$04,$00,$FF", it sends $81,$09,$04

Why?

Thanks for your help!!

Comments

  • mpullinmpullin Obvious Troll Account, Marked for Deletion Posts: 949
    This is a well known problem with the Diagnostics tool. It cuts off strings at the null byte. Your program is probably sending the right thing, you just won't be able to read it all in Diagnostics.
  • Joe HebertJoe Hebert Junior Member Posts: 2,154
    One work around for the SEND_STRING 0 null lop off is to send to a virtual device instead and then monitor the strings for that virtual device in Notifications. The data will show up correctly within Notifications.
  • JasonSJasonS If I had known it was going to be that kind of party... Posts: 226
    I'll stick to what I have always done, telnet! Working since before NetLinx diagnostics existed!
  • MorgoZMorgoZ Junior Member Posts: 116
    Ok, many thanks for all your of your answers!!
  • viningvining X Member Posts: 4,341
    There's also a Hex_Debug function that will convert your hex string to its ascii representation for printing to diagnostics.
  • ericmedleyericmedley Senior Member - 3709 Posts Posts: 4,130
    Netlinx has never much like zeros in general. :)
Sign In or Register to comment.