Remote Base: Doug Hall RBI-1: Difference between revisions

From AllStarLink Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
There has never been documentation to this.... EVER
I will be building it out soon -kb8jnm - still not complete if you are reading this.




For those that have a Doug Hall Electronics Model RBI-1 frequency agile multi port remote base and wish to use it on app_rpt / AllStar system.
For those that have a Doug Hall Electronics Model RBI-1 frequency agile multi port remote base and wish to use it on app_rpt / AllStar system.


This was originally created for direct use in a PC that has a parallel port for signaling the device. There is no other method built into the software.
This was originally created for direct use in a PC that has a parallel port for signaling the device. There is no other method built into the app_rpt software.


It uses the first 3 pins of the parallel port and can not be changed. So if you have been using the pins for anything else, you will need to migrate them to higher pins than the first 3.
It uses the first 3 pins of the parallel port and can not be changed. So if you have been using the pins for anything else, you will need to migrate them to higher pins than the first 3.
Line 17: Line 14:


No buffering is required attaching this to the RBI-1's DB9 interface on the correct PP pins.  
No buffering is required attaching this to the RBI-1's DB9 interface on the correct PP pins.  
But, for some reason if you find you must, use a transistor capable of transitioning in less than 50ms on the data/clock lines.


See data on Parallel Port GPIO: https://wiki.allstarlink.org/wiki/SimpleUSB_Channel_Driver#Parallel_Port
See data on Parallel Port GPIO: https://wiki.allstarlink.org/wiki/SimpleUSB_Channel_Driver#Parallel_Port
Line 28: Line 24:
iobase=0x378                      ;(for lpt1)
iobase=0x378                      ;(for lpt1)
remote=rbi                        ; Doug Hall RBI-1
remote=rbi                        ; Doug Hall RBI-1
functions=funtions-remote29285    ; Function list from link - use your node number
functions=funtions-remote29285    ; Function list from link (a list of agile working commands) - use your node number
memory=memory29285                ; system stored radio presets, not required - use your node number
memory=memory29285                ; 'system stored' radio presets, not required - use your node number




Line 57: Line 53:
;Not Required but noted:
;Not Required but noted:


[memory29285]              ;stored presets for radio, format: Freq mhz.khz,pltone, (R)ecieve pl (T)x pl -MODE (F,A,U,B for lsb) & pwr LMH & offset + -
[memory29285]              ;stored presets for radio, format: (recall# xx) = (Freq 6 digits and decimal) (TX PL Tone ) ( CTCSS Tone (ofset + - S ) ( power l m h )
 


init=224.660,100.0,-l      ;initial freq/mode on start-up/boot - choose something safe in case of error
init=224.660,100.0,-l      ;initial freq/mode on start-up/boot - choose something safe in case of error. Not required. Can be remarked out.


00=224.660,100.0,-l
00=224.560,100.0,-l
01=224.460,114.8,-l
01=224.460,114.8,-l
02=224.580,131.8,-l
02=224.580,131.8,-l
03=223.980,100.0,-l
03=223.980,100.0,-l
;04=146.940,114.8,-lt
04=146.940,114.8,-lt
;10=442.175,162.2,+l
10=442.175,162.2,+l
;11=444.475,114.8,+l
11=444.475,114.8,+l
;12=444.150,100.0,+l
12=444.150,100.0,+l
;13=446.500,100.0,sl
;13=446.500,100.0,sl


; Tuning a agile remote base has a unchangeable prefix of (star 5) *5


There are other options to explore.
Note :
There is a security log-in function for remote control  -TBA-
 
It is more than convenient and desirable to put all of the control functions on a published node and secure the node/audio on a private node you can disconnect.
It is more than convenient and desirable to put all of the control functions on a published node and secure the node/audio on a private node you can disconnect.
This makes it dis-connectable for periodic use and prevents you from the need to connect to the node in 'command mode' ie *4xxxxx to control it's agile interface.
This makes it dis-connectable for periodic use and prevents you from the need to connect to the node in 'command mode' ie *4xxxxx to control it's agile interface.
That can allow you to set it before connecting the node for audio as well.
Always review and test macro/scheduler initiations of this before leaving it to run from it unattended.
There is a security log-in function for remote base control  -*To be added to the wiki in a section for all remote base* -

Revision as of 00:56, 4 February 2021


For those that have a Doug Hall Electronics Model RBI-1 frequency agile multi port remote base and wish to use it on app_rpt / AllStar system.

This was originally created for direct use in a PC that has a parallel port for signaling the device. There is no other method built into the app_rpt software.

It uses the first 3 pins of the parallel port and can not be changed. So if you have been using the pins for anything else, you will need to migrate them to higher pins than the first 3.

PP1 = data

PP2 = clock

PP3 = reset

No buffering is required attaching this to the RBI-1's DB9 interface on the correct PP pins.

See data on Parallel Port GPIO: https://wiki.allstarlink.org/wiki/SimpleUSB_Channel_Driver#Parallel_Port


Set-up inside app_rpt:

In Rpt.conf you will need to set lines in the nodes stanza:

iobase=0x378  ;(for lpt1) remote=rbi  ; Doug Hall RBI-1 functions=funtions-remote29285  ; Function list from link (a list of agile working commands) - use your node number memory=memory29285  ; 'system stored' radio presets, not required - use your node number


Remote Commands

[funtions-remote29285] ;for rbi-1 use your node number

0=remote,1  ; Retrieve Radio Stored Memory Channel 1=remote,2  ; Set freq. VFO MMMMM*KKK*O (Mhz digits, Khz digits, Offset) 2=remote,3  ; Set tx PL tone PL Tone HHH*D* 3=remote,4  ; Set rx PL tone HHH*D*

40=remote,100  ; Rx PL off 41=remote,101  ; Rx PL on 42=remote,102  ; Tx PL off 43=remote,103  ; Tx PL on 44=remote,104  ; Low Power 45=remote,105  ; Medium Power 46=remote,106  ; High Power

51=remote,5  ; Long status query 52=remote,140  ; Short status query 67=remote,210  ; Send a * 69=remote,211  ; Send a #


Not Required but noted

[memory29285] ;stored presets for radio, format: (recall# xx) = (Freq 6 digits and decimal) (TX PL Tone ) ( CTCSS Tone ) (ofset + - S ) ( power l m h )


init=224.660,100.0,-l ;initial freq/mode on start-up/boot - choose something safe in case of error. Not required. Can be remarked out.

00=224.560,100.0,-l 01=224.460,114.8,-l 02=224.580,131.8,-l 03=223.980,100.0,-l 04=146.940,114.8,-lt 10=442.175,162.2,+l 11=444.475,114.8,+l 12=444.150,100.0,+l

13=446.500,100.0,sl
Tuning a agile remote base has a unchangeable prefix of (star 5) *5

Note : It is more than convenient and desirable to put all of the control functions on a published node and secure the node/audio on a private node you can disconnect. This makes it dis-connectable for periodic use and prevents you from the need to connect to the node in 'command mode' ie *4xxxxx to control it's agile interface. That can allow you to set it before connecting the node for audio as well. Always review and test macro/scheduler initiations of this before leaving it to run from it unattended.

There is a security log-in function for remote base control -*To be added to the wiki in a section for all remote base* -