Skip to content

D110 connection issue#33

Open
teambob wants to merge 1 commit into
labbots:mainfrom
teambob:D110_connect
Open

D110 connection issue#33
teambob wants to merge 1 commit into
labbots:mainfrom
teambob:D110_connect

Conversation

@teambob
Copy link
Copy Markdown

@teambob teambob commented Feb 17, 2025

D110 shows as two Bluetooth devices. One has a number of services, the other has none. On the D110 we want the one with no services

In the longer term the user should be able to choose the device in the UI or we should find a better heuristic. Perhaps we could look for a particular device type?

…e other has none. On the D110 we want the one with no services

In the longer term the user should be able to choose the device in the UI or we should find a better heuristic. Perhaps we could look for a particular device type?
@MultiMote
Copy link
Copy Markdown

MultiMote commented Feb 17, 2025

One has a number of services

This one is Bluetooth Low Energy address. It can be used too if you find suitable characteristic.

Second one is Bluetooth Classic which can be used as Bluetooth Serial.

https://niim-docs.pages.dev/documents/NIIMBOT_hardware_interfacing.html

@teambob
Copy link
Copy Markdown
Author

teambob commented Feb 18, 2025

Thanks for the information. NiimPrintX only worked for me with the BLE, not the classic bluetooth. I'll dig into the documentation and see what's happening

Avicennasis added a commit to Avicennasis/NiimPrintX that referenced this pull request Apr 11, 2026
D110 appears as two Bluetooth devices. Filters for the one with no
service UUIDs, which is the correct one for printing.
Added .get() safety for cross-platform metadata compatibility.
Upstream: labbots#33 by @teambob

Partially addresses labbots#13, labbots#22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants