![background image](http://html.mh-extra.com/html/kramer/vs-34fd/vs-34fd_user-manual_2001327054.webp)
Kramer Electronics Ltd.
VS-34FD
– Protocol 3000
52
Function
Description
Syntax
Parameters/Attributes
Example
EXT-POE
Enable/disable the
+48V input for the PS-
4812 PoE power
supply add-on.
Only the input for
the PS-4812 PoE
power supply add-on
can be
enabled/disabled. The
module card ports do
not.
COMMAND
#EXT-POE
0,enable_value
<CR>
FEEDBACK
~nn@EXT-POE
0,enable_value,48V_status
<CR><LF>
port_id
–
0
– 48V input connector
enable_value
–
ON
– 48V input is enabled
OFF
– 48V input is disabled
48v_status
– Operational status of 48V input:
OK
– Receiving power
WARN
– Not working
POWERDOWN
– Enabled, but receiving
power
Enable the 48V
input for the PS-
4812 PoE power
supply add-on:
#EXT-
POE
0,ON
<CR>
EXT-POE?
Get the PoE power
operational status for
one of the module
card ports or for the
+48V input for the
PS-4812 PoE power
supply add-on.
COMMAND
#EXT-POE?
port_id
<CR>
FEEDBACK
~nn@EXT-POE?
0,enable_value,48V_status
<CR><LF>
port_id
–
0
– 48V connector
1
–34
enable_value
–
ON
– 48V input is enabled
OFF
– 48V input is disabled
48v_status
– Operational status of 48V input:
OK
– Receiving power
WARN
– Not working
POWERDOWN
– Disabled, but receiving
power
Get the
enable/disable
status of the 48V
input for port 2:
#EXT-
POE?
2
<CR>
EXT-PSU?
Get the status of the
power supply unit.
COMMAND
#EXT-PSU?
ps_id
<CR>
FEEDBACK
~nn@EXT-
PSU
ps_id
,
plug_status
,
ps_status
<CR><LF>
ps_id
– Power supply id number:
1
–2
*
– both PSUs
plug_status
– Physical connection status of
the power supply:
ON
– Connected
OFF
– Disconnected
ps_status
– Power status of the power supply:
OK
– powered properly
WARN
– not powered properly and may need
to be checked
OFFLINE
– not receiving power
Get the status of
power supply 1:
#EXT-
PSU?
1
<CR>
EXT-PSU-
BUZZER
Enable/disable PSU
warning buzzer.
COMMAND
#EXT-PSU-BUZZER
enabled_status
<CR>
FEEDBACK
~nn@EXT-PSU-BUZZER
enabled_status
<CR><LF>
enabled_status
–
0
– Disable
1
– Enable
Enable the PSU
warning buzzer:
#EXT-PSU-
BUZZER
1
<CR>
EXT-PSU-
BUZZER?
Get the enable/disable
status of the PSU
warning buzzer.
COMMAND
#EXT-PSU-BUZZER?
<CR>
FEEDBACK
~nn@EXT-PSU-BUZZER?
enabled_status
<CR><LF>
enabled_status
–
0
– Disabled
1
– Enabled
Get the
enable/disable
status of the PSU
warning buzzer:
#EXT-PSU-
BUZZER?
<CR>
EXT-VOLT?
Get the voltage of the
board.
COMMAND
#EXT-VOLT?
slot_id
<CR>
FEEDBACK
~nn@EXT-VOLT?
slot_id
:
volt_checkpoint_id/volt_checkpoint_total :
stdand value
:
actual value
:
status
<CR><LF>
slot_id
– Module ID (slot number):
1
–17
volt_checkpoint_id
– ID number of current
voltage detection point, starting from 1
volt_checkpoint_total
– Nnumber of
voltage detection points
stdand value
– Hardware design value
actual value
– Current value
status
–
WARN
OK
Get the voltage for
the card in slot 1:
#EXT-
VOLT?
slot_id
<
CR>
FACTORY
Reset device to
factory default
configuration.
This command
deletes all user data
from the device. The
deletion can take
some time.
Your device may
require powering off
and powering on for
the changes to take
effect.
COMMAND
#FACTORY
<CR>
FEEDBACK
~nn@FACTORY
ok
<CR><LF>
Reset the device to
factory default
configuration:
#FACTORY
<CR>
FPGA-VER?
Get current FPGA
version.
COMMAND
#FPGA-VER?
fpga_id
<CR>
FEEDBACK
~nn@FPGA-VER
fpga_id
,
expected_ver
,
ver
<CR><LF>
fpga_id
– FPGA id
expected_ver
– Expected FPGA version for
current firmware
ver
– Actual FPGA version
Get current FPGA
version:
#FPGA-
VER?
1
<CR>
GEDID
Get EDID support on
certain input/output.
For old devices
that do not support
this command,
~
nn
@ERR
002
<CR><LF>
is
received.
COMMAND
#GEDID
io_mode
,
in_index
<CR>
FEEDBACK
~nn@GEDID
io_mode
,
in_index
,
size
<CR><LF>
io_mode
– Input/Output
0
– Input
1
– Output
2
– Default EDID
io_index
– Number that indicates the specific
input or output port:
1
–34
size
– Size of data to be sent from device, 0
means no EDID support
Get EDID support
information for
input 1:
#GEDID
1
<CR>
GET
Get file contents.
COMMAND
#GET
file_name
<CR>
FEEDBACK
Multi-line:
~nn@GET
file_name
,
file_size
ready
<CR><LF>
contents
~nn@GET
file_name
ok
<CR><LF>
file_name
– Name of file from which to get
contents, includes:
CONFIGURATION.JSON
CONFIG_LOG.JSON
METADATA.JSON, MESSAGES
contents
– Byte stream of file contents
file_size
– Size of file (device sends it in
response to give user a chance to get ready)
#GET
file_resp
onse.dat
<CR>