USB Port Mapping

[DSongra]

Dear Armin,

Hope you are doing well!

I am working on Modbus RTU node red in our NetPi RTE Gateway using RS485 to USB converter, but not able to mapped the USB port in node red docker container, as we have already done this successfully in last year (thread-653) I have referred this same.

I am getting error while creating the Docker Container if I add "/dev/ttyUSB0" in Devices attached screenshot for your reference.


Br,
Devendra

[Armin@netPI]

Well you need to know to which physical device the USB converter is mapped to. Then you can map it right

To get out to which physical device it is mapped to take $30 consumer raspberry pi or an open netFIELD Connect gateway. Then establish a terminal connection to the used device.

In the terminal session call the command first of all

Code:

ls /dev/

This command lists all available physical devices in the OS. 

After that insert the USB converter into this device and call again

Code:

ls /dev/

You will recognize that a new device was created next to all the other existing ones. Remember this name of this new device. This device will be exactly the same device as it will be mapped in netPI later.

[DSongra]

Dear Armin,

I have checked, but not showing USB port info, node red created through the Docker only not from console. Please find attached screenshot.

USB converter connect and removed and connect back again try the same few times, but still same response.


Br,
Devendra

[Armin@netPI]

No I said you need to use consumer Raspberry Pi for this test or netFIELD Connect gateway. I did not say using netPI for this test! The USB test is NOT possible on netPI.

[patribenq]

If you have doubts about whether there is a hardware problem with the USB connector or the installed system, an easy way to check this is to make any bootable USB flash drive, connect it to this connector and check whether it is visible in the bios. If yes— is it being downloaded from it? If the drive is visible, the download is underway. Then everything is fine in hardware. We are looking for a problem in the system, installing the original drivers on the chipset and, if available on the official website, on USB controllers. If the breakdown is severe, you will most likely need FLASH DRIVE RECOVERY, which specialists will be able to do.

[Armin@netPI]

Well the point is that booting from USB on a Raspberry PI3B - which a netPI device is based on - is not trivial. It is not supported from scatch in the boot ROM and needs to be activated in the security fuses in the Pi3B GPU. See for example https://www.makeuseof.com/tag/make-raspb...-boot-usb/. The desribed method does not work with Hilschers standard netPI OS but with Raspbian OS only.

Thx
Armin