September-17th-2018, 11:06 AM
(September-14th-2018, 10:55 AM)Armin@netPI Wrote: Hello Jonas,
1.) I don't understand "getting the bluetooth of the host without restarting netPI"? What exactly do you mean? At least you have to load the bluetooth container into netPI at least once, correct? And then you tell it is necessary to restart netPI in this case? Why should this be necessary? What is not working if you do not restart netPI?
2.) If bluetooth is running in a container the bluetooth operation is no restricted by any instance. So the same amount of bluetooth device will run as if you are working with bluetooth on a standard Raspberry Pi
Armin
Hello Armin,
I build an own python container and added the configurations from the example bluetooth container you can pull from netpi's docker hub. In an old post you described, that you have to reboot the device, so that it comes from a fresh boot:
So what have I done? I started the container hilschernetpi/netpi-bluetooth:latest with network = host and privileged mode = on and device = /dev/ttyAMA0 mapped. Then I shutdown the device and repowered it, so that the it comes up from a fresh boot.
When Docker was ready back I watched the embedded log entry in the Docker web GUI. You can get to this log window yourself, if you click the container name in the running container list and then click as next to "!Logs".
There I can see the following
starting ssh ...
starting dbus ...
Starting OpenBSD Secure Shell server: sshdStarting system message bus: dbus.
init
Set Controller UART speed to 921600 bit/s
Flash firmware /etc/firmware/BCM43430A1.hcd
Set Controller UART speed to 921600 bit/s
Device setup complete
(September-14th-2018, 10:55 AM)Armin@netPI Wrote: Hello Jonas,
1.) I don't understand "getting the bluetooth of the host without restarting netPI"? What exactly do you mean? At least you have to load the bluetooth container into netPI at least once, correct? And then you tell it is necessary to restart netPI in this case? Why should this be necessary? What is not working if you do not restart netPI?
2.) If bluetooth is running in a container the bluetooth operation is no restricted by any instance. So the same amount of bluetooth device will run as if you are working with bluetooth on a standard Raspberry Pi
Armin
Hello Armin,
I build an own python container and added the configurations from the example bluetooth container you can pull from netpi's docker hub. In an old post you described, that you have to reboot the device, so that it comes from a fresh boot:
"So what have I done? I started the container hilschernetpi/netpi-bluetooth:latest with network = host and privileged mode = on and device = /dev/ttyAMA0 mapped. Then I shutdown the device and repowered it, so that the it comes up from a fresh boot.
When Docker was ready back I watched the embedded log entry in the Docker web GUI. You can get to this log window yourself, if you click the container name in the running container list and then click as next to "!Logs".
There I can see the following
starting ssh ...
starting dbus ...
Starting OpenBSD Secure Shell server: sshdStarting system message bus: dbus.
init
Set Controller UART speed to 921600 bit/s
Flash firmware /etc/firmware/BCM43430A1.hcd
Set Controller UART speed to 921600 bit/s
Device setup complete"
When I only restart the container there comes up the message "No such device" and when I completely restart the netPi the message "Device setup complete" comes up.
