Confused about using generic-tcp-serial

[FinkPloyd545]

I have a Unimux 8 port KVM that has an RS232 port on it, so I have it hooked up to a Mac Mini that is running companion. I used the connection: Generic: TCP Serial Port, and I think I set all the values in the connection correctly (Baud rate, listen port, etc.), but I don't have the ability to send any commands when choosing which actions to include on a button with this connection.

The only options I have are "Select Next Serial Port in List" and "Select Previous Serial Port in List"

Am I missing a module I need in order to send commands via serial to this device?

[MeestorX]

From the Help screen:
"This is a helper to assist other modules. There are no actions."

My guess is that you use it to convert RS-232 to TCP. You connect another module to that IP address. You have to find out what commands your KVM supports if there's no native Companion module for it.

[FinkPloyd545]

@MeestorX Thank you for responding.

I was going to program it with the commands it demonstrates in the manual.

Guess I'm a bit lost with the device on where to get an IP address for it since it has no IP capabilities by the looks of it.

[FinkPloyd545]

I was going to program it using the tcp-udp module*

[MeestorX]

Just match the port in the tcp-serial module to the port in the tcp/udp module. Use 127.0.0.1 for the ip address if it needs one. The udp/tcp module will then communicate with the tcp-serial module which will the communicate with your device.

…

On Fri, Apr 4, 2025 at 4:05 PM FinkPloyd545 ***@***.***> wrote: I was going to program it using the tcp-udp module* — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG6HXOUFUFHSATSKEZGR2GT2X36Y7AVCNFSM6AAAAAB2PTWTRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZZHAYDGOBRGM> . You are receiving this because you were mentioned.Message ID: ***@***.*** com> [image: FinkPloyd545]*FinkPloyd545* left a comment (bitfocus/companion-module-generic-tcp-serial#33) <#33 (comment)> I was going to program it using the tcp-udp module* — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG6HXOUFUFHSATSKEZGR2GT2X36Y7AVCNFSM6AAAAAB2PTWTRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZZHAYDGOBRGM> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[h07d0q]

Like MeestorX said, use the generic TCP module in conjunction with this module.
You will quickly realize that you can control the device, but are missing feedbacks or updates ist you control the device outside companion. I also started that way and ended programming my own module for Extron MMX. (I still have to move it to the official Bitfocus repository)

Anyhow, this issue can be closed since it's not an issue with this module.
Maybe the help and readme should be clearer and document a tutorial with the generic TCP module?