[aprssig] Re: New Paradigm for UIDIGI

Robert Bruninga bruninga at usna.edu
Sat May 14 08:05:37 CDT 2005


Dick,
Yes!  This UIDIGI version does appear to fix the major UIDIGI
 problem! When did this new version come out?  Thanks!
Bob

>>> Richard Jenkins <rejenkins at adelphia.net> 05/14/05 6:24 AM >>>
>It is my understanding that one of the reasons for the current
>recommended methodology for reprogramming UIDIGI eproms
> was that UIDIGI could not properly place the '*' character after the
>"expired" WIDE command.
>
>This capability was apparently added in version 1.8b6.  The
>applicable portions of the "CHANGES.TXT" file are listed below.
>
>- Added new flags to UIFLDFL command. Now the bit flags have the
>following
>meaning:
>
>bit 0 WIDEN-0 will be repeated
>bit 1 insert callsign before WIDEN-n
>bit 2 put has been repeated flag on WIDEN-0
>bit 3 make call substitution on WIDEN-0
>
>Eg:
>With bit 2 reset:
>IW3FQG>APRS,RELAY,WIDE2-2
>IW3FQG>APRS,DIGI1*,WIDE2-1
>IW3FQG>APRS,DIGI1*,WIDE2
>
>With bit 2 set
>IW3FQG>APRS,RELAY,WIDE2-2
>IW3FQG>APRS,DIGI1*,WIDE2-1
>IW3FQG>APRS,DIGI1,WIDE2*
>
>- Added new flags to UITRFL command. Now the bit flags have the
>following
>meaning:
>
>bit 0 TRACEN-0 will be repeated
>bit 1 put has been repeated flag on TRACEN-0
>bit 2 make call substitution on TRACEN-0
>
>I have changed the UIFLDfl parm to 4 (the numerical value of bit 2)
>and it works.  I now have 2 digis that are properly adding the *
>(asterisk) to the end of the expired WIDEn path statement.
>
>What does this do to the new paradigm plans for UIDIGI?  It would
>seemingly remove the need to alias the WIDE1-1 command.
>
>Dick w2gwy









More information about the aprssig mailing list