You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here in the New Zealand \ Australian region (and possibly others) we use 915Mhz frequency for the Becker Centronic USB stick.
This, unfortunately, gives it a different device path by id. I have replaced the hard-coded usb-BECKER-ANTRIEBE_GmbH_CDC_RS232_v125_Centronic-if00 with the device id the 915Mhz stick provides, which is usb-BECKER-ANTRIEBE_GmbH_CDC_RS232_915_v115_Centronic-if00.
With this replacement your component works perfectly but would obviously break on any update.
Would you consider putting in a frequency switch selector into the configuration which could select an alternative frequency and therefore different USB Device ID?
You could default to the current one so it wouldn't break any current installs but allow the alternative above with a entry in the configuration file. Let me know if you need more information or testing assistance etc.
The text was updated successfully, but these errors were encountered:
Here in the New Zealand \ Australian region (and possibly others) we use 915Mhz frequency for the Becker Centronic USB stick.
This, unfortunately, gives it a different device path by id. I have replaced the hard-coded
usb-BECKER-ANTRIEBE_GmbH_CDC_RS232_v125_Centronic-if00
with the device id the 915Mhz stick provides, which isusb-BECKER-ANTRIEBE_GmbH_CDC_RS232_915_v115_Centronic-if00
.With this replacement your component works perfectly but would obviously break on any update.
Would you consider putting in a frequency switch selector into the configuration which could select an alternative frequency and therefore different USB Device ID?
You could default to the current one so it wouldn't break any current installs but allow the alternative above with a entry in the configuration file. Let me know if you need more information or testing assistance etc.
The text was updated successfully, but these errors were encountered: