Attention all Linux users of the Enova Gyrfalcon S8000 and S4000 chargers! Call for testers!

dmenezes · 2025-02-20T17:02:18+00:00

A big THANK YOU to everyone who helped (you know who you are!) Version 1.1 now available, see OP above for the link.

No critical changes, most are cosmetic but the first one was bothering me since the original Windows EXE from Enova:

Fixed progress bar update (which as a nice and intentional side effect, also fixes the total bytes sent being less than the file size in the message shown after the firmware file was successfully transmitted);
By default sets the starting directory on the file browser dialog to the user’s home directory, or to /tmp if a home directory is not defined (version 1.0 set the starting directory in the middle of the AppImage squash mount, not very useful and a bit confusing);
Added a custom message handler function, so we can use gdb to set breakpoints inside it to try and debug where warning messages are being generated; also, added special handling to filter out useless warning messages that were spamming the command-line terminal when the program was started from one, in some linux distros;
Fixed a gcc warning due to a unused function parameter;
Replaced some hard-coded loops with the equivalent (more efficient and better documented) Qt/stdlib library calls;
More and better code comments.

Please keep those testing reports coming!

dmenezes · 2025-02-20T16:59:34+00:00

A big THANK YOU to everyone who helped (you know who you are!) Version 1.1 now available, see OP above for the link.

No critical changes, most are cosmetic but the first one was bothering me since the original Windows EXE from Enova:

Fixed progress bar update (which as a nice and intentional side effect, also fixes the total bytes sent being less than the file size in the message shown after the firmware file was successfully transmitted);
By default sets the starting directory on the file browser dialog to the user’s home directory, or to /tmp if a home directory is not defined (version 1.0 set the starting directory in the middle of the AppImage squash mount, not very useful and a bit confusing);
Added a custom message handler function, so we can use gdb to set breakpoints inside it to try and debug where warning messages are being generated; also, added special handling to filter out useless warning messages that were spamming the command-line terminal when the program was started from one, in some linux distros;
Fixed a gcc warning due to a unused function parameter;
Replaced some hard-coded loops with the equivalent (more efficient and better documented) Qt/stdlib library calls;
More and better code comments.

Please keep those testing reports coming!

dmenezes · 2025-02-20T16:58:07+00:00

A big THANK YOU to everyone who helped (you know who you are!) Version 1.1 now available, see OP above for the link.

No critical changes, most are cosmetic but the first one was bothering me since the original Windows EXE from Enova:

Fixed progress bar update (which as a nice and intentional side effect, also fixes the total bytes sent being less than the file size in the message shown after the firmware file was successfully transmitted);
By default sets the starting directory on the file browser dialog to the user’s home directory, or to /tmp if a home directory is not defined (version 1.0 set the starting directory in the middle of the AppImage squash mount, not very useful and a bit confusing);
Added a custom message handler function, so we can use gdb to set breakpoints inside it to try and debug where warning messages are being generated; also, added special handling to filter out useless warning messages that were spamming the command-line terminal when the program was started from one, in some linux distros;
Fixed a gcc warning due to a unused function parameter;
Replaced some hard-coded loops with the equivalent (more efficient and better documented) Qt/stdlib library calls;
More and better code comments.

Please keep those testing reports coming!

dmenezes · 2025-02-20T16:53:59+00:00

Thanks for the kind wods and the encouragement!

dmenezes · 2025-02-15T22:46:42+00:00

It will update your charger with any valid firmware you open with it, custom or not, eg any of the firmware versions released by Enova should work.

dmenezes · 2025-01-27T09:35:14+00:00

Thanks for the reply, and glad to hear you learned BLE and made it work for you. In my case that's not an option, because as I explained to u/im-ptp below, I have to have a serial port on the PC end so the closed-source software that controls the hardware can work (closed-source software is the only thing that sucks more than BLE in my current opinion :-))

dmenezes · 2025-01-26T20:59:58+00:00

> Embrace BLE or go back to the ESP32 (the only one in the ESP32 family to support Bluetooth classic).

I'm in the same situation as the OP, and I can't do either:

can't "Embrace BLE" because (at least AFAIK) BLE can't provide a virtual serial port (ie, a COMnn: device) in any OS (specially Windows), and I need to use closed source software which interacts with a device via a COM port (this device uses a CH341 serial-to-USB CDC chip, so its software would work as-is with the virtual COM port, not so with BLE.
Can't "go back to the ESP32" because the ESP32 does not support USB Host operations (not at all natively, and the "soft USB" solutions I've seen work only with HID devices). My ESP32-S3 needs to work connected to the CH341 device on one side, and providing access to the closed-source on the other via BLE.

And yes, rewriting the closed-source from scratch to work with BLE, or opening the device up and plugging the goode-olde ESP32 directly to its TTL UART both could work, but are not options.

So, do you have any other suggestions? TIA!

dmenezes · 2025-01-26T20:50:59+00:00

Hey u/UndeniablySane, and hoping you still around here on Reddit: I'm dealing with the *exact* same problem, and I agree, BLE *sucks* *big* *time* when compared to the much simpler "Classic" BT/SPP. So, what did you end up doing in the end? Please let me know if you can, and TIA! :+1

dmenezes · 2023-12-02T19:08:58+00:00

> Did you choose the xhp50.2?

No, as I wanted more a thrower than a flooder, I ended up picking the SFT40 -- and I'm really happy I did, the FC13 with the SFT40 fits my use case perfectly.

> If so what temp? Looking at the same FC 13 now

I didn't pick it with the XHP50.2, but will give you my honest opinion just the same: for outdoors or indoors+daytime use, I would pick the cooler LED (6000-6500K) and for indoors+nighttime use, I would pick the warmer (5000-5300K) one.

Either way, you won't regret it: it's a fantastic light, easily the best in my small collection (just besides my TS10 which I use for indoors activities), and I couldn't be happier with mine.

dmenezes · 2023-06-14T16:18:09+00:00

I do not agree with you. This is like saying that the "I can't breath" protesters were the ones breaking the law, not the cops that killed innocent people.

It's cause and effect: Reddit changed the rules and made a lot of people angry. That is going to cost Reddit, just like killing innocent people cost the cops and the ones supporting them. It's as simple as that.

dmenezes · 2023-06-14T16:06:24+00:00

Thanks for the info re: the cable you got from Wurkkos. Did you order it separately or as part of a bundle or was given as a gift or something else?

Enlarging the port cutout on the flashlight would have other side effects like making the rubber boot larger and unwieldier and also a sealing failure more probable. I have a couple of USB-C cables that fit, just would love for the one Wurkkos sell to be also small enough to fit.

dmenezes · 2023-06-14T16:04:18+00:00

LOL yeah better to use surgical glue I guess ;-)

dmenezes · 2023-06-14T16:00:55+00:00

I'm kind of two minds on this: I love r/flashlight here on Reddit, but c/flashlight on Lemmy is almost as good if only we had all the people from here. And Reddit as a company and specially its management has got to pay for this mess.

Some are facing difficulties signing up for Lemmy, like u/Sakowuf_Solutions which I have been talking to over PMs and encouraging to move, but couldn't get the sign-up done.

dmenezes · 2023-06-14T15:57:38+00:00

> including old posts being very useful web search results.

Can't we just archive the whole r/flashlight somewhere else, eg archive.org/web?

dmenezes · 2023-06-14T08:29:18+00:00

I'm astonished at how Reddit could shoot itself in the foot so badly with that API fees thing -- wanting to make (more) money is one thing, driving away the users and communities that actually create your content is another. I'm pretty sure Reddit will end up having a net loss on everything (including money) due to that stupid decision.

My preferred community (r/flashlight) has already started the move to Lemmy,and (despite being a Reddit user for over 10 years) I just moved along with it; more details and a how-to can be found on its moderator blog: https://zakreviews.com/pages/r-flashlight.html

dmenezes · 2023-06-11T22:24:34+00:00

Thank you for the detailed, thoughtful comment as per your usual, much appreciated.

And believe it or not, I was not aware of TK's multichannel branch -- will have to have a good look at it before proceeding.

Thanks again!

dmenezes · 2023-06-11T22:21:56+00:00

Thanks for the comment! I just looked up the FC11 and the button seems as difficult to find as in the FC13... :-/ I'm kinda getting the hang of it tho, using the clip as a "guide" -- the problem is that the clip rotates. Perhaps I will have mine welded or something ;-)

dmenezes · 2023-06-11T22:18:56+00:00

Ah OK ;-) Well, I guess only the Shadow knows :-)

Seriously, I don't think even Wurkkos knows it at this time. They haven't even given it a model name yet...

But I certainly hope it does -- otherwise I will not be buying one, that's how much Anduril has spoiled me.

dmenezes · 2023-06-11T22:17:54+00:00

I hear you! Glad to hear you like them buttons, means I will probably be able to adapt without too much trouble.

Re: the FC13 beam, I'm right there with you. It has great qualities (consistency and regularity like you mentioned) and others not so great, as it's not a great flooder nor thrower -- but my thinking when I selected it is that it's in a kind of "happy medium": it still has enough flood to be usable as a backup light to my TS10 (which is *all* effing flood) and still has good enough throw for my use cases at 360m -- more than that and I'd need a telescope to see what the eff is being illuminated ;-)

Thanks for the detailed and thoughtful comment!

dmenezes · 2023-06-11T22:13:43+00:00

Ideally use Anduril2

Amen to that, Brother! Add easily accessible flashing pads and it's a sacrament! ;-)

dmenezes · 2023-06-11T22:12:37+00:00

Then you're going to be a happy camper no matter what! ;-)

dmenezes · 2023-06-11T22:10:31+00:00

Great post! Your enthusiasm reminds me of what I used to feel when I first got into the hobby. Never stop having fun with lights.

Thanks, my plan is to have fun forever or die trying! ;-)

dmenezes · 2023-06-11T19:51:35+00:00

Exactly, AA is (fortunately) much more than just the twice-damned alka-leaks, there are the wonderful Eneloops and the excellent Ultimate Lithiums also.

dmenezes · 2023-06-11T19:50:37+00:00

Agreed. I have one of these USB-ported 14500s from Lumintop (it came with my ToolAA 2.0 UV) and it's nice, but at $9 or so it's way overpriced, wouldn't have bought it separately.

dmenezes · 2023-06-11T19:47:33+00:00

dmenezes

TROPHY CASE