Feature Description
The serial port manager is the only DCM that requires user configurations. Users have to know which com port they're connecting their device to in order for us to use it. If there's nothing set up that requires this on server launch, the serial scan should just skip, because there's no way configurations can be added while the server is running.
The big question is, how do we get that information to the manager? Should we create a "should scan" setting on device manager startup?
Feature Description
The serial port manager is the only DCM that requires user configurations. Users have to know which com port they're connecting their device to in order for us to use it. If there's nothing set up that requires this on server launch, the serial scan should just skip, because there's no way configurations can be added while the server is running.
The big question is, how do we get that information to the manager? Should we create a "should scan" setting on device manager startup?