An interesting point to note which I and a few others have noted with
Tiny2's and their clones, is that
the kiss params need reloading on a regular basis, this also happens when a
dedicated kiss EPROM is used.
Getting to the point , the way to over come the former is to run a short
script with all the kiss params
controlled by cron.
I suspect that a similar method could be used to over come your tiny 2
dropping back to command mode. Just run a script putting it in kiss mode
every n minutes , where n is less than the period it
takes to change mode.
73 Richard G8JVM
-----Original Message-----
From: Brian Wilde [mailto:[EMAIL PROTECTED]]
Sent: 24 July 2000 21:45
To: [EMAIL PROTECTED]
Subject: Re Tiny2 & STA led
Hi All
Thanks to Richard & Paul for your notes on the Tiny2 jumping back to command
mode.
I have checked this out but it appears that the TNC is remaining in Kiss
mode.
So I rebooted to DOS and used Paket6 to put the TNC
back to the command mode with Alt k
The TNC runs fine in kissmode with DOS/BPQ and
with Windows98 running AGW Packet engine.
I have since noted that the TNC does not receive any packets when it has the
STA light problem. Restarting the TNC with the on/off switch has no effect
other than cancelling the STA light but still no packets are received.
I have found the only way to get it to work is to start with the TNC in
command
mode and then put it in kissmode from Linux. I can only think that on
shutdown
some rubbish is being left on the TNC but I would have thought that a
restart
would clear that.
I have also used the call programme with the same results.
I have managed to set up my Baycom board on bcsf0 and that works fine under
Linpac. :-)
I did an "ifconfig" and ax0 is up and running as normal
Interesting problem I suppose it might be a duff Tiny2!
CU
73's Brian
