IF150 Supported Commands
The IF150 Firmware supports
all the original commands that the Lowe IF-150 Interface supports and
also some additional ones.
More commands may be added that could be used by a driving program such
as my HF150 Control Program
but it is important to understand that the Lowe HF-150 Receiver will
only respond to the formal Lowe commands and therefore any additional
commands implemented in this IF150
Firmware will be specific to the IF150 Interface and will not sent on
the output to the HF-150 Receiver.
Lowe Commands
There are four Lowe commands. FRQ,
MOD, RCL and STO.
FRQ - Set Receiver Frequency - Execution Time 700ms
FRQ <value in
kHz> <CR>
FRQ 1234
<CR>
Tunes receiver to 1234 kHz
FRQ 15222.998<CR>
Tunes receiver to 15222.998 kHz
<value in kHz> range limits
are from 30 to 29999.999
for .nnn values the nearest 8Hz tuning
step is chosen
<CR> = carriage return
MOD - Set Receiver Mode - Execution Time 80ms
MOD <mode>
<CR>
mode LSB = Lower Sideband
mode USB = Upper Sideband
mode AMN = AM narrow filter
mode AM = AM wide filter
mode AMS = AM Synchronous double sideband
(alternative for AMD)
mode AMD = AM Synchronous double sideband
mode ASF = AM Synchronous 'HiFi' mode
mode ASL = AM Synchronous lower sideband
mode ASU = AM Synchronous upper sideband
MOD LSB <CR>
Sets receiver to Lower Sideband mode
<CR> = carriage return
RCL - Recall Receiver Memory - Execution Time 230ms
RCL <memory
number> <CR>
<memory number> range
limits are from 1 to 60
RCL 1
<CR>
Recalls receiver memory
location 1 setting stored frequency and mode
RCL 08
<CR>
Recalls receiver memory
location 8 setting
stored frequency and mode
RCL 33
<CR>
Recalls receiver memory
location 33 setting
stored frequency and mode<CR>
= carriage return
STO - Store into Receiver Memory - Execution Time 150ms
STO <memory
number> <CR>
<memory number> range
limits are from 1 to 60
STO 2
<CR>
Store receiver current
frequency and mode into
receiver memory location 2
STO 06
<CR>
Store receiver current frequency and
mode into receiver memory
location 06
STO 44
<CR>
Store receiver current frequency and
mode into receiver memory
location 44<CR> = carriage return
IF150 Additional Commands
These are the current supported additional commands. More may be
supported in the future.
? or HELP - Returns IF150 Interface Firmware Information
?
<CR>
Returns IF150
firmware information
HELP
<CR>
Returns IF150 firmware
information
<CR> = carriage return
Example response:
IF150 Control
Interface (C) N. R. Bailey 2012
Version
V1.0.5P 04 Jul 2012
IDENT - Returns IF Interface Identity Information
IDENT
<CR>
Returns IF150 interface
identity information
<CR> = carriage return
Example response:
IF150-V1.0.5P-S.00000001-NRB-A.00783394
Command Case and Valid Characters
The interface accepts the following characters/controls in the commands
and arguments sent to the interface:
Letters
'a' to
'z' (ASCII 97 to ASCII 122)
Letters
'A' to
'Z' (ASCII 65 to ASCII 90)
Numbers
'0' to '9'
(ASCII 48 to ASCII 57)
Symbols
'.'
(ASCII 46) (decimal point, period)
Controls
<CR>
(ASCII 13) (carriage return) (command terminator)
Controls
<ESC>
(ASCII 27) (escape)(cancels and pending command and
clears input buffer)
Controls
<space>
(ASCII 32) (space) (accepted but ignored)
Example:
FRQ 12345.678 <CR> will be processed the same as FrQ12345.678<CR>
moD Usb <CR> will
be processed the same as MOD
uSb<CR>
All other characters and control
characters will result in an error condition.
General Notes:
- upper, lower and mixed case is accepted
- spaces are ignored
- carriage return (ASCII code 13) terminates command
- escape character (ASCII code 27) will cancel any pending command
and clear input buffer
- longest accepted command with
spaces is FRQ 12345.678 CR i.e. 15 characters
Command Processing and Error Indication
The interface supports a status LED. The LED has three states and
indications:
- LED OFF - the interface
is idle and awaiting a command
- LED ON for limited time -
the interface is active processing the command sent to it. The
command is validated then the command is executed. The LED will
turn OFF after the command has been successfully executed
- LED ON permanently - this
indicates one of two states:
- Command sent to interface is unrecognised and/or parameter/data
values are invalid
- Interface has crashed / failed
If the LED is permanently ON due to an invalid command/data then as
soon as the next valid command is received and processed the LED will
turn off. If a valid command does not result in the LED turning
OFF then the interface has most probably crashed. In this case
try a valid command again and if the problem persists then you will
have to power cycle and reset the interface by disconnecting and
reconnecting the USB lead to the interface.
Top Of Page
© Nick Bailey 2012-2020