the Fluctus flight computer

The Rocketry Forum

Help Support The Rocketry Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
This is fantastic news. So now, I have to ask. Does anyone have good recommendations for daylight readable Android tablets? I’m an iOS guy, so don’t really have any experience in the Android side. I bought a Tablet last week to try out, but when outside in the sun it’s useless.

Did you solve the screen issue? what tablet are you using?
 
It's finally here !


1723338386640.png


The new Stead
yBlue bluetooth ground station is available for sale separately on silicdyne.net/products, for those who want to upgrade their Fluctus setup. The FluctusTelemetry mobile application is currently being updated for both Android and iOS to take full support of it.

They will also be available soon on Wildman and ModelRocketsUK.
 
Last edited:
It's finally here !


View attachment 660537


The new SteadyBlue bluetooth ground station is available for sale separately on silicdyne.net/products, for those who want to upgrade their Fluctus setup. The FluctusTelemetry mobile application is currently being updated for both Android and iOS to take full support of it.

They will also be available soon on Wildman and ModelRocketsUK.
Can't wait to get mine!
 
It's finally here !


View attachment 660537


The new SteadyBlue bluetooth ground station is available for sale separately on silicdyne.net/products, for those who want to upgrade their Fluctus setup. The FluctusTelemetry mobile application is currently being updated for both Android and iOS to take full support of it.

They will also be available soon on Wildman and ModelRocketsUK.
Just got it. Now I just need the iOS app. Also some basic instructions might be helpful. 😉
 
A new update has just been released which should make channel management a little more convenient for people using Fluctus at Balls32 from tomorrow.

Now when Fluctus starts up, its ID number is also displayed on the screen. This is an important value that needs to be kept in mind because it's this number that will ease you to check that you're listening to the right flight computer at launch. In the softwares this ID is also prominently shown.

As soon as you plug it in, it will check if there's any activity on the configured radio channel, and if there is, it will switch to the next channel automatically (e.g. if it's on channel C, it will switch to D). If it needs to make this change, you'll hear a long low-pitched beep followed by a series of high-pitched beeps indicating the new channel (1 beep = A, 2 = B, etc.).

Otherwise, the easiest way to verify your channel is to use the new proximity scan feature on the ground station:
press and hold the main button to start the scan, and after a few seconds, you'll have every Flutus or Reperix that have been detected displayed on the screen with their respective channels, and of course their unique ID.

1726794003702.png
 
Last edited:
A new update has just been released which should make channel management a little more convenient for people using Fluctus at Balls32 from tomorrow.

Now when Fluctus starts up, its ID number is also displayed on the screen. This is an important value that needs to be kept in mind because it's this number that will ease you to check that you're listening to the right flight computer at launch. In the softwares this ID is also prominently shown.

As soon as you plug it in, it will check if there's any activity on the configured radio channel, and if there is, it will switch to the next channel automatically (e.g. if it's on channel C, it will switch to D). If it needs to make this change, you'll hear a long low-pitched beep followed by a series of high-pitched beeps indicating the new channel (1 beep = A, 2 = B, etc.).

Otherwise, the easiest way to verify your channel is to use the new proximity scan feature on the ground station:
press and hold the main button to start the scan, and after a few seconds, you'll have every Flutus or Reperix that have been detected displayed on the screen with their respective channels, and of course their unique ID.

View attachment 667641
Ulyu, this brings up a good question. I looked through your documentation but could not find it. How many radio channels are avaialble to select from? And is there a list of the frequencies these channels are assigned to? At large events here in the U.S. we are starting to see the 900mhz band getting full quickly with so many devices crowding those spaces.
 
Ulyu, this brings up a good question. I looked through your documentation but could not find it. How many radio channels are avaialble to select from? And is there a list of the frequencies these channels are assigned to? At large events here in the U.S. we are starting to see the 900mhz band getting full quickly with so many devices crowding those spaces.

Hey, sorry for this late reply.

Page 28 of the documentation details channel allocation and will be updated soon with latest changes.

In short, it's divided into 26 independent channels ranging from 911.75 to 918Mhz.
I've post a frequency table here: https://www.rocketryforum.com/threads/ldrs-42-gps-frequency-tracker-spreadsheet.186090/post-2585265

So yes, if there's a lot of radio equipment in this frequency band, especially LoRa ones, this could reduce the range or cause some telemetry packets to be lost.
 
Blackbox data from my balls32 Wildman Mach 3 launch. CTI M1545 Green used for launch
 

Attachments

  • flightData.csv
    1.9 MB
Blackbox data from my balls32 Wildman Mach 3 launch. CTI M1545 Green used for launch
I find the differences between the dead reconning and baro altitudes and velocities to be interesting. Makes me wonder which one to trust during which phases of the flight. Wish it included GPS speed and altitude for comparison.

@Ulyu Also, side question. Any updates on the IOS app for the system?
 
I find the differences between the dead reconning and baro altitudes and velocities to be interesting. Makes me wonder which one to trust during which phases of the flight. Wish it included GPS speed and altitude for comparison.

Barometric altitude is good up to about 60k feet, after which it starts to deviates.
Dead reckoning altitude is generally quite reliable during mid long flights, and usually deviates from barometric altitude by no more than 5%. On this flight it's off by about 9%.
GPS altitude is not yet used in the current version due to a certain amount of problems with it, but will probably be in the future.

As for speed, during ascent you have to look at the accurate deadreckoning vertical speed estimate. Once at apogee and during descent, you have to rely on the barometric speed (which is under improvements).

Attached is the original blackbox file from Bobrogg's flight, you can open it using the Fluctus Control Center version 1.4 which can be downloaded here:
https://silicdyne.net/archives/

1728787027738.png

@Ulyu Also, side question. Any updates on the IOS app for the system?

It's still in beta but you can download it here:
https://testflight.apple.com/join/VkuPv18N
 
Last edited:
Back
Top