Troubleshooting, Utah scientific avs – Grass Valley iRouter v.6.01 User Manual
Page 42
Routing Switchers Tips and Tricks
Troubleshooting
38
Troubleshooting
Utah routers are using semi-ASCII protocol to communicate over serial port. Semi-ASCII means
that in some cases it uses binary characters while for most purposes it uses normal ASCII. Note
that all the commands are case sensitive. Here is the list of the commands that can be used
during troubleshooting:
• Matrix Refresh Report. In this mode the controller will periodically (~5 sec) send the status
of the router to the serial port. Typically should be disabled.
•
To enable this mode type
•
To disable this mode type
• Matrix Change Report. In this mode the controller will notify the serial port about changes
in the router status. Typically should be enabled.
•
To enable this mode type
•
To disable this mode type
The characters you’re typing will not be visible at the command prompt.The status updates
have the format:
where
SOH
is ASCII character with code 1, selected levels are represented with characters from
@
(no levels) to
O
(all levels), input and output are represented as three digits. For example, for
destination 5 levels 0 and 1 switched to source 7 will produce :
Utah Scientific AVS
This router is a predecessor of CS-3 series. The router is equipped with one 232 port (25 pin),
one configurable 232/422 port (9 pin), one 422 port (9 pin) and one diagnostics RS 232 port.
All the tests were done on the RS-232 port. To connect to a 232 port you will need a standard
RS-232 cable with gender-bender on the router side. To connect to the diagnostics port you
will need a null-modem RS-232 cable. The baud rates are set on the controller board using DIP
switches. The other parameters can be set from the diagnostics port. As mentioned, this is very
old and slow protocol.
Notes
• The <CR> character (Enter) is interpreted by the SC-3 as the end of set
crosspoint command. As a result it will execute a take of the last crosspoint
that was sent from that port. If no crosspoints were set before it will take bus
0 to source 0 on all available levels. Be careful!
• One can experience delays when receiving response from the router after a
crosspoint is taken. The delay can be 1-2 seconds. The crosspoint itself is
taken immediately. This behavior was noticed when running the software on
Linux while on Windows it works fine.