Flight Logs 64-bit Version Install Bug – Corrected

Flight Logs home page

We were recently notified of an installation bug in the 64-bit version of Flight Logs, release 8.5.2 BETA. When a user attempted to install the Flight Logs software, it would indicate that a file was missing and could not continue.

Upon being notified of the issue, we discovered that the download file on SourceForge was corrupted. This file was removed from the downloads listing and a new version was uploaded.

This new version is now listed as Flight Logs 64-bit 8.5.2 BETA 2. If you have previously downloaded the earlier version and found it would not install, we encourage to download this version and install it.

This issue only applies to the 64-bit version installation file. The 32-bit version and the Developers version are not affected. Further, there is no issue with the Flight Logs database itself. The error was contained wholly within the set-up program.

Update on Flight Logs Software

This post is to provide a quick update on the status of the Flight Logs software. I am afraid the news is not encouraging. You may have noticed that updates to the software has basically stopped. Let me explain what has happened.

Back on August 8, 2022, Microsoft announced that Windows updates would block VBA macros that originate from the Internet (https://learn.microsoft.com/en-gb/DeployOffice/security/internet-macros-blocked). Further, a banner would be displayed indicating that there is a security risk involved in running the software.

Then on January 17, 2023, Microsoft announced that an upcoming Windows update will scan user’s computers to “identify the number of users who are running out-of-support (or soon to be out-of-support) versions of Office, including Office 2013, Office 2010, and Office 2007.” (https://support.microsoft.com/en-us/topic/january-17-2023-update-for-office-2013-office-2010-and-office-2007-kb5021751-f4a23c1d-4d1f-44ba-a43a-7a5528afb4ea).

Flight Logs is developed using Microsoft Access 2010. It uses VBA to provide the underlying code, as well as several macros. It uses a “runtime” file that allows anyone to run the software even if they do not have Access installed on their system.

Given that Microsoft is already blocking software that uses VBA/macros and putting up scary banners, along with the recent news of their plan to scan for old versions of the software, I firmly believe that Microsoft will soon have barriers in place to stop the software from running.

Right now I am in a “holding pattern” to see the fallout from these recent Microsoft updates, but I am not optimistic. It is very discouraging to invest the amount of time in developing a program such as Flight Logs and see a warning banner indicating it is “security risk.” Such “warnings” can give the impression the other items I provide through the web site are also a security risk.

For now we have the latest release of the software still available on SourceForge. So far I haven’t seen a decrease in the number of downloads so that is encouraging. However, if Microsoft continues down its current course, I will likely remove Flight Logs from SourceForge.

Lastly, I want to thank the folks that have supported the Journal in general and the Flight Logs software in particular.

Flight Logs Version 0.8.5.2 BETA Now Available

This is the eleventh release of the Flight Logs Access database software. It should be considered BETA level software and not for use in a production environment. This is the first release in the 0.8 BETA series. You can download it from our SourceForge repository at https://sourceforge.net/projects/flight-log/files/

This version of the database is being release while work continues on several programming areas and user documentation. This release includes a number of fixes.

Bugs/Issues Resolved

The primary purpose of the 0.8 series is to focus on correcting any issues that are present/known in the software. This is in preparation for the 0.9 series which will be the Release Candidate (RC) versions. There are no new features in this release, nor are any expected until after the version 1.0 release.

The following is a listing of bugs/issues resolved in this release:

Summary

• 3D Printer Preferences – Tab moves to new record
• 3D Printer Preferences – Tab Order
• All Forms – Set Focus based on tab clicked
• Builder & Maintenance Preferences – tab goes to new record
• Builders Log-Tab Order
• Damage Assessment-Add option
• Design Preferences – All tabs Type-tab goes to new record
• Design Preferences Rocket Type-tab order
• Fleet Record – Plan Info Button still a macro
• Fleet Record – Refresh Database
• Fleet Record – Scratch-built Info Button still a macro
• Fleet Record – Tab Order
• Fleet Records – Engine Delay
• Fleet Records – Form Tabs
• Fleet Records – Glider Option Not Selected on Lifting Body
• Fleet Records – Glider Specifications “Invalid use of Null”
• Fleet Records – Preferences
• Fleet Records – Refresh database
• Fleet Records – Tab Order
• Fleet Records – Vehicle Specifications “Invalid use of Null”
• Fleet Records Screen – Recovery Options
• Fleet Records – Status drop-down activates wrong log button
• Fleet Records-Completion Date
• Flight Card Listing – Center Data Fields
• Flight Card Listing – Center Motor Info
• Flight Card Listing Report – Extend lines under data fields to left
• Flight Card Report Date Criteria – Start and end date loop
• Flight Card should only show active rockets in drop down
• Flight Card-Combo Box Headers
• Flight Card-Retain previous entry
• Flight Log – First Flight default selection in Rocket Name Drop-down
• Flight Log Form – Engine Manufacturer Required Entry
• Flight Log Form – Rocket Name Error after selection
• Flight Log Form – tab goes to next record
• Flight Log Form – Tab Order
• Flight Log Form – Time Display
• Flight Log form – Time missing leading 0
• Flight Log Form and Report – minimize form when report is displayed
• Flight Log-Combo Box Headers
• Forms (all) – check for tab order and cycling through all records
• Help File – Preferences Landing Page
• Help File – Preferences Program and Data
• Individual Flight Card – Color data
• Individual Flight Card – Only displaying 1 card per page
• NARTREK form – tab order is incorrect
• Need Scale and Glider type
• No Link to Web Site from Help File
• Personnel Form – Tab Order
• Personnel Form-Web site addresses
• Report Date Criteria Form – Cancel brings up error
• Scratch Built Info – tab cycles to new record
• Update Flight Status – tab ignores OK button
• User name/organization changes to a white bar if clicked on
• Vendor Preferences – Tab Order
• Wrong web site address

Work continues on the Flight Logs program as we are getting closer to the Version 1.0 release. If you discover any issues with the software, please let us know via the Issues section on  SourceForge or sending us an email at austin.aerospace.education@gmail.com.

Flight Logs & Arduino Launch Control System Status Update

Flight Logs Software Status

You may remember that after our last release of the Flight Logs database program, we indicated that the overall development was locked and that the program was entering a bug finding period. So far, there have been over 75 issues that have been identified and corrected. We are still working on this initial round of bug fixes, so that number will likely continue to grow.

Our hope is to have our first BETA release by the end of this month. There will be no new features, nor will there be any updates to the Help file. Help file updates will begin after the BETA period is over.

We are hoping to have a Release Candidate version available sometime in December, with a Version 1.0 release sometime early in 2023.

Arduino Launch Control System Software Status

Like the Flight Logs software, the Launch Control System software has also been going through BETA testing as well. This has been in conjunction with the Launch Control System series of posts here at the Rocketry Research Journal. We are pleased to report that the BETA testing is nearly complete and we hope to have a BETA release before the end of the month. If things continue to progress as expected, Version 1.0 will be released before the end of the year.

Of Temperatures and Altimeters

Ever since model rockets first took flight, the one question that has always been asked is “How high did it go?” In the past we would use theodolites and trigonometry to answer that question. In more recent years as our electronics became smaller and lighter, we were finally able to place altimeters on the rocket. This allows us to obtain a much more accurate altitude reading. Or does it?

Bill Cook is a rocketeer out of Huntsville Alabama and writes a blog called the “Rocketeer’s Corner.” His blog carries the usual stories about his rocket builds and the launches he attends. But it also carries some interesting stories on the science (and math) behind how things work.

Several recent blog posts have discussed some of the issues he has encountered when working with altimeters. In one blog post (NARCON Solves a Mystery) Bill discusses how he was having issues with a sharp dip in his altitude readings when the ejection charge went off. He had tried several fixes but had no luck in getting rid of the error. NARCON 2021 brought about the fix for this issue.

Two more recent posts (Learning More About Altimeters… and The Factor that Many TARC Teams Ignore) dealt with commercial altimeters and how those altimeters calculate altitude. He also describes a weakness in those altimeters and how it can cause issues for those using them in competition – especially the TARC competition.

Once we read about this issue we knew that it was something we wanted to address in the Flight Logs data software. In Version 0.7.4 a new checkbox(Adjust altimeter measurements to compensate for actual air temperature) was added into the Program and Data Preferences screen (highlighted in red). When this box is checked it will adjust your altimeter readings based on the actual air temperature readings at the time of the launch. This assumes that you have entered the temperature at the time of the flight. If the temperature is not entered, no adjustment is possible.

We also know that not all altimeters have this flaw. For example, I am currently working on an electronic altimeter using the Arduino and the BMP180 sensor. This sensor provides both pressure readings and temperature readings. Since the temperature is recorded in real time with the pressure, the adjustment Bill describes is not required.

In the next version of Flight Logs we will adjust the coding to include not only the default of adjusting altitude for all flights, but that you can also perform the calculation on a flight by flight basis.

If you have never seen Bill Cook’s blog I would encourage you to stop by and take a look. It is always interesting reading. You might want to bookmark it in your browser.