Specifications
Specifications
Welcome to the Firmware section!
If you are not redirected automatically, click here.
Subsections of Specifications
General
Connections
| Connector | |
|---|---|
| Ethernet | |
| Net 1 | Gigabit Ethernet (Intel i210AT) |
| Net 2 | Gigabit Ethernet (Intel i210AT) |
| Net 3 | Gigabit Ethernet (Intel i210AT) |
| Serial | |
| DB9 serial | Deactivated |
| Power | |
| Jack (2.5 mm) center positive | 12V DC, about 6 to 12W |
Environmental
| Power | 12V, 12W max |
| Heat Dissipation | Max 42 BTU / HR |
| Operating temp | 0°C – 60°C |
| Dimensions | L: 238mm, W: 208mm, H:44mm |
| Compliance | CE, ROHS |
| Weight | 900g |
CAD step file
Network
Network
Caution
None of the specified protocols or ports, nor the communication can be changed. (except port configurable in sdm.config )
Its wise to review the lists and allow SDM to communicate with all ports and protocols defined.
SDM will not work without any of the ports and protocols defined.
Caution
SDM need frequent internet access Details
Ports used by Dante™
Depending on the configuration physical ports, VLAN or bridges used for Dante™ may use these ports for communication.
| Address | Port | Usage | Type |
|---|---|---|---|
| 239.255.0.0/16 | 4321 | ATP Multicast Audio | Multicast |
| 239.69.0.0/16 | 5004 | AES67 Multicast Audio (RTP / AVP port) | Multicast |
| 224.0.1.129-132 | 319, 320 | PTP | Multicast & Unicast when using DDM |
| 224.0.0.251 | 5353 | mDNS | Multicast |
| 224.0.0.230 – 233 | 8700 – 8708 | Multicast Control and Monitoring | Multicast |
| 239.254.1.1 | 9998 | Logging | Multicast |
| 239.254.3.3 | 9998 | PTP Logging (if enabled) | Multicast |
| 239.254.44.44 | 9998 | Logging | Multicast |
| 239.255.255.255 | 9875 | SAP (AES67 discovery) | Multicast |
| UDP | 28800, 28700-28708 | Via control & monitoring | Unicast |
| UDP | 38800, 38700-38708 | DVS control & monitoring | Unicast |
| UDP | 14336 -14591 | Unicast Audio [Excluding Via] | Unicast |
| UDP | 34336-34600 | Unicast Audio [Via Only] | Unicast |
| UDP | 4440, 4444, 4455 | Audio Control [Excluding Via] | Unicast |
| UDP | 24440, 24441,24444,24455 | Audio Control | Unicast |
| UDP | 4777 | Via Control | Unicast |
| TCP | 4777 | Via Websocket | Unicast |
| UDP | 8850,28900, 24445 | Via control & Monitoring | Unicast |
| UDP | 8850,38900,8899 | DVS control & monitoring | Unicast |
| UDP | 8000 | Dante Domain Manager Device Port | Unicast |
| UDP | 8001 | Dante Millau Device Proxy | Unicast |
| UDP | 8002 | Dante Lock Server | Unicast |
| UDP | 8751 | Dante Controller metering port | Unicast |
| UDP | 8800 | Control & Monitoring | Unicast |
| TCP | 8753 | mDNS clients | Unicast |
| TCP | 16100-16131 | HDCP Authentication for Video Endpoints | Unicast |
| UDP | 61440-61951 | FPGA level audio flow keepalive | Unicast |
Ports used by SDM for Control
Depending on the configuration physical ports, VLAN or bridges used for control may use these ports for communication.
| Protocol | Source IP | Source Port | Destination IP | Destination Port | Description |
|---|---|---|---|---|---|
| HTTP | All | all | Control interface Address | Port configured in sdm.config | Control over HTTP |
| TCP | All | all | Control interface Address | Port configured in sdm.config | Control over TCP |
General ports used by OS and services (Mandatory ports)
| Protocol | Source IP | Source Port | Destination | Destination Port | Description |
|---|---|---|---|---|---|
| TCP | All interfaces | all | l02.genesis-technologies.ch | 443 | nexgentec™ license service |
| UDP | All interfaces | all | swan.genesis-technologies.ch | 443 | nexgentec™ maintenance service |
| TCP | All interfaces | all | DNS service | 53 | DNS |
| UDP | All interfaces | all | DNS service | 53 | DNS |
| UDP | All interfaces | all | NTP service | 123 | NTP |
| TCP | All interfaces | all | www.app.qbee.io | 443 | 3rd party maintenance service |
Internet access
Why does SDM need Internet access?
- Since we live in an unpredictable world we have to protect our paying customers. Therefore we check the SDM license at least every 7 days. This avoids software piratery and allows us getting enough financial resources to further develop sdm and provide future support.
- We do monitor all relevant parameters for continuous operation. Software is always written by humans and may contain bugs like a memory leak. Without monitoring we are not able to act before you even take a notice that there is an issue.
How frequent does SDM need Internet access?
At least every 7 days a successful license check must be possible. If not SDM stops working
What if I do not agree?
Send the SDM device back to where you bought it. We have no intention to change our mind.
What if I think that this could be done better?
Sure we listen, just give us a call.
Time Server access
Why does SDM need a valid time and therefore access to a ntp time server?
- Without a valid time all license checks will fail and SDM will stop working
- Running a computer whithout correct time is in general a bad idea
How frequent does SDM need time server access?
- We do recommend that SDM has continued access to a NTP time server
- At least every 7 days a successful time sync should be possible
What if no ntp time server is accessible?
- Then the operation of SDM is not guaranteed.