TinyTrak4 (its been a while!)

Well it has been quite a while since I last spoke about the TinyTrak4 So I suppose I should really start with a summery of feature changes in the latest Alpha Code.

source: tt4_alpha_v0.60.zip / readme.txt

Changes in v0.60
———————-
Added 9600 baud decoding and DEC96 command
Added BANK, BNKMODE and COPY commands
Added DDIST command
Renamed DIGI123 to PATH123
Removed PPATH12
Added HEADERLN command
Added DMETRIC command

Changes in v0.59
———————-
Fixed Bug with message sending timers

Changes in v0.58
———————-
Fixed SSID bug on digipeater callsign insertion
Added digipeated packets to PKTOCOM
Fixed bug parsing L in MIC-E dest call
Added TRNKMODE command
Added PAVP command
Fixed ^T temp when >= 100
Improved supply voltage reading

Changes in v0.57
———————-
Fixed a bug that prevented entering commands over 15 chars in the config menu

Changes in v0.56
———————-
Prevented sending of KISS Data Frames
Changed DIGIID to do callsign insertion, rather than substitution
Removed digipeated and serial generated packets from PKTOCOM
Fixed GPS Database Errors caused by GPS Waypoint from positionless weather reports
Added parsing of messages through IGATES (third patry)
Added parsing of messages without IDs
Added basic configuring via keyboard & display – Use F5
Changed default CDLEVEL from 8 to 20
Added RPATHDISP command
Added LEDS command

Changes between v0.54 and v0.55
———————-
Added FRAWDISP – Force packets to be displayed raw instead of parsed
Added HRAWDISP – Disables display of unparsed packets
Added EXPORT – Displays settings in a format that can be re-loaded
Added WYPTXT – Sends Waypoints to TEXT ports in addition to GPS ports
Added PKTICOM – Enables sending decoded packets to the computer TEXT and KISS ports
Added PKTOCOM – Send generated packets back to the computer
Added $PGRMW support (for altitude)
Added Variables in the status text (temp & voltage) ^V ^T ^t ^1 .. ^7
Defaulted > before BTEXT
Defaulted TOSV to true
Fixed support for GPSs with 3 digits after decimal in position

Changes between v0.53 and v0.54
———————-
Properly fixed MIC-E decoding Hemishpere decoding bug

Changes between v0.52 and v0.53
———————-
Fixed decoding short KISS packets (15 bytes long)
Fixed Altitude, course, speed bug in Waypoint output
Added GPS Relay (GRELAYBITS and GRELAYRATE)
Added GPS timing support for GPSs with 5 sec updates
Fixed TOSV bug
Fixed MIC-E decoding Hemishpere decoding bug (MIC-E L code)
Gave more time to enter menu with 3 ESC
Added APRS Compressed mode encoding

Changes between v0.51 and v0.52
———————-
Added keyboard decoding, UI Modes, and Text Messaging
Added Weather mode for Peet stations
Added WPERIOD and WXPOS commands
Defaulted DUPETIME to 30 seconds
Improved Carrier Detect Code
Changed LCD code organization

Changes between v0.5 and v0.51
———————-
All interrupt code re-written to improve occasional hangs
RXAMP should be about 1/4 of the value in the previous verion

Changes between v0.4 and v0.5
———————-
Display Altitude properly when missing as —
Display weather data, and changed position display
Added TXTDISP command (to display incoming serial text)
Enabled Power LED after first LED sweep
Changed ABAUD and BBAUD to full numbers (not div100)
Fixed SFFDELAY typo
Fixed Statusrate option type bug
Fixed Altitude lost due to incoming packets bug
Added NODISP command (disable display for digital telemetry)
Improved High Res Telemetry Clamping
Renamed PDELAY, TDELAY, BDELAY to PPERIOD, TPERIOD, BPERIOD
DESTCALL defaults to APTT4, and % restores that
Added PPATHING command (Proportional pathing)
replaced MICEMESSPATH with MICEMESSAGE and SSIDROUTE
Changed volts to be 10*volts in low res
Added DMSDISP option (display in DMS rather than DMm)
Added GWAYMODE command ($PKWDWPL & $PMGNWPL Magellean support)
Added MICETMV command and format
Changed MT-TT4 defaults
Added FILTERCALL command (BUDLIST)
Added SSIDROUTE command
Added TSTATUS command
Renamed TSB to SBEN
Renamed SBFDELAY SBSDELAY to SBFPERIOD SBSPERIOD

Now as I haven’t posted a change log before some of its content is now obsolete/substituted for new commands or functionality. There has also been some confusion when loading the Alpha Code, and then connecting a GPS and expecting the TinyTrak4 to just work! well you do need to configure it first! and just recently Byon has released a simple UI to achieve this. I must add, the the TinyTrak4 has two serial inputs and the default settings for those are that…

Serial Port 1: Speed: 19200 Parity: none Bits: 8 Stopbits: 1

Serial Port 2: Speed: 4800 Parity: none Bits: 8 Stopbits: 1

You need to make a custom Y cable (or purchase one from Byon) to access the second serial port as the DB-9 is wired to a non-standard meaning that if you attempt to use off the self cables the second serial port is in assessable! So once you have the Y-cable sorted then you have access to both serial ports.

I’ve successfully got my TinyTrak4D monitoring the ISS for APRS packets, and each morning there is something different displayed on the LCD screen!

I’m also making slow progress on the re-build of the TinyTrak4 wiki

7 Hosts & 50 Services – Icinga Rocks!

I’ve been working on my Icinga Monitoring service, to date I now have it successfully monitoring 7 hosts and 50 services!

So what am I monitoring ??? OK well, I only have a small home network, however I want to know just what is down at any stage! as I run my own Email/Web server its obvious that I want to know if there is a problem with this. I’m also monitoring the services required by the web-server , as in MySQL to ensure that the database is in good health, My sever also has a small UPS that uses NUT, So again just ensuring that all is OK there. I’m also ensuring the services that I make use of from my ISP (POP3, SMTP, HTTP & PING… are they there!) are accessible too, along with two other PC’s (My Desktop & Amateur Radio I-Gate)

If you are interested in how I have achieved this, then here is a link to the relevant files… Icinga-files Please feel free to add any suggestions or advice on these configuration files, as I’m still learning the basics about how they all do the magic that they do!  😉

7 Hosts & 50 Services – Icinga Rocks!

I’ve been working on my Icinga Monitoring service, to date I now have it successfully monitoring 7 hosts and 50 services!

So what am I monitoring ??? OK well, I only have a small home network, however I want to know just what is down at any stage! as I run my own Email/Web server its obvious that I want to know if there is a problem with this. I’m also monitoring the services required by the web-server , as in MySQL to ensure that the database is in good health, My sever also has a small UPS that uses NUT, So again just ensuring that all is OK there. I’m also ensuring the services that I make use of from my ISP (POP3, SMTP, HTTP & PING… are they there!) are accessible too, along with two other PC’s (My Desktop & Amateur Radio I-Gate)

If you are interested in how I have achieved this, then here is a link to the relevant files… Icinga-files Please feel free to add any suggestions or advice on these configuration files, as I’m still learning the basics about how they all do the magic that they do!  😉

Australia-first native ADSL IPv6 access trial

sourced from http://www.internode.on.net/news/2009/11/157.php

IPv6 is the next generation Internet Protocol that offers a vast number of new, longer IP addresses to overcome the upcoming exhaustion of new IP version 4 addresses, expected within the next two years.

Internode has operated a native IPv6 backbone since the middle of 2008, with routers running in ‘dual stack’ mode, allowing it to provide concurrent IPv4 and IPv6 services. However, to date, the only customers who could use IPv6 were those with a direct Ethernet connection to Internode’s network or those able to undertake the complex configuration required to “tunnel” IPv6 through an IPv4 connection.

Today’s announcement marks the first time an Australian broadband provider has offered IPv6 services running in native mode on its national ADSL network: This means that IPv6 can work directly with any Internode ADSL service, offering concurrent IPv6 and IPv4 PPP access with any router or computer that supports it.

The trial is intended for technically experienced customers who are familiar with IPv6; Internode expects any customers participating in the trial to be comfortable with IPv6 configuration and to provide feedback on the operation of the service, in order to assist Internode to deliver its full production-grade IPv6 service offering by mid 2010.

Internode managing director Simon Hackett said Internode appreciated the assistance of any technically experienced customers who wanted to participate in the trial. “This is the first public Australian national trial of native IPv6 for ADSL customers,” he said.

Our objective is to ensure that Internode has the most experience of any Australian broadband provider with the operation and support of native IPv6. By the time IPv6 becomes a necessary part of connecting new users to the Internet, Internode will offer the very best ‘production’ IPv6 service available in Australia. At that point, for all customers, IPv6 will ‘just work’.

Only a small number of consumer ADSL routers available in Australia currently support IPv6. Internode currently recommends using a Cisco device such as the Cisco 877 ADSL router running IOS 12.4 or above, or using an ADSL router placed into ‘bridge’ mode with a PPPoE based IPv6 connection directly from a personal computer. IPv6 support is built into current versions of Macintosh OS X, Microsoft Windows and Linux.

Internode is working with various manufacturers of ADSL2+ routers to encourage their support of native IPv6 access. Internode expects to announce the availability of IPv6 firmware support for a variety of ADSL2+ routers during the course of the trial.

Mr. Hackett continued: “There has historically been a ‘chicken and egg’ problem with IPv6, where ADSL router vendors have not supported IPv6 because no network was ready to run IPv6, and vice versa. We have broken that impasse – and we invite any further ADSL2+ router vendors with IPv6 capability to test those routers on our network and prove their own IPv6 readiness.