TCP2UDP Plugin - Bidirektionale TCP-Kommunikation mit dem Miniserver

[Tico]

Es könnte sich als nützlich erweisen, die Funktion "Virtuelle Texteingabe" zu testen, die in diesem Thread unter Beitrag 69 (ungetestet) beschrieben ist.

Dann erhalten Sie längere Texte, die mit einer Vielzahl von Befehlserkennungsoptionen analysiert werden können.

[frankenhooker]

Danke, ich schau es mir mal an.

[frankenhooker]

Habe es nun gelöst, eventuell zu umständlich. Aber es funktioniert mit Vergleichen und Analogspeicher, um die 0 bei Erkennung "MV\v" rauszufiltern. Manchmal steht MVMAX in einer neuen Zeile, manchmal auch nicht.

[steelpan]

Hello,

Is it possible to set up a TCP connection that requiers authentication?
I would like to connect the Miniserver with a Bang & Olufsen Beolink Gateway.

Kind Regards,
Luc
-----
Hallo,

Ist es möglich, eine TCP-Verbindung einzurichten, die eine Authentifizierung erfordert?
Ich möchte den Miniserver mit einem Bang & Olufsen Beolink Gateway verbinden.

Mit freundlichen Grüße,
Luc

[Christian Fenzl]

A tcp connection has no authentication by itself.
You need to do the authentication as you get the authentication response as documented by your device.

[steelpan]

Thank you Christian for the answer. It gives me hope to get things working.

A tcp connection has no authentication by itself.
You need to do the authentication as you get the authentication response as documented by your device.

If I understand well this means that I have to organize the miniserver so that

• it sends an outgoïng message "user name" followed by CR+LF whenever it recognizes an incomming string "login: "
• it sends an outgoïng message "password" followed by CR+LF whenever it recognizes an incomming string "CR+LF+password: "

The sending and receiving goes by UDP.
Is there a way to monitor the TCP comminication?

Kind regards and "Frohe Ostern+CR+LF".
Luc

[steelpan]

• By restarting the connection and using the UDP monitor in Loxone I could find out the incomming UDP-messages.
• The log files you organized in TCP2UDP gives all necessary info! Well documented!!

[steelpan]

However some problems:

• In Loxone config I can learn the incoming UDP commands (first picture) but the UDP monitor remains empty (second picture)
• Gives picture 3 the right way to recognise the in incomming message "login : " (which I retrieved from the UDP learning module)? I used a virtual UDP input.
• Gives picture 4 the richt way to organise a virtual UDP output to the TCP2UDP plugin (I used the local IP-adres of the loxberry Pi and the port number defined in the Plugin).
• Gives picture 5 the right way to send the login (Admin) to the Plugin?

I will post the Plugin data in a next item.

Kind regards,
Luc

[steelpan]

TCP2UDP data

[steelpan]

Log file from the plugin

[Christian Fenzl]

Use

BLGW: login:

in a Command Recognition as Digital Input: YES.
This should give a pulse to your input that should fire your virtual output with the username.
Same for the password.
Make sure your syntax is 100% correct, especially whitespaces and casing.

Regards, Christian

[steelpan]

Hello,

I used the syntax from the command recognition so I am quit sure that the syntax is correct. From the UDP monitor in Loxone Config you can see that the Objects are somehow recognised (right column).
What I don't understand is why in the live view window the VI inputs in the page are not marked yellow as normally should be the case. Is this correct? What could be wrong?

Kind regards,
Luc

[Christian Fenzl]

Can you show all settings of your login VI?

[steelpan]

Hello,

I think the inputs were working properly but their status was not visible in the life view up to now. To check this I used counters and found out all messages are recognised.
So something must be wrong with the outgoing message to the BLGW. That message should be the username (admin) followed by CR and LF.
As I marked the command terminator to be \r\n in de TCP2UDP setup I suppose that the message to send is simply "admin".

You can see the setup of the VQ in the picture. Is there a way to find out which outgoing UDP messages from Loxone are received by TCP2UDP and what is send to the device BLGW on the TCP connection?

Kind regards and thanks for the support,
Luc

[Christian Fenzl]

You need the \r\n sent with your VO from Loxone.
The setting in the plugin is only for the init command.

[steelpan]

I changed the command to sent to "admin\r\n" but it still doesn't work.

• Is the address I use for outgoing UDP messages (/dev/udp/192.168.1.43/9101) correct?
  The IP address is the local adres of the loxberry. The port (9101) is the port number in the TCP2UDP setup. This address works for other UDP messages (with different port number)
• Is there a way to log the communication?

Kind regards,
Luc