VoxCommando

Help and Support (Using VoxCommando) => VoxCommando Basics and Core Features => Topic started by: monkee on September 29, 2023, 10:13:06 PM

Title: Trouble viewing incoming TCP info in VC
Post by: monkee on September 29, 2023, 10:13:06 PM

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!

Title: Re: Trouble viewing incoming TCP info in VC
Post by: jitterjames on October 01, 2023, 10:30:11 AM

Please post the xml for whatever command have tested.

Title: Re: Trouble viewing incoming TCP info in VC
Post by: jitterjames on October 01, 2023, 10:31:23 AM

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

Title: Re: Trouble viewing incoming TCP info in VC
Post by: jitterjames on October 01, 2023, 10:34:01 AM

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

Title: Re: Trouble viewing incoming TCP info in VC
Post by: monkee on October 02, 2023, 12:59:04 AM

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?

Title: Re: Trouble viewing incoming TCP info in VC
Post by: jitterjames on October 04, 2023, 10:39:47 AM

I have no idea.