Pacific Research Solutions RI-1 User Manual
Page 60
Pacific Research Solutions
RI-1 and PE-1 User Manual
Page 54
Passing S-Commands to Another Controller
S-Commands can be sent from one controller to another when you have multiple controllers connected together via the
auxiliary buss. This is done by including the destination controller’s address in front of the S-Command. When the destination
controller address leads the S-Command, that S-Command is not executed in the source controller. When you have an S-
Command that needs to be executed in another RI-xxx controller, you simply insert (for example) an “A1” into the macro
before the S-Command and its data. All data from the “A1” through the “C” (S-Command separator) will be sent to the
controller which has a “1” set as its controller address. Each controller in the system will have its own address. When sending
an S-Command to another controller, the controller with the same address as the “A” number in the S-Command will execute
that S-Command. In other words, a controller with address 1 will respond to an S-Command with an “A1” prefix. A controller
with address 3 will respond to an S-Command with an “A3” prefix. The “controller address” is set with
S-Command 39 and can be any address from 1 through 9. For controllers to communicate in this format, S-Command 38 must
be in the default state mode 1, serial port mode. The following example will send an S-Command to another controller to turn
off the CTCSS/DCS tone for that controller.
1. Un-lock the controller with your password.
2. Send “63 152” and un-key. This will set the macro start line pointer to line 152.
3. Send “64 A1 01 1” and un-key.
The “64” is the macro editor command. A1 is the address of the controller that will execute the following S-Command.
The “01” is the system mode S-Command.
The “1” is the repeater COS access S-Command data.
4. Send “64” and un-key. The “64” without data will tell the controller to insert a “D” to mark the end of this macro.
5. The data stored in the macro table at line 152 will look like “A1011CD”.
USER S-COMMANDS
Think of user S-Commands as just renamed S-Commands. User S-Commands are processed just like standard commands.
User S-Commands can, but do not have to, pass a data field to the actual S-Command.
Use the user S-Commands for simple applications. Use standard commands for applications with multiple S-Commands. The
following example will allow a user to lock on the repeater transmitter for a set time.
1. Un-lock the controller with your password.
2. Send “61 25 2 0 005 21” and un-key.
The “61” is the user S-Command.
The 25 is the user command storage location.
The 2 is the command type, User S-Command.
The “0” is the group number for this command.
The “005” is the force PTT on for x time S-Command. This item requires a leading zero.
The “21” is the name of the user S-Command.
3. Send “69” and to lock the controller and save your data.
4. Send “22 150” and un-key, you should hear a speech message “fifteen seconds”. You should notice that the repeater
transmitter has stayed keyed for 15 seconds. The “22” is the name of the user S-Command and the 15 was the data that is
passed to S-Command 05.
5. You now have a user command to force on the repeater transmitter.