Parsing error 3 on UDP input

[calfredson]

Hello,

 

I'm trying to control a generic input using a UDP string sent from another computer on the network.  Here is the string that I am sending:

 

setInput “testin” 0.5

 

The Watchout computer recognizes that there is a command sent, but it returns this error:

 

Parsing error: 3; Unexpected end of file/line/communication: setInput

 

Anyone know what I am doing wrong?

 

Thanks,

 

Craig

[jfk]

Possibly you neglected the required Carriage Return at the end of the string (hex 0D) ?

[calfredson]

Thank you for the reply.  I have tried adding a carriage return in all possible forms, but I still get the same error.  The program that we are (currently) using to send the UDP data is Max/MSP, so I'm not exactly sure how that program formats carriage returns and hex bits.

 

Otherwise, is my syntax correct?

[jfk]

Thank you for the reply.  I have tried adding a carriage return in all possible forms, but I still get the same error.  The program that we are (currently) using to send the UDP data is Max/MSP, so I'm not exactly sure how that program formats carriage returns and hex bits.

 

Otherwise, is my syntax correct?

 

Yes, the sytax is correct.

Keep in mind the input name is case sensitive - so it must be an exact match to the Input named in the WATCHOUT program.

But the error message does not point at that type of an issue.

[TimFranklin]

The application must be sending the command as a list of strings. Try wrapping the whole command in double quotes -- "setInput “testin” 0.5"

 

You may need to escape the inner double quotes with a backslashes like this - "setInput \“testin\” 0.5"

 

Watchout sends that error if some part of a message is omitted. Sending only "setInput" would give you that exact error.

[calfredson]

SOLVED!  

 

Thank you Tim.  You were almost correct, but led me to the correct solution.  The string that finally worked was:

"setInput testin 0.5"

with no internal quotes.

Craig

[jfk]

SOLVED!  

 

Thank you Tim.  You were almost correct, but led me to the correct solution.  The string that finally worked was:

"setInput testin 0.5"

with no internal quotes.

Craig

 

so tim's guess on how to designate quotes within a quoted string was incorrect, but still important advice.

The reason it worked with no internal quotes is your input name had no spaces.

(The quotes around the input name are not required in that case)

 

If your input name had spaces, you would have a problem

until you discover how to delimit names with spaces within that string.

[RBeddig]

Hello,

 

I'm trying to control a generic input using a UDP string sent from another computer on the network.  Here is the string that I am sending:

 

setInput “testin” 0.5

 

The Watchout computer recognizes that there is a command sent, but it returns this error:

 

Parsing error: 3; Unexpected end of file/line/communication: setInput

 

Anyone know what I am doing wrong?

 

Thanks,

 

Craig

 

I was able to simulate the same sort of error message when sending 

 

setInput “testin 0.5

 

instead of

 

setInput “testin” 0.5

 

WATCHOUT could not recognize the name correctly due to the missing    "

[TimFranklin]

I've attached a screenshot of a functional Max patch that works properly with input names that contain spaces.

 

https://drive.google.com/file/d/0B8aHFFwB6M8Tc1BReUdPcm16ZzA/view?usp=sharing

 

Watchout will receive this- setInput "test input" .2

 

Within Max the inner double quotes do need to be escaped using a backslash or the message will not be interpreted correctly and will get split apart into a list of strings.

[calfredson]

This resides more on the Max side of things than the Watchout side, but I kept getting errors in WO when I used the "udpsend" object.  For some reason, Max was sending an extra comma a few bytes after the message.  It was working, but it bogged down WO considerably with the error message.  It turns out that "udpsend" formats all its outgoing messages as OSC, so that might have been where the extra comma was coming from.

 

Anyway, I switched to using the "mxj net.udp.send" object and all was fine.

[calfredson]

So I am now getting a different error in Watchout:

 

Parsing error: Bad number: "setInput"

 

It doesn't seem to be occurring every time I send a value, predominantly when I am sending lots of data in quick succession.  Any ideas?

 

Craig

[Andrew]

If you want to solve this problem, make sure that your MAX/MSP is sending the correct syntax first.

 

I suggest UDP monitoring program.

 

Check the exact syntax with the UDP monitoring program instead of WATCHOUT.

 

You are sure thath the syntax is correct then use your WATCHOUT.

[calfredson]

The syntax is correct.  I've been using Wireshark extensively to snoop on the UDP packets; it has definitely been a useful tool.

 

The latest error relating to bad numbers is definitely related to sending too many data packets.  I throttled the frequency that the data packets are being sent and the error went away.