News:

Would you like to say "Thanks!" for extra support or new features that we provided? Donations are gratefully accepted.

Main Menu

Trouble viewing incoming TCP info in VC

Started by monkee, September 29, 2023, 10:13:06 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

monkee

Hi, I'm having trouble getting VC to recognize the response from my receiver using the TCP plugin.  I can successfully send it "(VOL U)" command and the volume goes up.  Then my receiver spits out the current volume, I can see the info in Wireshark, but I cannot see it in VC and my lastresult stays empty.  What can I try?  I'd like to use any incoming volume changes to trigger events. 

Thanks so much!

jitterjames

Please post the xml for whatever command have tested.

jitterjames

It might also help to know what brand and model of receiver you are talking to.

jitterjames

Are you using Client.Connect?  Have you read the action descriptions for the TCP plugin?

http://voxcommando.com/mediawiki/index.php?title=Plugin_TCP#Connect

monkee

Hi, sorry, I was doing more experimentation and figured it out!  Thank you for the reply.

I am, indeed, using Client.Connect.  I needed to increase the delay when using Client.Write, maybe it was closing the connection before I got the response. 

However, my response is followed by \x00\x00\x00 about 20 times, which I do not get in a normal telnet response.  Is there a way to stop that from coming through or do I have to regex the result?  I have to anyway but hopefully there is a better way to get rid of the \x00\'s or not see them at all?

jitterjames