| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 953.3 | Easy CRRC Pins that look GREAT | ROCK::MINER | Electric = No more glow-glop | Tue Apr 11 1989 16:41 | 141 |
| > Now for the really, really serious stuff. You will have
> to bring a CRRC regulation frequency pin.
If you have a PostScript printer, here's a real easy way to get an
official size, NICE looking, CRRC frequency pin:
1) Extract this note: Notes> extract CRRC_PIN.PS
2) Edit the file CRRC_PIN.PS with your favorite editor;
- remove all lines up to and including the "Cut-Here" line
- change my name and AMA number to match yours (Do _NOT_
remove the "( )" characters around your name & AMA #)
3) Exit your editor and print the file to a PostScript printer.
4) Cut out the appropriate channels and using clear packing tape,
tape the paper pin to a piece of 1/16" plywood (or 1/8" balsa).
5) Glue a clothes pin to the back so the "clamp" part points away
from the end with your channel number on it.
_____
| \
| \ Silent POWER!
_ ___________ _________ | Happy Landings!
| \ | | | | |
|--------|- SANYO + ]-| ASTRO |--| - Dan Miner
|_/ |___________| |_________| |
| / | " The Earth needs more OZONE,
| / not Caster Oil!! "
|_____/
%%%%%%%%%%%%%%%%%%%%%% (Cut-Here) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%!PS-Adobe-1.0
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Frequency pins for CRRC club
% Change the following two lines for your name and AMA number...
% (And NOTHING else...)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
/name (Daniel Miner) def % Do NOT remove "( )" characters!!!
/ama (AMA 227070) def % Do NOT remove "( )" characters!!!
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
/inch {72 mul} def
/box_width 5.0 inch def
/box_height 1.0 inch def
/name_typesize 0.3 inch def
/chan_typesize 1.14 inch def
/chan_width 1.0 inch def
%
/chan_y 0.1 inch def
/name_y box_height name_typesize 2 mul sub 3 div def
/name_x box_width chan_width 2 mul sub def
%
%--------------------------------------------
%
/leftnum
{ /Helvetica-Bold findfont chan_typesize scalefont setfont
exch dup stringwidth pop chan_width exch sub 2 div
chan_y moveto show
dup stringwidth pop chan_width exch sub 2 div chan_width add
chan_y moveto show
/Helvetica-Bold findfont name_typesize scalefont setfont
name dup stringwidth pop name_x exch sub 2 div chan_width 2 mul add
name_y 2 mul name_typesize add moveto show
ama dup stringwidth pop name_x exch sub 2 div chan_width 2 mul add
name_y moveto show
.5 setgray newpath
0 0 moveto
box_width 0 lineto
box_width box_height lineto
0 box_height lineto
closepath stroke
0 setgray
0 box_height neg 0.3 inch sub translate
} def
%
%--------------------------------------------
%
/rightnum
{ /Helvetica-Bold findfont chan_typesize scalefont setfont
exch dup stringwidth pop chan_width exch sub 2 div name_x add
chan_y moveto show
dup stringwidth pop chan_width exch sub 2 div chan_width add name_x add
chan_y moveto show
/Helvetica-Bold findfont name_typesize scalefont setfont
name dup stringwidth pop name_x exch sub 2 div
name_y 2 mul name_typesize add moveto show
ama dup stringwidth pop name_x exch sub 2 div
name_y moveto show
.5 setgray newpath
0 0 moveto
box_width 0 lineto
box_width box_height lineto
0 box_height lineto
closepath stroke
0 setgray
0 box_height neg 0.3 inch sub translate
} def
%
% --------------------------------------------------------------------------
%
/newpage
{ 8.5 inch box_width sub 2 div 9.55 inch translate
} def
newpage
(1)(2) leftnum
(1)(4) leftnum
(1)(6) leftnum
(1)(8) leftnum
(2)(0) leftnum
(2)(2) leftnum
(2)(4) leftnum
(2)(6) leftnum
showpage
newpage
(2)(8) leftnum
(3)(0) leftnum
(3)(2) leftnum
(3)(4) leftnum
(3)(8) rightnum
(4)(0) rightnum
(4)(2) rightnum
(4)(4) rightnum
showpage
newpage
(4)(6) rightnum
(4)(8) rightnum
(5)(0) rightnum
(5)(2) rightnum
(5)(4) rightnum
(5)(6) rightnum
showpage
|
| 953.5 | Neato | LEDS::WATT | | Wed Apr 12 1989 09:08 | 6 |
| These numbers are not for the transmitter, they are for a pin that goes
on the frequency board. The AMA doesn't specify size on these.
Dan, these are great. Now I have to learn what a postscript printer is.
Charlie
|
| 953.6 | other fonts ? | ESASE::CULLEN | | Wed Apr 12 1989 09:48 | 9 |
| Hi,
These look great !! Is there a font that is similar to the designations
put on mil / commercial aircraft - the straight edged / corners
cut off type ?
Regards,
Eric();
|
| 953.8 | try this for size | ESASE::CULLEN | | Wed Apr 12 1989 11:20 | 7 |
| I got it work with ...
print/queue=ln03r$post/notify filename.ps /form=lps$ln03r$form
Regards,
Eric();
|
| 953.10 | Wrong topic again, but... | ROCK::MINER | Electric = No more glow-glop | Wed Apr 12 1989 15:20 | 54 |
| RE: .4
As Charlie said in .5, Yes, they are for the freq. board and that is
why some numbers are on the left and some are on the right.
(Numbers on the left are for pins that clip on the left side of the
board, etc.)
RE: .5
Charlie, if you want to become an official "PostScript hacker" go to
a bookstore and buy the two books:
"PostScript Language Tutorial and Cookbook" and
"PostScript Language Reference Manual"
both are published by Addison-Wesley and are written by Adobe
Systems Inc. - the developers of PostScript. Both of these books
are very good. (That is, if you want to learn PostScript. :-)
RE: .6
Eric C., there probably is a way to get the military-type font, but
I don't know how.
RE: .7
Dave, if you know the name of your LPS40 queue (for example
ANSI_LPS40 or LPS40$ANSI where "LPS40" is the "node name" of the
LPS40), try to do a
$ show queue *LPS40*
Look for the queue name that has "PS" or "POST" or "POSTSCRIPT" in
it. (Or something similar...) Then try:
$ print/queue=(queue name from above) filename.ps
To everyone: Thanks for the compliments. This is how I made my
freq. pin over a year ago and I was not able to generate ANY
interest in the CRRC club - where everyone else has made theirs by
hand. Gee, I guess people who work with computers everyday can
appreciate this more, huh? :-) :-)
I even offered to print one out for anyone that wanted one...
_____
| \
| \ Silent POWER!
_ ___________ _________ | Happy Landings!
| \ | | | | |
|--------|- SANYO + ]-| ASTRO |--| - Dan Miner
|_/ |___________| |_________| |
| / | " The Earth needs more OZONE,
| / not Caster Oil!! "
|_____/
|
| 953.24 | Postscript poop | LEDS::COHEN | | Thu Apr 13 1989 14:18 | 12 |
| >RE: .6
>
> Eric C., there probably is a way to get the military-type font, but
> I don't know how.
No, LPS40's and LN03's don't have such a font. They are limited to a
choice of, I believe, a Helvetica like font, a Times like font, and one
or two others. Postscript printers can usually have downline loadable
fonts. I don't believe that DEC has software to suport this ability.
If you request a font in a PS file that doesn't exist, the printer
will try and substitute what it believes to be a close approximation.
Some times, the substitution is quite poor.
|
| 953.25 | EXTRACT FREQ_PIN.COM and @FREQ_PIN Have Fun | EARRTH::ALLEN | | Mon Oct 09 1989 21:05 | 112 |
| $ READ/PROMPT="Name: " SYS$COMMAND NAME
$ READ/PROMPT="AMA Number: " SYS$COMMAND NUM
$ READ/PROMPT="Output File <FREQ_PIN.PS>: " SYS$COMMAND FILE
$ IF FILE .EQS. "" THEN $ FILE = "FREQ_PIN.PS"
$ COPY/NOLOG SYS$INPUT: 'FILE'
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%!PS-Adobe-1.0
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
$ OPEN/APPEND OUT 'FILE'
$ WRITE OUT "/name (''NAME') def"
$ WRITE OUT "/ama (''NUM') def"
$ CLOSE OUT
$ APPEND SYS$INPUT: 'FILE'
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
/inch {72 mul} def
/box_width 5.0 inch def
/box_height 1.0 inch def
/name_typesize 0.3 inch def
/chan_typesize 1.14 inch def
/chan_width 1.0 inch def
%
/chan_y 0.1 inch def
/name_y box_height name_typesize 2 mul sub 3 div def
/name_x box_width chan_width 2 mul sub def
%
%--------------------------------------------
%
/leftnum
{ /Helvetica-Bold findfont chan_typesize scalefont setfont
exch dup stringwidth pop chan_width exch sub 2 div
chan_y moveto show
dup stringwidth pop chan_width exch sub 2 div chan_width add
chan_y moveto show
/Helvetica-Bold findfont name_typesize scalefont setfont
name dup stringwidth pop name_x exch sub 2 div chan_width 2 mul add
name_y 2 mul name_typesize add moveto show
ama dup stringwidth pop name_x exch sub 2 div chan_width 2 mul add
name_y moveto show
.5 setgray newpath
0 0 moveto
box_width 0 lineto
box_width box_height lineto
0 box_height lineto
closepath stroke
0 setgray
0 box_height neg 0.3 inch sub translate
} def
%
%--------------------------------------------
%
/rightnum
{ /Helvetica-Bold findfont chan_typesize scalefont setfont
exch dup stringwidth pop chan_width exch sub 2 div name_x add
chan_y moveto show
dup stringwidth pop chan_width exch sub 2 div chan_width add name_x add
chan_y moveto show
/Helvetica-Bold findfont name_typesize scalefont setfont
name dup stringwidth pop name_x exch sub 2 div
name_y 2 mul name_typesize add moveto show
ama dup stringwidth pop name_x exch sub 2 div
name_y moveto show
.5 setgray newpath
0 0 moveto
box_width 0 lineto
box_width box_height lineto
0 box_height lineto
closepath stroke
0 setgray
0 box_height neg 0.3 inch sub translate
} def
%
% --------------------------------------------------------------------------
%
/newpage
{ 8.5 inch box_width sub 2 div 9.55 inch translate
} def
newpage
(1)(2) leftnum
(1)(4) leftnum
(1)(6) leftnum
(1)(8) leftnum
(2)(0) leftnum
(2)(2) leftnum
(2)(4) leftnum
(2)(6) leftnum
showpage
newpage
(2)(8) leftnum
(3)(0) leftnum
(3)(2) leftnum
(3)(4) leftnum
(3)(8) rightnum
(4)(0) rightnum
(4)(2) rightnum
(4)(4) rightnum
showpage
newpage
(4)(6) rightnum
(4)(8) rightnum
(5)(0) rightnum
(5)(2) rightnum
(5)(4) rightnum
(5)(6) rightnum
showpage
|
| 953.26 | CMRCM frequency control pins | RGB::MINER | Dan Miner, DTN:225-4015, HLO2-1/J12 (@ H11) | Tue Apr 23 1991 16:05 | 216 |
| RE: Note 953.3 by ROCK::MINER
At the request of Jim Rieth (note 1274.11), here is the newest
version of the PostScript pin generating program. This is the one
that was used to generate the sample pins in the recent CMRCM
newsletter. Main improvements are more pins per page and the
assoiated 2IM channel is added in small print.
If you have a PostScript printer, here's a real easy way to get an
official size, NICE looking, CMRCM frequency pin:
1) Extract this note: Notes> extract CMRCM_PIN.PS
2) Edit the file CMRCM_PIN.PS with your favorite editor;
- remove all lines up to and including the "Cut-Here" line
- change my name and AMA number to match yours (Do _NOT_
remove the "( )" characters around your name & AMA #)
3) Exit your editor and print the file to a PostScript printer.
4) Cut out the appropriate channels and using clear packing tape,
tape the paper pin to a piece of 1/16" plywood (or 1/8" balsa).
5) Glue a clothes pin to the back so the "clamp" part points away
from the end with your channel number on it.
_____
| \
| \ Silent POWER!
_ ___________ _________ | Happy Landings!
| \ | | | | |
|--------|- SANYO + ]-| ASTRO |--| - Dan Miner
|_/ |___________| |_________| |
| / | " The Earth needs more OZONE,
| / not Caster Oil!! "
|_____/
%%%%%%%%%%%%%%%%%%%%%% (Cut-Here) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%!PS-Adobe-1.0
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Frequency pins for CMRCM club
% Ex:
% /name (Daniel Miner) def
% /ama (AMA 227070) def
%
% Change the following name and ama lines with your name and AMA number...
% (And NOTHING else...)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
/name (____________) def
/ama (AMA ______) def
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
/inch {72 mul} def
/box_width 4.0 inch def
/box_height 1.0 inch def
/box_sep 0.05 inch def
/name_typesize 0.3 inch def
/chan_typesize 1.14 inch def
/ham_typesize 0.90 inch def
/chan_width 0.7 inch def
/margin 0.1 inch def
%
/chan_y 0.1 inch def
/name_y box_height name_typesize 2 mul sub 3 div def
/name_x box_width chan_width 2 mul sub def
%
/Helvetica-Bold findfont name_typesize scalefont setfont
/leftnamex box_width name stringwidth pop sub margin sub def
/leftnamey name_y 2 mul name_typesize add def
/leftamax box_width ama stringwidth pop sub margin sub def
/leftamay name_y def
/rightnamex margin def
/rightnamey name_y 2 mul name_typesize add def
/rightamax margin def
/rightamay name_y def
%
%--------------------------------------------
%
/leftnum
{ /Helvetica-Bold findfont chan_typesize scalefont setfont
exch dup stringwidth pop chan_width exch sub 2 div
chan_y moveto show
dup stringwidth pop chan_width exch sub 2 div chan_width add
chan_y moveto show
/Helvetica-Bold findfont name_typesize scalefont setfont
leftnamex leftnamey moveto name show
leftamax leftamay moveto ama show
chan_width 2 mul margin add leftamay moveto show % show 2IM channel
nextbox
} def
%
%--------------------------------------------
%
/rightnum
{ /Helvetica-Bold findfont chan_typesize scalefont setfont
exch dup stringwidth pop chan_width exch sub 2 div name_x add
chan_y moveto show
dup stringwidth pop chan_width exch sub 2 div chan_width add name_x add
chan_y moveto show
/Helvetica-Bold findfont name_typesize scalefont setfont
rightnamex rightnamey moveto name show
rightamax rightamay moveto ama show
dup stringwidth pop box_width chan_width 2 mul margin add sub exch sub
rightamay moveto show % show 2IM channel
nextbox
} def
%
%--------------------------------------------
%
/hamnum
{ /Helvetica-Bold findfont ham_typesize scalefont setfont
0 chan_typesize ham_typesize sub chan_y add 2 div moveto show
/Helvetica-Bold findfont name_typesize 2 div scalefont setfont
(MHz) show
/Helvetica-Bold findfont name_typesize scalefont setfont
leftnamex leftnamey moveto name show
leftamax leftamay moveto ama show
nextbox
} def
%
% --------------------------------------------------------------------------
%
/nextbox
{ .5 setgray newpath
0 0 moveto
box_width 0 lineto
box_width box_height lineto
0 box_height lineto
closepath stroke
0 setgray
0 box_height neg box_sep sub translate
} def
/newpage
{ 0.25 inch 9.75 inch translate
} def
/newcol
{ box_width 0.05 inch add 10.5 inch translate
} def
newpage
( ) (0)(0) rightnum
( ) (0)(1) rightnum
( ) (0)(2) rightnum
( ) (0)(3) rightnum
( ) (0)(4) rightnum
( ) (0)(5) rightnum
( ) (0)(6) rightnum
( ) (0)(7) rightnum
( ) (0)(8) rightnum
( ) (0)(9) rightnum
newcol
(/34) (1)(1) leftnum
( ) (1)(2) rightnum
(/36) (1)(3) leftnum
( ) (1)(4) rightnum
(38/) (1)(5) rightnum
( ) (1)(6) leftnum
(40/) (1)(7) rightnum
( ) (1)(8) leftnum
(/42) (1)(9) leftnum
( ) (2)(2) rightnum
showpage
newpage
(46/) (2)(3) rightnum
( ) (2)(4) leftnum
(48/) (2)(5) rightnum
( ) (2)(6) leftnum
(/50) (2)(7) leftnum
( ) (2)(8) rightnum
(/52) (2)(9) leftnum
( ) (3)(0) rightnum
(54/) (3)(1) rightnum
( ) (3)(2) leftnum
newcol
(56/) (3)(3) rightnum
(/11) (3)(4) leftnum
(/13) (3)(6) leftnum
(15/) (3)(8) rightnum
(17/) (4)(0) rightnum
(/19) (4)(2) leftnum
( ) (4)(4) leftnum
(23/) (4)(6) rightnum
(25/) (4)(8) rightnum
(/27) (5)(0) leftnum
showpage
newpage
(/29) (5)(2) leftnum
(31/) (5)(4) rightnum
(33/) (5)(6) rightnum
(53.1) hamnum
(53.2) hamnum
(53.3) hamnum
(53.4) hamnum
(53.5) hamnum
(53.6) hamnum
(53.7) hamnum
newcol
(53.8) hamnum
showpage
|
| 953.27 | format questions? | POBOX::KAPLOW | Set the WAYBACK machine for 1982 | Tue Apr 23 1991 19:42 | 12 |
| I just printed this out and have a couple questions. Forgive me if
I've missed some of the deleted replies, or the groundwork behing
this project.
1) Is there some significance to the "left handed" versus "right
handed" pins?
2) Many pins are missing. Is this because you've customized it for
your field rules, and eliminated the channels that have
interference? Is there some other reason?
Thanks
|
| 953.28 | Nice hack. | ZENDIA::REITH | Jim Reith DTN 226-6102 - LTN2-1/F02 | Wed Apr 24 1991 08:46 | 9 |
| 1) field sign has a left and right side P^)
2) field rules disallow odd channels above 34 and the new even channels
(I'm not as sure about this part)
Thanks for the upgrade Dan. Nice, simple, easy to understand, Forth...
I mean postscript. I was able to go to the bottom and create an entire
sheet of pins for the two channels I own and avoid printing the two
pages I don't use.
|
| 953.29 | Reasons for missing channels | RGB::MINER | Dan Miner, DTN:225-4015, HLO2-1/J12 (@ H11) | Wed Apr 24 1991 11:02 | 16 |
| RE: Note 953.27 by POBOX::KAPLOW
1) As Jim mentioned in -.1, this is because our freq. board is set
up this way. The non-obvious arrangement of frequencies is to help
eliminate 3-IM.
2) The pins that are missing are for 3 reasons:
A) the odd channels above 34 are not allowed to accommodate anyone
who may still have a wideband (silver sticker) Tx in that range.
B) the channels above 56 are not allowed to reduce the complications
of the 2-IM combinations they would cause. See note 1274.10.
C) at our field, we have TV channel 4 nearby and thus, can't use RC
channels 20 and 21 for 2-IM reasons.
|
| 953.31 | Frequency pins for ALL channels | RGB::MINER | Dan Miner, DTN:225-4015, HLO2-1/J12 (@ H11) | Thu Apr 25 1991 11:07 | 279 |
| Note 953.30 accidentally had the same program as the earlier note.
This note now contains the correct file.
In .27, Bob implies that some people may have different field rules
than the CMRCM has and may in fact be able to use all 50 of the new
channels. Sooooo... Here's a set of pins that include all 50 of the
new channels (plus ham freq.). All 2IM combinations are taken in to
account also.
*******************************************************************
NOTE: if you have a TV channel 4 transmitter in your
area, channels 20 and 21 should be banned for RC use.
*******************************************************************
The choice of whether the pin points to the left or right is based
on this frequency plan (to minimize 3-IM):
Station 1 Station 2 Station 3 Station 4
11 12 13 14
18 17 16 15
19 20 21 22
26 25 24 23
27 28 29 30
34 33 32 31
35 36 37 38
42 41 40 39
43 44 45 46
50 49 48 47
51 52 53 54
58 57 56 55
59 60
Where the boards for stations 1 and 3 are on the left; 2 and 4 are
on the right. Like this:
+-----+ +-----+
| | | |
| 1 | Tx | 2 |
| | Impound | |
+-----+ in +-----+
| | Middle | |
| 3 | | 4 |
| | | |
+-----+ +-----+
If you have a PostScript printer, here's a real easy way to get an
NICE looking, frequency pin:
1) Extract this note: Notes> extract ALL_PINS.PS
2) Edit the file ALL_PINS.PS with your favorite editor;
- remove all lines up to and including the "Cut-Here" line
- change the "___" name and AMA number lines to match yours
(Do _NOT_ remove the "( )" characters around your name & AMA #)
3) Exit your editor and print the file to a PostScript printer.
4) Cut out the appropriate channels and using clear packing tape,
tape the paper pin to a piece of 1/16" plywood (or 1/8" balsa).
5) Glue a clothes pin to the back so the "clamp" part points away
from the end with your channel number on it.
_____
| \
| \ Silent POWER!
_ ___________ _________ | Happy Landings!
| \ | | | | |
|--------|- SANYO + ]-| ASTRO |--| - Dan Miner
|_/ |___________| |_________| |
| / | " The Earth needs more OZONE,
| / not Caster Oil!! "
|_____/
%%%%%%%%%%%%%%%%%%%%%% (Cut-Here) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%!PS-Adobe-1.0
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Frequency pins for CRRC club
% Ex:
% /name (Daniel Miner) def
% /ama (AMA 227070) def
%
% Change the following name and ama lines with your name and AMA number...
% (And NOTHING else...)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
/name (____________) def
/ama (AMA ______) def
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
/inch {72 mul} def
/box_width 4.0 inch def
/box_height 1.0 inch def
/box_sep 0.05 inch def
/name_typesize 0.3 inch def
/2IM_typesize 0.22 inch def
/chan_typesize 1.14 inch def
/ham_typesize 0.90 inch def
/chan_width 0.7 inch def
/margin 0.1 inch def
%
/chan_y 0.1 inch def
/name_y box_height name_typesize 2 mul sub 3 div def
/name_x box_width chan_width 2 mul sub def
%
/Helvetica-Bold findfont name_typesize scalefont setfont
/leftnamex box_width name stringwidth pop sub margin sub def
/leftnamey name_y 2 mul name_typesize add def
/leftamax box_width ama stringwidth pop sub margin sub def
/leftamay name_y def
/rightnamex margin def
/rightnamey name_y 2 mul name_typesize add def
/rightamax margin def
/rightamay name_y def
%
%--------------------------------------------
%
/leftnum
{ /Helvetica-Bold findfont chan_typesize scalefont setfont
exch dup stringwidth pop chan_width exch sub 2 div
chan_y moveto show
dup stringwidth pop chan_width exch sub 2 div chan_width add
chan_y moveto show
/Helvetica-Bold findfont name_typesize scalefont setfont
leftnamex leftnamey moveto name show
leftamax leftamay moveto ama show
/Helvetica-Bold findfont 2IM_typesize scalefont setfont
chan_width 2 mul margin add leftamay moveto show % show 2IM channel
nextbox
} def
%
%--------------------------------------------
%
/rightnum
{ /Helvetica-Bold findfont chan_typesize scalefont setfont
exch dup stringwidth pop chan_width exch sub 2 div name_x add
chan_y moveto show
dup stringwidth pop chan_width exch sub 2 div chan_width add name_x add
chan_y moveto show
/Helvetica-Bold findfont name_typesize scalefont setfont
rightnamex rightnamey moveto name show
rightamax rightamay moveto ama show
/Helvetica-Bold findfont 2IM_typesize scalefont setfont
dup stringwidth pop box_width chan_width 2 mul margin add sub exch sub
rightamay moveto show % show 2IM channel
nextbox
} def
%
%--------------------------------------------
%
/hamnum
{ /Helvetica-Bold findfont ham_typesize scalefont setfont
0 chan_typesize ham_typesize sub chan_y add 2 div moveto show
/Helvetica-Bold findfont name_typesize 2 div scalefont setfont
(MHz) show
/Helvetica-Bold findfont name_typesize scalefont setfont
leftnamex leftnamey moveto name show
leftamax leftamay moveto ama show
nextbox
} def
%
% --------------------------------------------------------------------------
%
/nextbox
{ .5 setgray newpath
0 0 moveto
box_width 0 lineto
box_width box_height lineto
0 box_height lineto
closepath stroke
0 setgray
0 box_height neg box_sep sub translate
} def
/newpage
{ 0.25 inch 9.75 inch translate
} def
/newcol
{ box_width 0.05 inch add 10.5 inch translate
} def
newpage
( ) (0)(0) rightnum
( ) (0)(1) rightnum
( ) (0)(2) rightnum
( ) (0)(3) rightnum
( ) (0)(4) rightnum
( ) (0)(5) rightnum
( ) (0)(6) rightnum
( ) (0)(7) rightnum
( ) (0)(8) rightnum
( ) (0)(9) rightnum
newcol
(/34/57) (1)(1) leftnum
(35/58/) (1)(2) rightnum
(/36/59) (1)(3) leftnum
(37/60/) (1)(4) rightnum
(38/) (1)(5) rightnum
(/39) (1)(6) leftnum
(40/) (1)(7) rightnum
(/41) (1)(8) leftnum
(/42) (1)(9) leftnum
(43/) (2)(0) rightnum
showpage
newpage
(/44) (2)(1) leftnum
(45/) (2)(2) rightnum
(46/) (2)(3) rightnum
(/47) (2)(4) leftnum
(48/) (2)(5) rightnum
(/49) (2)(6) leftnum
(/50) (2)(7) leftnum
(51/) (2)(8) rightnum
(/52) (2)(9) leftnum
(53/) (3)(0) rightnum
newcol
(54/) (3)(1) rightnum
(/55) (3)(2) leftnum
(56/) (3)(3) rightnum
(/11/57) (3)(4) leftnum
(/12/58) (3)(5) leftnum
(13/59/) (3)(6) rightnum
(/14/60) (3)(7) leftnum
(15/) (3)(8) rightnum
(16/) (3)(9) rightnum
(/17) (4)(0) leftnum
showpage
newpage
(18/) (4)(1) rightnum
(/19) (4)(2) leftnum
(/20) (4)(3) leftnum
(21/) (4)(4) rightnum
(/22) (4)(5) leftnum
(23/) (4)(6) rightnum
(24/) (4)(7) rightnum
(/25) (4)(8) leftnum
(26/) (4)(9) rightnum
(/27) (5)(0) leftnum
newcol
(/28) (5)(1) leftnum
(29/) (5)(2) rightnum
(/30) (5)(3) leftnum
(31/) (5)(4) rightnum
(32/) (5)(5) rightnum
(/33) (5)(6) leftnum
(11/34/) (5)(7) rightnum
(/12/35) (5)(8) leftnum
(/13/36) (5)(9) leftnum
(14/37/) (6)(0) rightnum
showpage
newpage
(53.1) hamnum
(53.2) hamnum
(53.3) hamnum
(53.4) hamnum
(53.5) hamnum
(53.6) hamnum
(53.7) hamnum
(53.8) hamnum
showpage
|
| 953.32 | 2-IM frequency board which allows all channels if no Attacks are present | HANNAH::REITH | Jim HANNAH:: Reith DSG1/2E6 235-8039 | Wed Jul 15 1992 12:15 | 78 |
| I started from the board in .31 and have come up with the following system to
allow all channels when an Attack radio isn't in effect. I'd like some comments
before I submit this in about a week.
Here's a description of the problem and solution:
The Futaba Attack radio is susceptable to 2IM (as discussed in the Beginner
Electric topic). This is a design defect that several clubs have worked around
by combining channels on the same pin (channels 23 apart share a pin). This
disallows fliers 23 channels apart from flying together when an Attack is NOT
in use. The following is an attempt to allow this.
The double lines separate the channel blocks 23 apart that currently share a
pin. The single lines separate individual channels. There will be an indicator
at the top of the board as to whether an Attack is in use and this will
determine the grouping used by fliers. When an Attack is in use this indicator
will be set and only the double line groups will be allowed. This is the
responsibility of the Attack flier and will hopefully discourage the use and
buying of Attack radios without outright banning them (which was discussed).
When the indicator isn't set, channels 11 and 34 may fly together (the single
line separators are in effect). An Attack user needs to wait until only double
line groups are in use before taking the pin and setting the indicator. The
Attack pins will have an annotation on them so that it is clear when the
indicator may be unset (in case multiple Attacks are active at a time). This
will also give the Attack owners a little notoriety which may discourage use.
There is still the safety issue of a pager combining with an RC Tx 22.5 channels
away or the unfortunate field that has 2 local pagers 460kHz apart. ch20/21 may
be flown in the "No Attack" mode in the TV4 area!
Once this is finalized I intend to modify the pins at the end of .31 to reflect
the new left/right configurations, a Station number and Attack indicator.
Station 1 Station 2 Station 3 Station 4
==========================================================
11 12 13 14
----------------------------------------------------------
34 35 36 37
----------------------------------------------------------
57 58 59 60
==========================================================
18 17 16 15
----------------------------------------------------------
41 40 39 38
==========================================================
19 20 21 22
----------------------------------------------------------
42 43 44 45
==========================================================
26 25 24 23
----------------------------------------------------------
49 48 47 46
==========================================================
27 28 29 30
----------------------------------------------------------
50 51 52 53
==========================================================
33 32 31
----------------------------------------------------------
56 55 54
==========================================================
Ham Ham Ham Ham
==========================================================
Where the boards for stations 1 and 3 are on the left; 2 and 4 are
on the right. Like this:
+-----+ +-----+
| | | |
| 1 | Tx | 2 |
| | Impound | |
+-----+ in +-----+
| | Middle | |
| 3 | | 4 |
| | | |
+-----+ +-----+
|
| 953.33 | More than just Attack radios | RGB::MINER | Dan Miner, DTN:225-4015, HLO2-1/J12 (@ H11) | Wed Jul 15 1992 14:21 | 22 |
| Jim,
It is NOT sufficient to force the 2-IM combos ("double line" mode)
for Attack radios only. Anyone with older receivers that are single
conversion will also be effected.
Since most R/C fliers have no clue if they are flying with 2-IM
resistant receivers or not, I suggest having the double-line mode in
effect at all times.
If people complain, tell them to write the AMA and have them change
their rules to ban all receivers that are not resistant to the 2-IM
mode of interference...
If you go ahead with the "single / double converstion" mode receiver
pin, someone will mis-understand and screw it up... It's too easy
to be confused with "Sometimes you can fly 11 and 34 together and
sometimes you can't." Just say you can never fly these together.
That's my 2Hz. :-)
- Dan M.
|
| 953.34 | AMA listed Rxs only (which should limit it to the Attack) | HANNAH::REITH | Jim HANNAH:: Reith DSG1/2E6 235-8039 | Wed Jul 15 1992 14:38 | 11 |
| We're a narrow band only club these days so the Rx must be on the AMA (soon to
be discontinued) list to be used. Anyone not conforming to that won't bother
following the frequency board rules. I believe the Attack Rxs are the only ones
that give us 2IM problems off the AMA list. The other option is to ban the Attack
totally. It will probably come to that soon. Pagers present too big a risk in
this situation.
BTW: I noticed a couple of Attack radios at the Nats but didn't see anything
special being done towards them. Did anyone else notice anything done to avoid
2IM?
|
| 953.35 | No Restrictions at Nats | LEDS::WATT | | Thu Jul 16 1992 13:10 | 7 |
| All frequencies were in use at the Nats between all of the various
events. I did not see any restrictions. We did have to sign a paper
that said we were using a 1991 approved narrow band receiver. The
Attack AM would qualify for this in the eyes of the AMA.
Charlie
|