开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
Date

KAM+ exitnc.cmd

 

Anyone using a KAM+ may find adding the following to the exit command
program (exitnc.cmd) useful.

I added two lines

M ON
B E 30

and amended the line MON OFF to

MC OFF

The first command (M ON) turns the monitor back on when reverting to normal
TNC mode,
B E 30 sets the Beacon Every command to 30 minutes. B E 30 is needed as
UI-View sets the TNC Beacon to Zero on setting up, to avoid double
beaconing, but on exiting the TNC needs to have the Beacon Every time reset.
(NB: If you want to send a beacon at something other than 30 minutes, alter
the figure to the number of minutes you want. An alternative is B A 'X' -
Beacon After, where the KAM will wait until the channel has not been used
for 'X' minutes before sending a beacon. Round here, that would be like
setting B E 0. HI.....)

MC OFF is needed otherwise the KAM+ will start to show packets from other
stations when you are connected to a station.

Hope these ideas help someone else.

Cheers de Dave (G0DJA)


Using a KAM+

 

Any other users of the KAM+ on the list please?

If so, have you managed to solve the following problem with this TNC?

When using Host Mode (i.e., selecting 'NONE' mode in Comms Setup) incoming
UI frames from other users have the VHF identifier /V added. This means
that if I send a packet 'Hello' to, say, M0BCU-3 the following happens:-

KAM+ sends -
G0DJA-3>M0BCU-3: ~Hello~00

KAM+ receives an ACK, but decodes it as -
M0BCU-3>G0DJA-3/V: ~00

So UI-View doesn't recognise this as my callsign, not surprisingly, and
resends the message ~Hello~. M0BCU-3 responds with an ACK, but the KAM+
still doesn't recognise it as my callsign.

I've looked through the KAM+ instruction manual, but cannot see how to turn
off the /V from received packets in UI frames.

I would like, eventually, to use UI-View on HF as well as VHF, so would
prefer to be able to use NONE mode, rather than KISS (which works OK) which
seems only to address the VHF port on the KAM+.

Any ideas please?

Thanks de Dave (G0DJA)


Re: THE ANTI BRIGADE

 

I never did understand the 'APRS needs an NoV' arguement. Can someone
explain what the reasoning was please?

As far as I can see, many stations send beacons and you have to identify in
some format. Since UI frames are used for unconnected packets, such as when
you unexpectedly loose a connection for some reason, or decide to call 'CQ'
(Now, that takes me back to the days before NODES and Digipeaters, when you
had to find someone else using packet to be able to connect at all. HI!)
then UI frames should be 'OK'. So, where the arguments against APRS based on?

That is, other than the usuall mistrust of anything new, or that is not
understood by the complainant. :o)

de Dave (G0DJA)


Re: Map

Roger Colwell
 

They already are Mick! They are shown in the Stations List, along with those
within the area of the current map.

--
73 - Roger G4ZEC <zec@...>

----- Original Message -----
From: Mick O'Donnell <mickodonnell@...>
To: <ui-view@...>
Sent: Monday, April 19, 1999 12:07 AM
Subject: [ui-view] Re: Map


From: "Mick O'Donnell" <mickodonnell@...>

Hello Roger.

Another suggestion.

Can Off-Map locations be flagged up so that we know there are others
about,
even if we can't see them on the currently loaded map?
Perhaps a callsign with an Arrow pointing to the direction the location is
off-map?

Thanks and 73, Mick O'Donnell

Phone/Fax:: +44 (0)1908 316052
Mobile : +44 (0)836 228084
E-Mail: mickodonnell@...
ICQ 27902590


Re: THE ANTI BRIGADE

Roger Barker <[email protected]
 

In article <001401be89b2$fad50100$9bbd883e@ciemon>, Ciemon Dunville
<g0trt@...> writes

As a longtime APRS user I can tell you that this attitude will spread very
quickly amongst BBS users. The latest case I can quote happened, and to a
certain extent still does, from stations in the Norwich area. I managed to
get three BBS to include their APRS posn and a number of end users to not
only change their btext but also have a go with the software.

But a lot of complaints, even to the DCC, about use of APRS led to the BBS'
removing their posns to keep users happy. At the time we were using 144.850,
my WIDE digi was able to link, on a good day, the south coast, Suffolk and
up to G4IDE in Lincs, but only APRS beacons that were set to use RELAY WIDE.
[snip]

So, we all set our unproto to RELAY WIDE or even RELAY,WIDE,WIDE to ensure
maximum coverage. Why do we need such coverage? Two examples:
[snip]

Doesn't the above very much represent a self-fulfilling prophecy? ;-)

"You will get opposition from BBS users ... We need to set our digis to
RELAY,WIDE ..."

If people would read the following sections of the UI-View help -
"Introduction", "Station Setup" and "It Might Not Be For You..." - I
hope that I have made my opinion about the use of beacons and digis on
the BBS frequencies clear.

If/when you use the program other than on the BBS frequencies, the
caution I have advised doesn't apply. The reality, however, is that most
people are going to use it on the BBS frequencies, because that is where
their packet systems "live". No matter how good APRS is, few are going
to permanently move their systems onto a dedicated APRS frequency, even
when one is agreed.

What I see happening at the moment is that an image of UI-View is being
projected by comments to the UIVIEW packet topic, that wide area
digipeating is a prerequisite of using the program, which isn't true.

So, to repeat what I've said several times before - Do as much, or as
little in the way of digipeating as is locally acceptable. Don't create
local confrontation for the sake of making the program work better.

--
Roger Barker, G4IDE roger@...
Boston, UK


Re: THE ANTI BRIGADE

Stephen A. Wigg
 

From: Roger Barker <roger@...>

Also, anyone who can do a few sums can easily show that the total volume
of traffic being generated by UI-View use will pale into insignificance
compared to a user downloading a few bulletins from the BBS.

The real problem is that:-

(a) An attitude has developed in the UK that "packet = using the BBS
network", and the packet channels are to be used for nothing other than
accessing BBSs.

(b) Packet has almost ceased to be an amateur radio mode. Not only do
some users never think of packet in terms of self-training and
experimentation, but they complain if anyone else does!

As a Sysop here at Rugeley (GB7RUG), a BBS which looks after 40+ users, I
encourage the use of UI-VIEW on my mailbox 144.850Mhz port, via a seperate
machine running UI-View, interlinked to the main node and mailbox. I can
support no Sysop that doesn't! There is nothing to support the argument,
that UI-VIEW is taking over or increasing traffic on mailbox ports. The
mailbox and its users,
are unaffected by the passive UI frames, while they are connected to the
mailbox.


I take an active approach, by encouraging all my users to try experimentation
and new additions within Packet radio, whether it be hardware or software. If
we fail to try these new, modes, which encourage good software writers like
Roger, and hardware designers, where will packet Radio be in the next be in
the next 10years?


UI-View in the future will be a very valuable asset to Amateurs, and other
aspects of life in the future, its up to "all" to support it!



Steve (G1KQH) Sysop @ GB7RUG.#28.gbr.eu


Re: Map

"Mick O'Donnell" <[email protected]
 

Hello Roger.

Another suggestion.

Can Off-Map locations be flagged up so that we know there are others about,
even if we can't see them on the currently loaded map?
Perhaps a callsign with an Arrow pointing to the direction the location is
off-map?

Thanks and 73, Mick O'Donnell

Phone/Fax:: +44 (0)1908 316052
Mobile : +44 (0)836 228084
E-Mail: mickodonnell@...
ICQ 27902590


Re: THE ANTI BRIGADE

Ciemon Dunville
 

Hi all,

This is a bit long, but stick with it!

As a longtime APRS user I can tell you that this attitude will spread very
quickly amongst BBS users. The latest case I can quote happened, and to a
certain extent still does, from stations in the Norwich area. I managed to
get three BBS to include their APRS posn and a number of end users to not
only change their btext but also have a go with the software.

But a lot of complaints, even to the DCC, about use of APRS led to the BBS'
removing their posns to keep users happy. At the time we were using 144.850,
my WIDE digi was able to link, on a good day, the south coast, Suffolk and
up to G4IDE in Lincs, but only APRS beacons that were set to use RELAY WIDE.

Even though we stopped using APRS on the freq, the btexts didn't change as
everyone sends beacons. But still the complaints kept coming. Then a number
of complainers started beaconing every 6 mins things like..... Get APRS off
144.850..... Does APRS need an NOV. So we decided to move APRS activity off
the BBS access freq and went to 144.825. In Suffolk and the surrounding area
there is no 9k6 activity so it made sense to us. We've had no complaints at
all, there are three trackers, approximatley7 or so users and my WIDE digi
so activity isn't too bad.

The revised band plan that Iain Phillips released a while back made mention
of a dedicated APRS freq. Hopefully this will be confirmed when the
re-revised band plan is released in May (?). I urge you all to use that freq
to get the most from APRS/UI-View.

On the subject of unproto here is the thinking that has been developed over
the last 5+ years in the states:

The whole idea is to be able to communicate with anyone that is on your map
and also ensure maximum coverage for mobile and qrp stations. If we all used
any old alias for our digis then it would be complicated to achieve a wide
area of coverage. So ALL stations should have their alias set to RELAY those
that live on top of maountains or have good coverage should set it to WIDE.

So, we all set our unproto to RELAY WIDE or even RELAY,WIDE,WIDE to ensure
maximum coverage. Why do we need such coverage? Two examples:

1. I'm going to travel to Yorks from my qth in Suffolk. If we all use RELAY
and WIDE on our digi's then I can set my car trackers unproto to RELAY WIDE
and ensure maximum coverage without having to reprogram it enroute. Remember
I said that I can hear Lincs from my WIDE. SO if there's a WIDE in Lincs I
could be sat in Yorks with my 25 watt mobile and people on the south coast
could not only see me moving, but send me messages as well!

2. I'm on foot, in Ipswich with my THD7 that has the ability to send
messages. My unproto is RELAY,WIDE,WIDE. By using a RELAY in Ipswich, My
WIDE in Wattisham and a WIDE in Lincs I could be having a packet qso with
someone north of Roger!!

Hope you all understood all of that!

If any of you would like to join my APRSUK list it can be found at onelist
like this one.

73...Ciemon Dunville g0trt@...
APRS UK
!5207.40N/00058.35E-PHG7268/ QRA:JO02lc QTH Wattisham Suffolk


Re: Map calibration...

Keith Maton
 

I agree with John.

Some maps are being chopped, some are reduced in size. Some work
OK, but not all.

Keith


Map Problems With V0.74b

Roger Barker
 

To try and summarise the situation:-

1. The sample maps supplied with UI-View are all GIFs and are all size
800x600.

2. There is no scaling or stretching of the maps when loaded. Therefore
at a resolution of 800x600 or lower, they should display with a scroll
bar. At 1024x768 or higher they should only partially fill the screen,
and there should be a grey area to the right of and below the map.

3. If you create your own maps, they can be BMPs or GIFs. BUT if you
create BMPs and put them in the UI-VIEW&#92;MAPS directory, and then make
them into GIFs but don't delete the BMPs, UI-View uses the BMPs in
preference to the GIFs.

4. I have found a problem with V0.74b that causes it not to correctly
size the window when loading BMPs. It leaves it at whatever size it was
before the BMP was loaded.

I have now fixed '4', but obviously I don't want to upload the fix if
there are some other problems that I'm not seeing.

--
Roger Barker, G4IDE roger@...
Boston, UK


Re: Map calibration...

Jon Eyes
 

I forgot to mention that..... :-)

~~~~~~~~~~
Jon Eyes
Southport UK.

-----Original Message-----
From: Mark Simper <mark.simper@...>
To: ui-view@... <ui-view@...>
Date: 18 April 1999 12:43
Subject: [ui-view] Re: Map calibration...


From: Mark Simper <mark.simper@...>

Hi Roger,
I too have a similar problem after upgrading to version 0.74b,
when
I first run UI-View it loads a map that I have created but it only fills
the
very top left corner of the map window. The workaround that I have found
here- if
I load one of the supplied maps and then go back to one of my own maps it
then
fill the screen, the trouble then though is that all stations are shifted a
couple of miles south of where they should actually be.

Roger Barker wrote:

From: Roger Barker <roger@...>

In article <001101be898c$e4667820$0a20832c@pr233>, Jon Eyes
<jon@...> writes
From: "Jon Eyes" <jon@...>

Hi one and all...
I've just upgraded to v0.74b this morning..
I have now discovered all the maps I was using, no longer cover all the
screen, as a result the location of heard stations has slipped quite
dramatically (They have all moved up and to the left).
Using the gifs, supplied with the original version of UIVIEW, staions
are
displayed in the correct area, but map is still not covering the whole
area
of the screen. (A large grey remains to the right and below the
displayed
image of the map).
I have been running at 1024x768... Reducing the screen size increases
everything proportionally, and adds the scroll bars as expected, but the
calibration is still incorrect.
The original maps won't cover the screen at 1024x768, so that is correct
behaviour.

As regards calibration, the original maps are still calibrated correctly
on my test systems. Are other people finding that the original maps are
no longer calibrated correctly?

--
Roger Barker, G4IDE roger@...
Boston, UK

------------------------------------------------------------------------
Has ONElist changed your life?

Visit our homepage and share with us your experiences at ONElist of the
Week!


------------------------------------------------------------------------
Have you visited the new ONElist home page lately?

ONElist: The Leading e-mail list and community service on the Internet!


Re: Map calibration...

Roger Colwell
 

Hello All,

The problem appears to be only with .BMP files. If you convert your existing
maps to .GIF format, rename/delete your equivalent .BMP files, then opening
the maps in UI-VIEW 074b should display stations correctly positioned.

--
73 - Roger Colwell G4ZEC <zec@...>

----- Original Message -----
From: Roger Barker <roger@...>
To: <ui-view@...>
Sent: Sunday, April 18, 1999 12:24 PM
Subject: [ui-view] Re: Map calibration...


From: Roger Barker <roger@...>

In article <001101be898c$e4667820$0a20832c@pr233>, Jon Eyes
<jon@...> writes
From: "Jon Eyes" <jon@...>

Hi one and all...
I've just upgraded to v0.74b this morning..
I have now discovered all the maps I was using, no longer cover all the
screen, as a result the location of heard stations has slipped quite
dramatically (They have all moved up and to the left).
Using the gifs, supplied with the original version of UIVIEW, staions are
displayed in the correct area, but map is still not covering the whole
area
of the screen. (A large grey remains to the right and below the displayed
image of the map).
I have been running at 1024x768... Reducing the screen size increases
everything proportionally, and adds the scroll bars as expected, but the
calibration is still incorrect.
The original maps won't cover the screen at 1024x768, so that is correct
behaviour.

As regards calibration, the original maps are still calibrated correctly
on my test systems. Are other people finding that the original maps are
no longer calibrated correctly?

--
Roger Barker, G4IDE roger@...
Boston, UK

------------------------------------------------------------------------
Has ONElist changed your life?

Visit our homepage and share with us your experiences at ONElist of the
Week!


Re: Map calibration...

Jon Eyes
 

All versions up to and including .73b have displayed the bitmaps at
1024x768, filling the screen, although as Roger correctly states, the as
supplied gifs were in 800x600.
(just checked by going back to the previous beta.
~~~~~~~~~~
Jon Eyes
Southport UK.

-----Original Message-----
From: Roger Barker <roger@...>
To: ui-view@... <ui-view@...>
Date: 18 April 1999 11:47
Subject: [ui-view] Re: Map calibration...


From: Roger Barker <roger@...>

In article <001101be898c$e4667820$0a20832c@pr233>, Jon Eyes
<jon@...> writes
From: "Jon Eyes" <jon@...>

Hi one and all...
I've just upgraded to v0.74b this morning..
I have now discovered all the maps I was using, no longer cover all the
screen, as a result the location of heard stations has slipped quite
dramatically (They have all moved up and to the left).
Using the gifs, supplied with the original version of UIVIEW, staions are
displayed in the correct area, but map is still not covering the whole
area
of the screen. (A large grey remains to the right and below the displayed
image of the map).
I have been running at 1024x768... Reducing the screen size increases
everything proportionally, and adds the scroll bars as expected, but the
calibration is still incorrect.
The original maps won't cover the screen at 1024x768, so that is correct
behaviour.

As regards calibration, the original maps are still calibrated correctly
on my test systems. Are other people finding that the original maps are
no longer calibrated correctly?

--
Roger Barker, G4IDE roger@...
Boston, UK

------------------------------------------------------------------------
Has ONElist changed your life?

Visit our homepage and share with us your experiences at ONElist of the
Week!


Re: Map calibration...

Roger Barker
 

In article <001101be898c$e4667820$0a20832c@pr233>, Jon Eyes
<jon@...> writes
From: "Jon Eyes" <jon@...>

Hi one and all...
I've just upgraded to v0.74b this morning..
I have now discovered all the maps I was using, no longer cover all the
screen, as a result the location of heard stations has slipped quite
dramatically (They have all moved up and to the left).
Using the gifs, supplied with the original version of UIVIEW, staions are
displayed in the correct area, but map is still not covering the whole area
of the screen. (A large grey remains to the right and below the displayed
image of the map).
I have been running at 1024x768... Reducing the screen size increases
everything proportionally, and adds the scroll bars as expected, but the
calibration is still incorrect.
The original maps won't cover the screen at 1024x768, so that is correct
behaviour.

As regards calibration, the original maps are still calibrated correctly
on my test systems. Are other people finding that the original maps are
no longer calibrated correctly?

--
Roger Barker, G4IDE roger@...
Boston, UK


Map calibration...

Jon Eyes
 

Hi one and all...
I've just upgraded to v0.74b this morning..
I have now discovered all the maps I was using, no longer cover all the
screen, as a result the location of heard stations has slipped quite
dramatically (They have all moved up and to the left).
Using the gifs, supplied with the original version of UIVIEW, staions are
displayed in the correct area, but map is still not covering the whole area
of the screen. (A large grey remains to the right and below the displayed
image of the map).
I have been running at 1024x768... Reducing the screen size increases
everything proportionally, and adds the scroll bars as expected, but the
calibration is still incorrect.
Dragging the cursor accross the screen and watching the lat long readout at
the bottom, the readings stop changing once off the map area. Top left and
bottom right corners agree with the co-ord in the inf file, so the co-ord on
the map are still correct and it seems to be do with the way the map is
loaded/displayed.

It would appear that the edges of the maps have also been cropped (The map I
usually use, as the coverage area of GB7OMN, should stop just south of Rhyl
on it's southern edge, but now stops at Prestatyn - this is the same view as
I get on PSP with the scroll bar in the up position at full screen)

The maps I have been using are imported from AutoRoute 2000, and saved as
bitmaps with paint shop pro.

Hope that's enough info!

Is this a result of the tweaks Roger has done to enable the .gifs to load
faster?

~~~~~~~~~~
Jon Eyes
Southport UK.


Re: Map calibration...

Mark Simper
 

Hi Roger,
I too have a similar problem after upgrading to version 0.74b, when
I first run UI-View it loads a map that I have created but it only fills the
very top left corner of the map window. The workaround that I have found here- if
I load one of the supplied maps and then go back to one of my own maps it then
fill the screen, the trouble then though is that all stations are shifted a
couple of miles south of where they should actually be.

Roger Barker wrote:

From: Roger Barker <roger@...>

In article <001101be898c$e4667820$0a20832c@pr233>, Jon Eyes
<jon@...> writes
From: "Jon Eyes" <jon@...>

Hi one and all...
I've just upgraded to v0.74b this morning..
I have now discovered all the maps I was using, no longer cover all the
screen, as a result the location of heard stations has slipped quite
dramatically (They have all moved up and to the left).
Using the gifs, supplied with the original version of UIVIEW, staions are
displayed in the correct area, but map is still not covering the whole area
of the screen. (A large grey remains to the right and below the displayed
image of the map).
I have been running at 1024x768... Reducing the screen size increases
everything proportionally, and adds the scroll bars as expected, but the
calibration is still incorrect.
The original maps won't cover the screen at 1024x768, so that is correct
behaviour.

As regards calibration, the original maps are still calibrated correctly
on my test systems. Are other people finding that the original maps are
no longer calibrated correctly?

--
Roger Barker, G4IDE roger@...
Boston, UK

------------------------------------------------------------------------
Has ONElist changed your life?

Visit our homepage and share with us your experiences at ONElist of the Week!


Re: THE ANTI BRIGADE

Roger Barker
 

In article <000f01be8967$50421f20$ce5a95c1@pbncomputer>, Eddy Payne
<EJPayne@...> writes
Roger,
It's started. Down here on the South Coast this bull
was put out this morning. The massive increase it's talking about,
to the best of my knowledge, is three people.
[snip]

Yes, I was aware of the situation regarding GB7VRB, G8DHE and also one
of his remote sysops.

Surely a first step should be for the few users of UI-View to stop
digipeating via G8DHE's node and see if they then stop complaining?

Also, read the comments in the "Station Setup" section of the help about
sending beacons. Try and make sure that you aren't sending out beacons
too often - every 30 minutes is adequate - and that you aren't sending
out a UI-View beacon and also sending a beacon from your TNC BTEXT or
from WinPack.

Otherwise, the only advice I can offer is - Take heed of the "It Might
Not Be For You..." section of the UI-View help. There's no point in
getting involved in a battle with the local sysop over the use of the
program!

Anyone who understands BPQ and reads the comments from G8DHE will
realise that at least some of what he is saying is completely wrong, but
that isn't going to make him change his mind! I attempted to reply to
some of his previous comments via one of his users, without success.

Also, anyone who can do a few sums can easily show that the total volume
of traffic being generated by UI-View use will pale into insignificance
compared to a user downloading a few bulletins from the BBS.

The real problem is that:-

(a) An attitude has developed in the UK that "packet = using the BBS
network", and the packet channels are to be used for nothing other than
accessing BBSs.

(b) Packet has almost ceased to be an amateur radio mode. Not only do
some users never think of packet in terms of self-training and
experimentation, but they complain if anyone else does!

--
Roger Barker, G4IDE roger@...
Boston, UK


V0.74b Update Available

Roger Barker
 

I've just uploaded the V0.74b update to my web site. Please note that
this is only an update, not a complete installation system. The update
can be applied to V0.6b or later and includes all the changes made since
that version, you don't need to apply the previous updates before
applying this one. The url is:-



Please don't publicise the link outside this mailing list. Also, because
some of the changes involve fairly profound alterations to the code,
it's probably a good idea not to pass it on to too many people until a
day or two has elapsed, to allow any serious problems to be reported by
subscribers to this list.

Here is the relevant section of HISTORY.TXT:-

V0.74b 1999-Apr-17 1. If UI-View is running in WinpDDE mode, and you
close down WinPack, UI-View will also close.
2. Loading of GIF images now about twice as fast
as previous versions.
3. "Refresh Mode" options added to the
"Miscellaneous Setup" dialogue. Read the help for
the dialogue to find out what they do.
4. "Refresh Map" option added to the Action menu.
5. "Auto Refresh" option added to the Option menu.
If it is disabled, then stations are crossed out
and the callsign is greyed out, rather than
removed, when they expire or move. (Note that
various actions, such as changing the map or
changing the label colours, will always cause a
refresh, even if "Auto Refresh" is disabled.
6. Fixed a bug which caused the SSID of callsigns
six characters long to be lost when using host
mode KISS. E.g. GM4IDE-9 would appear as GM4IDE.
7. Fixed a bug with parsing the frame headers when
using a KAM.
8. Auto sort option added to the Miscellaneous
Setup. If it is enabled then the Station List is
sorted every time it is updated. The sort order is
most recently heard at the top. How usable it is
depends on the speed of your PC, and how many
stations you have in the list.
9. Sort button added to the Station List, to allow
sorting to be done manually.
10. Help updated to reflect the above changes.

--
Roger Barker, G4IDE roger@...
Boston, UK


Re: Idea and Questions.

Roger Barker
 

In article <924370390.2118189.0@...>, Keith Maton
<feek@...> writes
From: "Keith Maton" <feek@...>

From: Roger Barker <roger@...>
[snip]
The current method of loading GIFs is to convert them to a BMP using
GIF2BMP.EXE which you will find in the UI-VIEW directory, load the BMP
into the map window, and then delete it. Yours are obviously failing
during the conversion, so either the format is wrong, or GIF2BMP.EXE is
corrupted.
As said above, I've not used gif2bmp, so it can't be that. Should it
matter whether they are 87a or 89a gif format?
UI-View uses GIF2BMP.EXE to load the GIFs into the program. So, if it
has somehow become corrupted, it could cause a problem. However, it is
difficult to imagine corruption that would allow it to load some GIFs
but not others.

Both 87a and 89a load ok for me.

Anyway, V0.74b uses completely different code to load GIFs, and GIF2BMP
is no longer used, so it will be interesting to see if the problem goes
away.

--
Roger Barker, G4IDE roger@...
Boston, UK


THE ANTI BRIGADE

Eddy Payne
 

Roger,
It's started. Down here on the South Coast this bull was put out this morning. The massive increase it's talking about, to the best of my knowledge, is three people.

USE of UI frames and DIGIPEATING
Due to the recent massive increase in the use of UI frames and now the extended use of Digipeating, I have reluctantly decided >to turn of the digipeater on GB7VR. This was for the use of those needing to use the FBB broadcast mode on Winpack/TPK etc. >For those stations who are out of direct range of the BBS my apologies, you will need to find another BBS who's User channels >are not so badly affected.

For those of you who are creating UI frames being digipeated onto 432.675MHz please bear in mind that you are now blocking >both User channels into the BBS. Digipeated frames are sent without regard to the use of the AX.25 protocol and hence are >repeated without waiting. You might also bear in mind that for every packet that is sent via a digipeater the packet will be >repeated on EVERY channel that is enabled. Thus a 6 port Node allowing Digi'ing to all ports will generate 6 additional packets. >Currently the BBS sees the same UI frame repeated 3 times, the original, the digipeated packet on 144.950 and the digipeated >packet on 432.675, other Nodes may well see many more copies! You may also wish to bear in mind that for every UI frame sent >in a connected session then there will be 14 UI frames generated when digipeated via a 6 port node (original + 6 copies, >ACK + 6 copies).

IF the increase of UI frames and Digipeating continues to grow then to ensure that the BBS can continue to function, it will be >necessary to turn of the FBB broadcast protocol, this will obviously affect all users of the BBS - you will have to revert to >connecting and obtaining a list of messages manually and then selecting those messages to be read.

73 Geoff G8DHE @ GB7VRB - Sysop Worthing Video Repeater Group BBS
geoff@...
I did attend a meeting of the local packet user group (SUNPAC) and whilst they were not for or against the use of UI-View (they have agreed to put locators in the text of their beacons on BBs's and nodes) they have said that the auto digipeating facility was never switched on, on their nodes because of the increase in traffic it would generate.

Keep up the good work.

73 - Eddy, G6UQI