OpenFIRE App Public Release 2.2 - Tsuzura

I2C fixes and tweaks

• GPIO pins are now color-coded with respect to their I2C lane - I2C0 pin pairs are colored blue, and I2C1 pin pairs are colored orange.
• When mapping I2C functions (either Camera SDA/SCL or Peripheral SDA/SCL), the current pin layout is checked to ensure that a Camera function isn't mapped in the same lane as a Peripheral function, or that the Camera/Peripheral partner of a pair (Data or Clock) aren't already mapped to the opposite lane; if either condition aren't met, the offending pin is unmapped with an appropriate message printed in the status bar.
• Changes to NeoPixel settings will appropriately notify that a reboot might be required to see changes properly reflected, as it's a limitation of how the NeoPixel library handles pixel strand remapping.
• Raspberry Pi Pico (W) and Arduino Nano RP2040 Connect default layouts now properly reflect a default Temperature Sensor mapping that was added in the last released OpenFIRE Firmware.
• App now correctly parses version numbers with alphanumeric characters, e.g. git hashes attached from firmware GitHub artifacts.

Installation

For Windows users, extract to wherever is most convenient. Run OpenFIREApp.exe
For Linux users, Arch Linux has an AUR PKGBUILD available @ openfireapp, installable using your favorite terminal/AUR helper. For other distros, use OpenFIRE_App-x86_64.AppImage.
Your user should be a part of the dialout library to be able to access serial ports--the app will alert you and provide the command to copy-paste into a terminal to add your user to said group. For other distros or architectures (i.e. Raspberry Pi/ARM systems), refer to the README for build instructions for your system.

At the moment, a microcontroller running OpenFIRE needs to be plugged in before starting! Hopefully this will change in a future app update.

OpenFIRE App Public Release 2.1 - Aino

Calibration Message Fix

There has been enough time spent in release candidacy, and all of the early concerns have been resolved, so the app is at a good place now to be in normal release schedule.

Along with all the fixes from the release candidates, this version resolves the calibration message not being updated to reflect the current calibration system. It's a small scale fix, but it was felt that the confusion caused by leaving this unresolved was enough to justify the new release.

Installation

For Windows users, extract to wherever is most convenient. Run OpenFIREApp.exe
For Linux users, Arch Linux has an AUR PKGBUILD available @ openfireapp, installable using your favorite terminal/AUR helper. For other distros, use OpenFIRE_App-x86_64.AppImage.
Your user should be a part of the dialout library to be able to access serial ports--the app will alert you and provide the command to copy-paste into a terminal to add your user to said group. For other distros or architectures (i.e. Raspberry Pi/ARM systems), refer to the README for build instructions for your system.

At the moment, a microcontroller running OpenFIRE needs to be plugged in before starting! Hopefully this will change in a future app update.

OpenFIRE App Public Release (Candidate) 6 - Aino

The Help & Consistencies Fix

There seemed to have been some confusion regarding the TinyUSB functionality, so this release helps to alleviate the problem with the most pertinent info baked into the app; namely:

• The TinyUSB area now has section captions informing the user of the necessity of different gun identifiers for multiplayer usage.
• Both the simple and advanced TinyUSB section views will display some text informing the user of how the functionality of the Start & Select buttons changes (or doesn't) depending on the selection.
• And, just in case they haven't seen it yet, there is a new Help section in the app menu, with links to both the OpenFIRE Enclosed Instruction Book as well as the OF Wiki page documenting serial functionality at a high level (which also links to the Mamehook deep dive).

This update also contains a clarification on the Autofire toggle functionality, both in updated tooltip text and it only allowed to be enabled if either Solenoid or Rumble FF are also active; as well as disabling any settings related to Hold to Pause, Solenoid Timings, and Rumble Strength/Length if their master toggles are disabled. Alongside this, solenoid and rumble settings will be forcefully unchecked and disabled if they are unmapped in the current pins layout, either board default or custom.

Installation

For Windows users, extract to wherever is most convenient. Run OpenFIREApp.exe
For Linux users, Arch Linux has an AUR PKGBUILD available @ openfireapp, installable using your favorite terminal/AUR helper. For other distros, use OpenFIRE_App-x86_64.AppImage - this will be the standard going forward, as well as this being the last release to use the Ubuntu 22.04-based binary.
Your user should be a part of the dialout library to be able to access serial ports--the app will alert you and provide the command to copy-paste into a terminal to add your user to said group. For other distros or architectures (i.e. Raspberry Pi/ARM systems), refer to the README for build instructions for your system.

At the moment, a microcontroller running OpenFIRE needs to be plugged in before starting! Hopefully this will change in a future app update.

OpenFIRE App Public Release (Candidate) 5 - Aino

Fix Those Chains, Batman!

• Fixes cases where static NeoPixel counts could exceed the length of a NeoPixel strand, which is ILLEGAL (though would be harmless when deployed to the FW as it handles this, but would still be no less confusing to the user).
  • Now if the static Pixel count is detected to be bigger than the strand length, the value will be forced to the strand length value.
  • Also if the NeoPixel strand length is decreased below the current static Pixel count, the latter will be forced to the new length of the strand.
• Fixes static pixel color boxes all being available on sync, even when the count of static pixels is less than the maximum of 3 Pixel(s).

Installation

For Windows users, extract to wherever is most convenient. Run OpenFIREApp.exe
For Linux users, Arch Linux has an AUR PKGBUILD available @ openfireapp, installable using your favorite terminal/AUR helper. For other distros, you may try your luck with the Ubuntu binary (built against Qt 5.15 libraries). Your user should be a part of the dialout library to be able to access serial ports--the app will alert you and provide the command to copy-paste into a terminal to add your user to said group. For other distros or architectures (i.e. Raspberry Pi/ARM systems), refer to the README for build instructions for your system.

At the moment, a microcontroller running OpenFIRE needs to be plugged in before starting! Hopefully this will change in a future app update.

OpenFIRE App Public Release (Candidate) 4 - Aino

Yet More Fixes

• Includes yesterday's hotfix for displaying an error if a camera-related string is detected instead of the sync message it expects.
• Changed the Profile "Layout" setting from an ambiguous checkbox to a combobox with both possible settings clearly labeled. This should resolve any confusion regarding how to setup diamond layout cali profiles. The text strings in the profiles tab also have correct centered alignment.
• Adds support for preset layouts for future addon board makers to make their setups easier. Currently, this only provides an alternate layout for the Adafruit ItsyBitsy boards for SAMCO 1.1, which has a different layout from this model's default layout of SAMCO 2.0.

Installation

For Windows users, extract to wherever is most convenient. Run OpenFIREApp.exe
For Linux users, Arch Linux has an AUR PKGBUILD available @ openfireapp, installable using your favorite terminal/AUR helper. For other distros, you may try your luck with the Ubuntu binary (built against Qt 5.15 libraries). Your user should be a part of the dialout library to be able to access serial ports--the app will alert you and provide the command to copy-paste into a terminal to add your user to said group. For other distros or architectures (i.e. Raspberry Pi/ARM systems), refer to the README for build instructions for your system.

At the moment, a microcontroller running OpenFIRE needs to be plugged in before starting! Hopefully this will change in a future app update.

OpenFIRE App Public Release (Candidate) 3 - Aino

Welcome to OpenFIRE!

After nearly a year of cumulative work, this is the first second third Release Candidate of the OpenFIRE project. This is near-final initial release code as far as features and performance are concerned, but there might be some bugs hidden in certain odds and ends - so if you run into any problems, don't hesitate to make an issue about it!

That said, the OF App has no known issues, as far as I (@SeongGino) am concerned.

EDIT: Binaries were updated June 25th @ 4:05 PM to add a catch for crossed camera wire errors.

Installation

For Windows users, extract to wherever is most convenient. Run OpenFIREApp.exe
For Linux users, Arch Linux has an AUR PKGBUILD available @ openfireapp, installable using your favorite terminal/AUR helper. For other distros, you may try your luck with the Ubuntu binary (built against Qt 5.15 libraries). Your user should be a part of the dialout library to be able to access serial ports--the app will alert you and provide the command to copy-paste into a terminal to add your user to said group. For other distros or architectures (i.e. Raspberry Pi/ARM systems), refer to the README for build instructions for your system.

At the moment, a microcontroller running OpenFIRE needs to be plugged in before starting! Hopefully this will change in a future app update.

Rolling Pre-release builds

Test builds for the (roughly) current state of the repo.

Last updated: June 8th @ 2:34 PM