Serial port on Hyper-V loxberry

[J V]

Hello,

I'm running Loxberry on Hyper-V and am trying to use the Serial-USB plugin ( https://www.loxwiki.eu/display/LOXBE...ial-USB-Bridge ). I seem to have problems getting it to work.
First weird thing is that the plugin does not find the miniserver (in the drop down box of the configuration). The virtual Loxberry is connected to an external hyper-V switch, so it should have access to the network; it can download plugins from internet, so I think it is fine.
Second weird thing are the serial ports. I have defined a named pipe, and configured Hyper-V so that the named pipe is passed to a comport. In Loxberry, for dmesg | tty, it lists me ttyS0 and ttyS1, but when I set /dev/ttyS1 as the device in the plugin, it does not seem to have the correct settings (e.g. baud). So either they plugin is not talking to that port.

Not fully Loxberry related, but any ideas or things I could try?

Thanks!

Jörg

[Prof.Mobilux]

First weird thing is that the plugin does not find the miniserver (in the drop down box of the configuration).

You have to configure your Miniserver in System Settings -> Miniserver

Second weird thing are the serial ports. I have defined a named pipe, and configured Hyper-V so that the named pipe is passed to a comport. In Loxberry, for dmesg | tty, it lists me ttyS0 and ttyS1, but when I set /dev/ttyS1 as the device in the plugin, it does not seem to have the correct settings (e.g. baud). So either they plugin is not talking to that port.

Don't know much about Hyper-V. Try to figure out current settings of the serial port (baudrate is only ONE thing):

setserial -a /dev/ttyS0

On a standard LB you have to install setserial wirth apt-get. I would guess you have to configure the virtual serial port exactly the same way you have configured the system's COM port.

[J V]

Thanks for the reply! I forgot to configure the Loxberry with the miniserver ip address...

It looks like it is starting to work somewhat; using the tool "screen", I can see that the data is arriving in the Loxberry on /dev/ttyS0. This means that the named pipe from Windows is working. However, the USB-Serial plugin does not seem to forward the UDP packages. In the plugin, when I select "abfrage aktualiseren", it shows me:
/dev/serial/by-id/*
but I have no entry "serial" in /dev. I suspect the plugin only detects USB-serial devices... I entered the name /dev/ttyS0, but it does not change in "abfrage aktualiseren"; it keeps showing the non-existant entry (I saved and rebooted).

The configuration now is:
Amplifier --serial-usb adapter--> Windows pc
In Hyper-V I have configured the Loxberry with a COM1, which creates a named pipe (I named it LoxberryCom1).
Using the tool np2coms ( https://github.com/albertjan/PipeToCom ), I forward the serial port in Windows (Com3 in my case) to the named pipe "LoxberryCom1".
Finally, in the Loxberry, I can use the tool "screen" to show what comes in". And it seems to work.

So close... :-)

Any suggestions for creating a bidirectional connection between a serial device and a udp port? This can even be in Windows...

Thanks!