| |
VK7AX > UIDIGI 18.05.05 14:10l 115 Lines 3730 Bytes #999 (0) @ VKNET
BID : VK7AX-1805UT
Read: GUEST
Subj: [Ui-Digi] Digest #484
Path: ON0AR<ON0AR<7M3TJZ<ON4HU<HG8LXL<VK4TTT<VK1DSN<VK7NW<VK7AX
Sent: 050518/1338z @:VK7AX.#ULV.TAS.AUS.OC [NWTNOS-NWTas] #:42809 $:VK7AX-1805U
Date: 18 May 2005 10:18:56 -0000
From: uidigi@yahoogroups.com
To: uidigi@yahoogroups.com
Subject: [uidigi] Digest Number 484
There are 2 messages in this issue.
Topics in this digest:
1. Re: Shoehorning the 'New Paradigm' into UIDIGI 1.9B3 - Revised Version 1.3
From: Ron Stordahl <ron.stordahl@digikey.com>
2. Re: Shoehorning the 'New Paradigm' into UIDIGI 1.9B3 - Revised Version 1.3
From: Ron Stordahl <ron.stordahl@digikey.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Tue, 17 May 2005 12:07:06 -0500
From: Ron Stordahl <ron.stordahl@digikey.com>
Subject: Re: Shoehorning the 'New Paradigm' into UIDIGI 1.9B3 - Revised Version 1.3
I have done extensive testing here...I have 9 UIDIGI-ROMs running within
about a 200 mile distance. But I have to wait until evening for me to
reliably hear their packets out to a level of 3. Ill post my heard
results after careful study, however at this point I am fairly confident
in my recommendations found at http://dxspots.com/FIX14439_UIDIGI-ROM.html.
Thanks for the offset locations to patch the image, to correct the
problem in the configuration program UIDGCFG.exe. Ill confirm this
before I add it to my document however....
Ron, N5IN
Ron Tonneson wrote:
> Ron
>
> UIFLD is at 344 hex, UITRF is at 346 hex in the PROM.
>
> I have two UIDIGI nodes here in eastern Iowa. My son who operates a
> number of nodes in Kansas took a look at my setup and at raw packets
> thru my digis. When I first did the setup he said that they were not
> handling WIDE1-1 properly. I did NOT have WIDE1-1 in my UID. After I
> added it he said it operated properly. My original UID was:
>
> WIDE4-4,WIDE5-5,WIDE6-6,WIDE7-7,WIDE5-4,WIDE6-4,WIDE6-5,WIDE7-6
>
> I now have it as:
>
> WIDE1-1,WIDE4-4,WIDE5-5,WIDE6-6,WIDE7-7,WIDE5-4,WIDE6-5,WIDE7-6
>
> Comments?
>
> Ron - K0QVF
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Tue, 17 May 2005 12:25:27 -0500
From: Ron Stordahl <ron.stordahl@digikey.com>
Subject: Re: Shoehorning the 'New Paradigm' into UIDIGI 1.9B3 - Revised Version 1.3
I have done extensive testing here...I have 9 UIDIGI-ROMs running within
about a 200 mile distance. But I have to wait until evening for me to
reliably hear their packets out to a level of 3. Ill post my heard
results after careful study, however at this point I am fairly confident
in my recommendations found at
http://dxspots.com/FIX14439_UIDIGI-ROM.html
<http://dxspots.com/FIX14439_UIDIGI-ROM.html.>
Thanks for the offset locations to patch the image, to correct the
problem in the configuration program UIDGCFG.exe. Ill confirm this
before I add it to my document however....
Ron, N5IN
Ron Tonneson wrote:
> Ron
>
> UIFLD is at 344 hex, UITRF is at 346 hex in the PROM.
>
> I have two UIDIGI nodes here in eastern Iowa. My son who operates a
> number of nodes in Kansas took a look at my setup and at raw packets
> thru my digis. When I first did the setup he said that they were not
> handling WIDE1-1 properly. I did NOT have WIDE1-1 in my UID. After I
> added it he said it operated properly. My original UID was:
>
> WIDE4-4,WIDE5-5,WIDE6-6,WIDE7-7,WIDE5-4,WIDE6-4,WIDE6-5,WIDE7-6
>
> I now have it as:
>
> WIDE1-1,WIDE4-4,WIDE5-5,WIDE6-6,WIDE7-7,WIDE5-4,WIDE6-5,WIDE7-6
>
> Comments?
>
> Ron - K0QVF
________________________________________________________________________
________________________________________________________________________
End Ui-Digi Digest #484
Read previous mail | Read next mail
| |
