search

DMXCore / DmxCore100

DMX Core 100 - Standalone Controller
0 stars 0 forks source link

Output configuration baselines - should not be able to delete. #5

Open VividRGBLighting opened 11 months ago

VividRGBLighting commented 11 months ago

Add logic to create outputs based on hardware platform. If the DMX output board is installed, two outputs for DMX are configured and not deleteable. Outputs can be turned on/off, but always visible in UI.

System could also possibly self-configure based on hardware (Processor sees the cards) Or a system option that allows you to pick from a list of possible add-on cards and then configures minimum/required options for that card.

HakanL commented 11 months ago

Actually the application re-creates a port if it detects the on-board DMX ports (at startup). But it's actually not the end of the world if a user were to delete a port, it's really just the "mapping" from the internal "Cosmos Id" to the outside world (sACN/ArtNet/DMX). It can be easily re-created. But I can see how preventing the user to delete the internal port may be worthwhile, let me think some more about it.

VividRGBLighting commented 11 months ago

This has more to do with a user that isn't sure what is going on. If an output gets deleted, and it was in use - Specifically the DMX outputs - then the user has no real way of knowing that they need to re-add the hardware and the only way to know for sure would be to take the box off the wall. Which should be unnecessary.

Case in point, the unit you sent me didn't have any DMX output in the interface. So it didn't create anything.

I guess what I'm saying is that users are going to expect the hardware to work out of the box with what's already connected to it. If the unit ships with a DMX output, or switch contact outputs, they are not going to want to have to configure it for it to work. The learning curve to "know that" and know what to do to get it to work is friction.

The benefit of having the system automatically knowing the cards are connected is more about saving time for you. I can see this as being one of the "I got the unit, but it doesn't work" support issues.

HakanL commented 11 months ago

I see what you mean. It does detect what is connected internally, that's why you have a "PORT1" on your unit. But I agree that it can be made better. And maybe separate the interfaces from mapping.