Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search for connected interfaces #95

Open
hrueger opened this issue Feb 7, 2020 · 6 comments
Open

Search for connected interfaces #95

hrueger opened this issue Feb 7, 2020 · 6 comments

Comments

@hrueger
Copy link
Member

hrueger commented Feb 7, 2020

The library is working great. A nice-to-have feature would be the ability to search for connected devices. Happy to implement that, but what would be the best approach? Should we add a search function to each driver and call them one after each other / simultaneously?

@wiedi
Copy link
Member

wiedi commented Feb 7, 2020

Sounds good.

The RDM Spec calls this functionality "discovery", so maybe discover() instead of search()?

I'm unsure how much hardware actually supports this. I know the Enttec USB DMX Pro does but many other devices probaby don't.

@hrueger
Copy link
Member Author

hrueger commented Feb 7, 2020

I'm sorry, I was talking about searching for interfaces, not the actual lights...

@hrueger hrueger changed the title Search for devices Search for connected interfaces Feb 7, 2020
@wiedi
Copy link
Member

wiedi commented Feb 7, 2020

I see.

That's going to be hard on the per driver level. Most would just report the same serial ports.
I also suspect that filtering by USB vendor IDs is going to be very unreliable.

The serialport package has a serialport-list command - is that something similar to what you had in mind?

@hrueger
Copy link
Member Author

hrueger commented Feb 7, 2020

The serialport package has a serialport-list command - is that something similar to what you had in mind?

Yes. I'll look into that.

@hrueger
Copy link
Member Author

hrueger commented Feb 11, 2020

So my original idea was to find a connected device using serialport-list. But then we would need to find out what driver to use, and as far as I found out, this would be pretty hard. The beaglebone interface for example can't respond to incoming data, so we could not check if it is that one.
In addition we would leave artnet devices out.

Any more thoughts on that?

@wiedi
Copy link
Member

wiedi commented Feb 23, 2020

Yeah I'm not sure we can create a reliable way to discover all possible devices and make correct driver suggestions. :/

Maybe the best we can do is add some documentation about serialport-list that helps people figure out their device path. There aren't many driver options and they probably know what they physically plugged in so that maybe a driver suggestion isn't needed anyway.

For artnet other stuff on the networking side needs to be configured as well so I'd hope people setting this up know what they are doing. Maybe more documentation could also help here - like a guide on the wiki or something.

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

No branches or pull requests

2 participants