------------------
At our local node we want to install an USV-battery, which signalizes that
power goes down in about 3 min. Is there any way to tell this to Clusse, to
shutdown normally ? I think Clusse is 'power-off' resistant, but normally
its better to shut down a program to finish all disk-activity.
-----------------

2. LOGin-command

VHF-DXers want to see after login only the last 20 spots of eg. 2m and 70cm,
without any shortwave spot! That's no problem AK1A's USERCMD.

-----------------

> Btw, BPUT needs an ending # to send the acknowledge message and I have to
> send this manually. I don't think, that this is a bug in my packet programm
> (GP/2), maybe the definition of the BPUT protocoll isn't exactly enough ?

  Which ack message? The #OK# ?

  The document defining the protocol isn't very exact (wouldn't be good
for an RFC). And... i wrote my implemention before found out the
definition EXISTED... by reverse engineering 8-)  And i haven't compared
it against the definition. Have to check it out.

---

some utilities:         HEAD.COM        (view the head of a file, ie. log file)
                        TAIL.COM        (view the tail of a file, ie. error.log)



From hessu@pspt.fi Tue Jun 24 20:11:21 1997
Date: Mon, 23 Jun 1997 11:16:23 +0300 (EEST)
From: Heikki Hannikainen <hessu@pspt.fi>
To: oh7lzb@funk.oh7lzb.ampr.org
Subject: bug report (fwd)

---------- Forwarded message ----------
Date: Mon, 23 Jun 97 03:02:33 -0400
From: pa3ezl@unix.ve3mch.ampr.org
To: hessu@pspt.fi
Subject: bug report

Hello Hessu,

This weekend clusse crashed again due to yet another crc error... Here is the
error.log:

21.06.97 18:58:06 I/O Error 154 occurred while reading netusers.clu:
  CRC error in data
  Uptime 4d 2h3m41s
21.06.97 18:59:48 I/O Error 154 occurred while reading c:\clusse\data\netusers.clu:
  CRC error in data
  Uptime 1m30s
PI5EHV-8 0805>

It seems that the error occurs when netusers.clu exceeds a certain size...
Every time that crc error occured we renames the file and restarted clusse.
Here's the list of the /data directory

  Directory of c:\clusse\/data\*.*  (CLUSTER)
.              <DIR>   01.01.80  08:51
..             <DIR>   01.01.80  08:51
users.clu        4368  23.06.97  07:57
netusers.ezl    57768  12.06.97  12:57
nodes.clu         238  23.06.97  07:51
dx.clu        2091305  23.06.97  07:57
announce.clu    70599  23.06.97  06:26
wwv.clu          9438  23.06.97  03:20
helpindx.clu     1500  07.05.97  23:09
frtnindx.clu    11704  15.07.95  17:32
last.clu       144032  23.06.97  07:48
status.clu          8  23.06.97  07:57
mid.clu         22000  23.06.97  07:57
convpers.clu        0  02.04.97  05:53
netusers.old   125496  16.06.97  07:46
netusers.rja   155957  21.06.97  21:46
netusers.clu    84411  23.06.97  07:57
  2 778 824 bytes in 17 files. 24 918 016 bytes free.
PI5EHV-8 0758>


Any progress on implementing PC frame filtering or HOPS control?

73 de Aurelio

ps. Send any reply to aurelio@esrac.ele.tue.nl, tnx.
From hessu@pspt.fi Tue Jun 24 20:11:30 1997
Date: Tue, 24 Jun 1997 19:52:30 +0300 (EEST)
From: Heikki Hannikainen <hessu@pspt.fi>
To: oh7lzb@funk.oh7lzb.ampr.org
Subject: run_time error  (fwd)

---------- Forwarded message ----------
Date: Sun, 15 Jun 1997 20:36:23 -0600 (CST)
From: "Aurelio Bellussi (PA3EZL)" <a.m.m.bellussi@stud.tue.nl>
To: hessu@pspt.fi
Subject: dx format

Hello Hessu,

Version 031-B6 has been running for a while now at PI5EHV-8. No more
run time errors BUT frequent I/O error 158 or 154 while reading netusers.clu
file, CRC error. Even after we've deleted the old netusers.clu and checked
the hardisk for any errors. At some time sunday after being UP for almost
two days something strange happend. Every time someone attempted to login on
to clusse the connection was disconnected and CLUSSE rebooted itself. After
startup the automatic linking started and was completed, but no spots were
forwarded over the active links...

Now for my question: In version 031-B6 we use at pi5ehv-8 the format of the
dx spots changed to the format Pavillion type cluster uses. At home I've the
same .zip file but the spots are of the familiar (short) clusse format. I
can't find any clue in any doc or help file as how to change the dx spot
format send to connected users... Can you help?

73 de Aurelio


***********************************************************************
*  Aurelio M.M. Bellussi, student at the University of Technology in  *
*                         Eindhoven, the Netherlands                  *
*  Licensed Radio Amateur Operator, Callsigns: PA3EZL,  AA2WH         *
*  Also member of Radio Clubs: PI4TUE/PI5EHV, PI9IRC, PI4VLB and OT6A *
*                                                                     *
*  E-mail address:           a.m.m.bellussi@stud.tue.nl    OR         *
*                            pa3ezl@esrac.ele.tue.nl                  *
*  Amateur packet address:   pa3ezl@on5vl.#lg.bel.eu                  *
***********************************************************************
From hessu@pspt.fi Mon Jun 30 18:36:15 1997
Date: Fri, 27 Jun 1997 09:02:54 +0300 (EEST)
From: Heikki Hannikainen <hessu@pspt.fi>
To: Rolf Schmidt <r.schmidt@tu-bs.de>
Cc: oh7lzb@funk.oh7lzb.ampr.org
Subject: Re: new features for Clusse


  Hi Rolf,

On Fri, 27 Jun 1997, Rolf Schmidt wrote:

> 1) LConnections <call> list connections for a specific callsign

  It's been on my mind too.

> 2) command for the local userlist, the workaround is now U DB0FC-5, but this
> is rather long in comparision with the other clusse commands

  Hm... any suggestions for a shorter command name? Both logical and not
conflicting too much with the old commands (i already have UList for
listing the local user file... ULOcal?) ?

> 3) ST Protocol should list the uptime automatically, because all counters
> get cleared on reboot

  Okay, sounds sensible.

> 4) ST Protocol <node> protocol statistics for a specific neighbour node
> partner

  Ok... it only takes some 50*4+10 bytes of memory per link.

> 6) hop count matrix to setup the hop counts for each node and PC-frame

  Much requested... as soon as i figure out a good way to do it... the hop
counter system is seriously broken in the PacketCluster, so it is not
really able to do all the stuff it should be... (read tech.doc, the part
about the PC protocol... the largest bug is explained there)


---

From hessu@pspt.fi Mon Jun 30 18:37:09 1997
Date: Sun, 1 Jun 1997 22:25:39 +0300 (EEST)
From: Heikki Hannikainen <hessu@pspt.fi>
To: oh7lzb@funk.oh7lzb.ampr.org
Subject: Re: more remote operation hints (fwd)



I would prefer the following, but not all are stored in CLUSSE.CFG

1) New command for adding a NEWS line without entering date/time &
transfering    the complete news.txt file
2) New command for debuging a link (LINK DEBUG ON/OFF) without modifying
3) Configurating LINKS.INI (maybe you move this also to CLUSSE.CFG ?)
4) Change expiration hour / settings
5) Change sound settings (sound package isn't yet available, or ?)
6) Change default settings for a new user


---------- Forwarded message ----------
Date: Wed, 25 Jun 1997 07:51:17 +0200 (METDST)
From: Rolf Schmidt <r.schmidt@tu-bs.de>
To: oh7lzb <hessu@pspt.fi>
Subject: Clusse 0.31 & excluded users

Hellu Hessu,


Another thing occured during the cw-fieldday, where I tried to put up a
listen only link to my neigbour node (he runs AK1A). This listen only link
was the only one in links.ini, so that i have no outgoing spots. But this
doesn't work, Clusse gets stucked during reboot. I cannot realize why
because of the remote-operation I cannot have a look on the screen 8-)
Do Clusse need at least one link with outgoing data ?
Maybe in the next version you can redirect the initial start screen into a file.

73, Rolf+


--
Dipl.-Ing. Rolf Schmidt, Institut fuer Eisenbahnwesen und Verkehrssicherung
                         Technical University Braunschweig
                         Rebenring 18, D-38106 Braunschweig, Germany
                         Tel.  : +49-531-391-3645
                         FAX   : +49-531-391-5766
                         EMail : r.schmidt@tu-bs.de or dl3lar@amsat.org

From hessu@pspt.fi Mon Aug  4 19:06:47 1997
Date: Mon, 4 Aug 1997 17:48:18 +0300
From: Heikki Hannikainen <hessu@pspt.fi>
To: oh7lzb@oh7lzb.ampr.org
Subject: Re: Hop counts (fwd)


  I strongly believe that majority of the sysops don't really know how the
network works, or the meanings of the different PC messages. Thus, if they
have to configure filters per PC message, it results in a broken network.
At least here, it has happened.... like, sending PC16 with larger hop
counter than PC17.

  I've thought about having two filter tables per link, one for outgoing,
one for incoming data. Something like in the dx spot filter. Both tables
could be in the same file, ie:

oh1rbi.flt could look like this:

#
# OH1RBI outgoing filter:
#
out:
 dx    from node vk* hop -10   # all spots from finnish node: reduce
                               # hop counter by 10
 users from link !oh* no       # Don't send users from foreign links
 nodes from link !oh* no       # No nodes either
 ann from call !oh* no         # And no foreign announcements
#
# OH1RBI incoming:
#
in:
 dx from node sm* hop 1        # Drop hop counter to 1, so that they
                               # are not forwarded anywhere from here

  And so on... how would that sound, people? Complicated enough? Comments,
please...

  Of course, you could choose the filter file name per link in links.ini,
so that the same table could be used for many links. And you could change
filter files 'on the fly'.

---
 < Heikki Hannikainen      <> ax.25:   oh7lzb@oh7rba.fin.eu   >
 < Internet: hessu@pspt.fi <> Amprnet: oh7lzb@oh7rba.ampr.org >

From hessu@pspt.fi Mon Aug  4 19:07:01 1997
Date: Mon, 28 Jul 1997 16:06:47 +0300 (EEST)
From: Heikki Hannikainen <hessu@pspt.fi>
To: Rolf Schmidt <r.schmidt@tu-bs.de>
Cc: oh7lzb@oh7lzb.ampr.org
Subject: Re: Clusse 0.31 user info bug


  Hello Rolf,

On Mon, 28 Jul 1997, Rolf Schmidt wrote:

> I've just upgraded DB0FC-5 to version beta 9. I've found out, that I can
> reproduce the reported crash, which occured in the beta 6 and I'll try it
> our this evening. Therefor I've to activate another .CON file. The crash
> occured a second time with especially that connect-script. I'll keep you
> informed.

  Which bug are you referring to? Reported when? What .con file? I don't
remember any more... i get lots of mail, you know. Please, when referring
to a previous message, do quote the message!

> If you start clusse and all network user logged in (after finishing
> handshake with the neighbour node) have a look at the userlist and choose a
> call which is marked as away (). Then list the user info to this call and
> you'll see, that the time 'Away since ...' is wrong. Sometimes it gets
> initialized like 1.1.97 00:00
> and sometimes junk appeared.

  Ah, ok. Sounds like an obvious one...

> Something strange happens, if an external called DOS programm (I tried 'dos
> time hh:mm') produces no output.

 'time' is not a program. It's a command in the shell (command.com).

> Clusse sends the output of the last called
> program with 'real' output (here 'dos type c:\clusse\db0eam.con').

   Heh. Ok, i'll take a look at that one too.

---
 < Heikki Hannikainen      <> ax.25:   oh7lzb@oh7rba.fin.eu   >
 < Internet: hessu@pspt.fi <> Amprnet: oh7lzb@oh7rba.ampr.org >

sh/head dl
DL Germany-DL: 237 degs - dist: 968 mi, 1558 km  Reciprocal heading: 42 degs

sh/head ua9
UA9 Asia-Novosibirsk-UA9: 74 degs - dist: 2106 mi, 3389 km  Reciprocal
heading: 304 degs
UA9 Asia-Russia-Perm-UA9: 86 degs - dist: 1114 mi, 1793 km  Reciprocal
heading: 293 degs

sh/head zs
ZS So-Africa-ZS1-ZS: 185 degs - dist: 6507 mi, 10473 km  Reciprocal heading:
3 degs
ZS So-Africa-ZS5-ZS: 175 degs - dist: 6230 mi, 10026 km  Reciprocal heading:
357 degs
ZS So-Africa-ZS6-ZS: 177 degs - dist: 5968 mi, 9604 km  Reciprocal heading:
358 degs

sh/head sv5
SV5 Dodecanese-SV5: 175 degs - dist: 1640 mi, 2640 km  Reciprocal heading:
357 degs


Subject: Clusse 0.30f (fwd)

Are you working on any kind of watchdog ? PR-MFS knows one: it triggers an
printer or rs-232 portbit to which you connect a MAX691. If permanently
trigger fails due to a software hang, the MAX691 causes a hardware-reset.

Alternate routes to cluster nodes:
clx knows up to 5 routes to a cluster node. If one route fails or is timed
out during connect, the linker tries another route. This is very useful at
my location because of up to 4 routes to my neighbor cluster node. Maybe you
can copy this idea from clx.

Sysop news:
If I add a news-message to the NEWS.TXT, I've to restart clusse for indexing
the new message. Is there a possibility for doing it without restarting ?
Maybe you can also re-index the other lists during runtime ?

-----------------------------

Subject: Formula (fwd)

Date: Mon, 3 Jun 1996 18:42:00 +0200 (MET DST)
From: Kjell Duna <kjelld@sn.no>
To: hessu@pspt.fi
Subject: Formula

Hi Heikki !

This is what I found :

Two formulas are used. (distance and bearing)

cos D = sin A sin B +  cos A cos B cos L (1)
sin C = cos B csc D sin L                (2)

where A = your latitude in degrees
      B = the other location in degrees (positive for N latitude , 
          negative for S latitude).
      L = lontitude difference between you and the other location.
      C = the direction of the other location from yours, in degrees
          East or West from North or South.
      D = distance along path, in nautical miles or minutes of arc 
          (1 min = 1 nautical mile = 1.15078 statute mile).

Example 1 :

Chicago = 41 52 N, 87 38 W
Cairo   = 30 00 N, 31 14 E

A = 41 52
B = 30
L = 87 38 + 31 14 = 118 52

cos D = sin(41 52) X sin(30) + cos(41 52) X cos(30) X cos(118 52) 
      = .6774 X .5 + .7447 X .8660 X (-.4828)
      = .3387 - .3114
      = .0273
    D = 88 26 = (88 X 60 + 26 = 5280 + 26 min.
      = 5306 nautical miles
      = 5306 X 1.15078 = 6106 statute miles or
      = 5306 X 1.852   = 9827 kilometers

Example 2 :

sin C = cos(30) X csc(88 26) X sin(118 52)
      
                    1                    .7584
      = .8660 X ------------ X .8758 = -------- = .7587
                 sin(88 26)              .9996

    C = 49 21

I guess that your computer will do the calculations for you in sinus,
cosinus and cosecans.....

This is the best I could get you. Source code for the programs that I told
you abt. are not available.

I hope this will be to some help for you !

73 de Kjell


