Phil,?
Three things I found while working with Nucleus:
1
If you have not yet worked with the hardware, you will need to note the decoder output type.?
TRX and RXS decoders differ in the HDMI output name. This difference is shown in the control matrix if you expand the decoder to show its ports.?
Example: you may see outputs labeled "HDMIOUT" while others are "HDMIOUTMAIN".?
This difference ** must ** be reflected in the API command when sending a route.?
The system I just finished had decoders of both types.?
If the wrong output label is used, an error 400 unconfigured, is returned (when in fact the endpoint is configured).?
2
You will want to set the API names in all endpoints. If not, you will need to route using device serial numbers, else a variant of the dreaded 400 error is returned.?
There is a command generator within the Nucleus server.?
Without API names defined, the generated commands will have source and destination based on endpoint serial numbers.?
However, when API names are set, the command generator will make commands that are based on the API names.?
3
If you are doing RS-232 over Ethernet (or even pass through), you will need to set a profile at the server level with the 232 comspec info.?
Then apply that profile to each decoder where the 232 is used.?
You will need separate profile for each different comspec, if applicable to your system.?
