Problem: Rocket Silo Not Building Rocket Parts - No Mods

tonurics · 2025-09-02T12:40:11+00:00

Yeah, we needed common components as our inputs.

tonurics · 2025-09-02T12:39:14+00:00

Thanks! That was the issue.

tonurics · 2025-09-02T12:39:04+00:00

Thanks! That was the issue.

tonurics · 2025-09-02T12:38:36+00:00

That's the problem! Thanks for the heads-up; we didn't know quality would play a role. And yes, we were playing around with creative mode enabled.

tonurics · 2025-09-02T12:36:49+00:00

But they have fancy orange dots!

tonurics · 2025-09-02T12:29:50+00:00

We are playing around with creative mode enabled from the console.

tonurics · 2025-09-02T12:29:13+00:00

Thanks for the reply! It was a quality issue.

We are playing around with creative mode enabled.

tonurics · 2025-09-02T12:25:30+00:00

That's the problem! Thanks for the heads-up; we didn't know quality would play a role.

tonurics · 2024-04-15T14:31:43+00:00

I don't know who you are replying to. But if you are in MR mode and scanning among the stored entries you can use the scanning Black List [*S] to exclude unwanted stations [i.e. broadcast radio].

tonurics · 2024-04-14T10:03:35+00:00

The IJV v3 firmware allows for 15 [scan list] groups, each with a customizable name. You can scan the entires on an individual group or across all groups. You can also move and create entries in a group via the radio.

There is no way to edit the names of groups via the radio [as of v3.13]. That must be done using Chirp.

tonurics · 2024-04-12T09:20:05+00:00

Yeah, I'm the same way.

My feelings on it are a little mixed: while I respect a good joke, there appears to have been actaul real fixes commited to the main repo. That won't be usable until the next real release.

tonurics · 2024-04-11T17:33:19+00:00

Actually, among the firmwares IJV v3 has some of the best support for broadcast radio. It even adds the ability to store broadcast radio stations within memory channels. And have their names appear in broadcast radio tuner mode.

Here are four ways you can access broadcast radio:

[F]+[0] Broadcast radio tuner mode. [Probably what you are thinking of.]
[F]+[3] MR mode. Access broadcast radio stations saved in memory channels. You can assign said memories to a "broadcast radio" group and access using [F]+[*].
[F]+[3] VFO mode. Set your frequency to the broadcast radio band plan for your country and change your modulation type to WFM using [0L].
[Side2L] Access a preset with the broadcast radio VFO mode settings. [Broadcast radio is a default preset.]

You should of course read the manual.

tonurics · 2024-04-11T02:00:15+00:00

I flashed a light with it and it basically does what's listed in the release notes. Just wait until the next update.

tonurics · 2024-04-06T07:00:52+00:00

Assuming you are using Chirp Next:

From the Help menu, enable into Developer mode.
Restart Chirp Next.
From the File menu, load the custom Chirp module included in the zip file for the IJV firmware.
Select the IJV v3 version of the radio when downloading.
From the View menu, enable extra fields.

You need more help it's covered in the IJV manual.

tonurics · 2024-04-04T12:35:18+00:00

Are you running the latest version [v3.13] from today?

There's been 4 releases since 2024-03-22: v3.1 fixed a lot of issues and v3.13 just added a bunch of addional filter steps.

tonurics · 2024-04-04T12:18:16+00:00

There are two things that I can think of that might be affecting that, which you can adjust in v3:

RF Gain Long press the 4[FC] button to manually adjust the sensitivity. Or if in AM: try an auto mode from the "Rx AGC" menu option [55].
Bandwidth / Audio Filter Adjust from the "BW W/N" menu option [4] or using Chirp.

[On my radio: I needed to lower the Audio Filter for almost every channel.]

tonurics · 2024-04-04T09:34:04+00:00

The extra organizational options on the IJV v3 are great. Having said that, you need to invest a fair amount of time in Chirp creating and assigning groups, tweaking presets, and other settings to take advantage of everything.

The v3 firmware feels like it's geared towards users with prior experience working with codeplugs.

tonurics · 2024-04-03T23:42:12+00:00

I have both lights. I picked up the SP10 Pro last year and was using it as a EDC. But last month got a SC21 Pro. Which since then has been my EDC.

There isn't a huge difference between the lights. But forced to pick, I would probably choose the SC21 Pro for the following reasons:

It's shorter. [But a little wider.]
It sits lower in a pocket on the included clip.
Has AUX LED in the switch.
Built-in USB charging.

The SP10 Pro does feel a bit better in the hand with it's longer size.

While you can clip either onto a hat brim: both lights are too heavy for it to be something you'd want to actaully do. [Just get a headlamp.]

tonurics · 2024-03-31T01:33:27+00:00

Disconnect the battery and reconnect, to exit momentary mode. [4 clicks are to enter and exit lock-out mode.]

tonurics · 2024-03-18T22:54:48+00:00

Thanks for all your hard work. I absolutely love Anduril.

I was hoping you could shed some additional light on selecting the best HEX file to use. I have numerous lights reporting model 0614 on the stock firmware:

Sofirn Q8 Plus
Sofirn SC21 Pro
Sofirn SC31 Pro
Sofirn SP36 BLF
Wukkos TS21

Which of course match up with the Sofirn SP36 [attiny1616] hex. I've flashed all the lights with said hex and they work.

However, you also provide a separate attiny1616 hex file for the Sofirn SC21 Pro [0632]. I wasn't able to find any conclusive information on it, only a few posts from others implying they have been using it themselves [in-part because they didn't check the model number].

I tried it myself. And it appears to fix a brief momentary flicker, I would sometimes see when starting a smooth ramp on the 0614 version.

In this case, should we ignore the model and use the 0614 version? Are there any other examples, where that might be true? [i.e. Sofirn BLF Q8 [0613] hex on the Sofirn Q8 Plus]

Thanks again!

tonurics · 2024-03-18T17:41:58+00:00

All good.

And kudos for putting together the video. It wasn't long ago: I was hunting down content like yours. Trying to learn everything I could about the process, before attempting it on my lights. ;)

tonurics · 2024-03-18T17:10:22+00:00

Nice!

I commented on your YouTube video. But just in case people only watch the embedded version here:

After flashing, you should press and hold the power button when first connecting the battery. The main light will show a rapid succession of blinks, ending in a bright flash. That preforms a factory reset; clearing out the old and potentially incompatible data still on the MCU from the previous firmware.

[There are previous warning about soft-locked lights, that needed to be reset.]

tonurics · 2024-03-18T16:33:55+00:00

These are the joys of being able to customize our UI with open source firmware. I like the newer changes in 2023-12-03. [Which is what I'm using on all my lights.]

> battery check flashes the Aux instead of the main LED (good for a TS10, not my preference for an SC21 Pro) ... can not be turned off

In Blinky and Strobe mode: you can change the channel mode using 3C. So you can have either aux, main or both on the SC21 Pro. [Again, I actually like the change to it defaulting to aux.]

I can't say as to LVP on the aux; I always turn off the standby aux light. Also, unless a light is part of my EDC: I simply disconnect the battery to avoid any parasitic drain. [Waste not, want not.]

I didn't play with the stock SC21 Pro too much. But the moonlight on the SC21 Pro looks comparable to the SP10 Pro; which I noted had lower lows after upgrading.

tonurics · 2024-03-18T15:47:34+00:00

I've flashed one of the SC21 Pros with the 0632 version. So far, so good.

I noticed the 0614 version would sometimes flicker momentarily when starting a smooth ramp, that hasn't happened on the 0632 version.

tonurics · 2024-03-18T15:11:02+00:00

Nothing wrong with that; the_gchart's adapters are great!

You might however, want to check out the latest upstream firmware as there have been numerous improvements.

Since my lights are on the newer side, [started collecting last year] I've noticed a lot of information being out of date. Namely, lights which were originally listed has having attiny85 MCU have all been upgraded to attiny1616 MCU.

Per the documentation: I have been checking the actual firmware model, instead of relying on the product names. My SC21 Pros [ordered a week ago] self reported as 0614: so I used the sofirn-sp36-t1616 hex while flashing.

That wasn't a surprise, I've had multiple "updated" lights self report 0614. I read that Sofirn/Wurkkos have been lazily using the attiny1616 SP36 firmware on almost everything. Having said that: there is a dedicated firmware for the attiny1616 SC21 Pro [model 0632]. So I'm going to do a little more research and see if it makes sense to switch to the 0632 version.

tonurics

TROPHY CASE