-
Looking into setting this up as using the HyperSerialPico config is much simpler. However, I have a question regading the HyperHDR hardware. Does a Rpi need to be used to host HyperHDR? Currently I have a small optiplex 3040 running linux with a few other services running inlcuding HyperHDR which has been fine. Just wondering if its neccesary to use a Rpi or if my current config will work. Also with the other services running, mainly a Bitfocus satelite node, impact HyperSerialPico as it also uses a usb port? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
You don't need to have RPi, HyperSerialPico works on Mac (Intel, M1 I haven't tested), webOS, Windows PC, Linux ARM/x64 etc. because it uses a standard serial port protocol well supported by almost all systems (CDC) and does not even require special permissions in the system. As for resources, I haven't noticed any conflicts with other devices, but in the past there were problems with esp8266 that used ch340g (and not CDC) when using USB2.0 resources on RPi3 https://github.com/awawa-dev/HyperSPI/tree/5a17e197ecfaf3aecc2210b7912d1ca6db63fb8b : fighting for resources limited the maximum bandwidth of the USB2.0 grabber but we're talking here about the maximum bitrate when transmitting video reaching the limits specified by USB2.0 protocol. But this was almost certainly due to the limited hardware performance of the USB bus on the RPi3 combined with the poor performance and quality of ch340g drivers. Which led to the creation of HyperSPI. BTW HyperSPI support for Pico is almost ready but you would need RPi for HyperSPI. |
Beta Was this translation helpful? Give feedback.
You don't need to have RPi, HyperSerialPico works on Mac (Intel, M1 I haven't tested), webOS, Windows PC, Linux ARM/x64 etc. because it uses a standard serial port protocol well supported by almost all systems (CDC) and does not even require special permissions in the system. As for resources, I haven't noticed any conflicts with other devices, but in the past there were problems with esp8266 that used ch340g (and not CDC) when using USB2.0 resources on RPi3 https://github.com/awawa-dev/HyperSPI/tree/5a17e197ecfaf3aecc2210b7912d1ca6db63fb8b : fighting for resources limited the maximum bandwidth of the USB2.0 grabber but we're talking here about the maximum bitrate when transmitting video …