sending tcp-ip to matrix pro

[rubendesnoo]

Hi,

With widget designer I set up a network to send tcp-ip commands to a Folsom image pro.
That worked great. I just programmed some scrips under a button.

Because I woud like to switch between 2 hd-inputs, I replaced the image-pro with a Barco matrix pro 8x8 dvi.
When setting up the network I choose for port 23 (like I red in the manual)
When pressing connect, the connection status flickers from connected to not connected. Looks like a error.

I am sure the cable is okay and the ip's are good (WD 2.0.0.4 Barco:2.0.0.10)

What am I doing wrong?

Regards

Ruben de Snoo

[Julia Foest]

Hi.

Your setup sounds to be correct!

Did you connect to the barco matrix before via another tool? So that the port probably is still used?
Same behaviour after you rebooted everything?

Best regards,
Julia

[Markus Zeppenfeld]

Hi Ruben,

is there anything other happening on the network and especially on that port?
Do you have another connection on that port running?

Is the connection working? Is it only a graphical "problem"?

Markus

[rubendesnoo]

Hi,

Quick support!

On the same port is no other connection.
I opened a new WD file and made a tcp ip connection, client only.
When connecting everything is fine.
Then I push a button with the following script:
(to recall a preset)

TCPStart,1
TCPSend,1,RPRST 1
TCPStop,1

after that I did send only TCPSend,1,RPRST 1

But every time when I push that button, the network starts erroring. The status toggles very quick from: "client connected" to "client connected from server".


The matrix had a factory reset before using.
and has now ip. 2.0.0.12 and subnet 255.0.0.0

Regards

[Julia Foest]

Hi,

I'm sorry, but there is a little bug in the current WD version with the TCPStart and TCPStop commands.
After you set up the connection to the barco matrix, please just send the commands, without starting and stopping the connection again.
This is will be fixed in the next release of WD.

Best regards,
Julia

[rubendesnoo]

Hi,

After some testing and programming I still have some TCP sending issues. I'm sending commands to a Folsom image pro.
On the widget design computer I'm also running Pandora's box, and I have an connection with an airscan.
Would this be an overload of data in widget design?
How could I reduce this?

I did send my file to support@coolux.de

regards

[Julia Foest]

Hi Ruben,

the Folsom needs a Carriage Return at the end of the command to be able to recognize it.
So the command should be
TCPSend,6,RTE 2 [CR]
Did you get it changing the input without the [CR] at the end?

In your WD file I see that you still start and stop the TCP connections several time. Or did you send an older project to me?
Instead of giving the commands
TCPStart,6
TCPSend,6,RTE 2
TCPStop,6
TCPStart,6
TCPSend,6,RTE 2
TCPStop,6

please just take
TCPSend,6,RTE 2 [CR]
If you need to send it twice, you could add a WDWait,’Seconds’ between the commands.

Do you get it working now?

Regarding your question about using the Airscan and PB simultaneously – as long as your network switch is still able to pass all packets, this should be ok to handle it together.

Best regards,
Julia

[Julia Foest]

Solved!