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
Direct Current Terminal Type #5796
Comments
Do you need more granularity than |
Although our applications have different termination types (screw connectors/terminal pugs) we don't need the granularity of having each type as an option. I can see how allowing those choices could lead to an endless list of options so I would be cautious adding them. |
But other users presumably might.
Well, let's see just how many it is. We have over 80 types as it is. Need some folks with DC-powered gear to offer more perspective. |
Most devices I usually work with (Nokia, Cisco...) come with a small connector which can be plugged into the power supply which itself has screw terminals for connecting a cable, or they have screw terminals fixed directly at the power supply without a small plug. As the main thing all of those devices have in common is the screw terminal, i'd therefore suggest to add a "DC screw terminal" to the list and maybe a "DC plug with screw terminal" do indicate a connection which can be disconnected by workers with no electrical background and help to dispatch the right people once a faulty device needs to be replaced. |
Environment
Proposed Functionality
Add the functionality to supply and receive DC power to devices.
Using DC to provide power to devices is a common practice in some environments. We would like to model these requirements.
I propose that:
Type 'DC Terminal' is added to Power Outlet Template
Type 'DC Terminal' is added to Power Port Template
Use Case
Some devices have the option to install DC power supplies or are powered using DC.
Database Changes
I don't believe that there would be a need to add any fields to the database.
External Dependencies
None
The text was updated successfully, but these errors were encountered: