CFW for KSGER/Quicko STM32 Soldering Stations

[Cuboy]

I can confirm the temperature display mode bug. Fixed.
Couldn't reproduce other issues. Maybe some builds were not updated correctly as tatel's comment suggests.
New builds available, try them.
It's sleep time for me, more tomorrow!

Cuboy, that mcu will work fine with the current ksger v2 build.

Does anyone have original backups of ksger v1.5/v2/v3 or quicko F072?

Any problems i will report back.

Anyway today i was searching throught the code and saw that you reverted the pid algorithm to an old one, why is that? Doesn't the "new" algorithm work properly?

I'm willing to spend time debugging and working on it.

Hi. I have tested backups and flashing KSGER v2.1S and the one from HANDSKIT. The HANDSKIT does not asks for codes after flashing back to original but KSGER does.
Here is the keygen for codes that i have tested with 2.1S
http://t12.omegahg.com/keygen.htm

The files I have used are:
- T12_HW21S_Encryption-SH1106 _SW211.hex (version HW-2.1S; SW-2.11; SH1106)
- T12_HW21S_Encryption-SH1106_SW212.hex (version HW-2.1S; SW-2.12; SH1106)
- T12_v.2.1S_OLED1.3_enc_mod_SW211.hex   (version HW-2.1S; SW-2.11; SH1106; encoder moves in opposite direction)
- T12_HW21S_Encryption-SSD1306_SW211.hex (version HW-2.1S; SW-2.11; SSD1306)

Oled Info:
SSD1306 - 0.96 inch
SH1106 - 1.3 inch

I have also attached short info how to flash the firmware.
Since google drive for firmwares is dead, I have uploaded also original copy of all the files there. From the name you should be able to identify the version.

I'm trying to reset my ksger to the old firmware, i have found those firmwares dont work for my station, i have HW: 2.0 SW: 2.09 do you know where i can find the firmware?

[illiac4]

https://drive.google.com/drive/folders/114IoglODyu8bP7dqmw3WWMFV5O7RB9o4

[Cuboy]

https://drive.google.com/drive/folders/114IoglODyu8bP7dqmw3WWMFV5O7RB9o4

I have downloaded the one for the 1.3 oled and it doesn't work, it makes a strange beep upon start and thats it.

Maybe i have fucked something up 

[Cuboy]

https://drive.google.com/drive/folders/114IoglODyu8bP7dqmw3WWMFV5O7RB9o4

Thank you for the firmwares, i have flashed it successfully to my old version.
I have a screen asking me for codes, i have id1:9E14 and id2: 685E

Ok found the keys, successfully reseted it to the original firmware.

[DavidAlfa]

Well, removed all the advanced filtering thing as it seemd to only cause trouble.
Now the only options are filter % and reset limit.
Reset limit is to override the filter if the difference is too big. And that's all.
This way it will cause a little overshoot when reaching the setpoint (actually not doing real overshoot at all) but will be a lot more stable.
Try the new builds and report.

[Cuboy]

Well, removed all the advanced filtering thing as it seemd to only cause trouble.
Now the only options are filter % and reset limit.
Reset limit is to override the filter if the difference is too big. And that's all.
This way it will cause a little overshoot when reaching the setpoint (actually not doing real overshoot at all) but will be a lot more stable.
Try the new builds and report.

David, i tried to install the firmware without any success, as noted i have HW: 2.0 SW: 2.09 1,3 oled KSGER

[DavidAlfa]

Weren't you already using this firmware?
Maybe your stm32 is actually 64KB only?

Post pictures of the errors and your board.

[Cuboy]

Weren't you already using this firmware?
Maybe your stm32 is actually 64KB only?

Post pictures of the errors and your board.

Forget the upgrade messages, those were stlink related. I have no board errors, its just that when i install the firmware the screen is dead.

My stm32 is 128KB, i have the black board -- im not sure about this, i need to confirm

STM32CubeProgrammer says i have the 128kb version (can this be trusted?) searching for the datasheet there are 2 versions available (64kb and 128kb)





the stm32 model is stm32101 rbt6 (Excuse the confusion, i thought by the review i had the one i said, but its this one)

And no, i wasn't using the firmware.

Will try to flash again

[DavidAlfa]

You should flash ksger v3 fw. Ksger versions are confusing, because the mix hw/sw v2/v3 versions.
If you read the readme... It clearly states to not flash based on the version reported by the original firmware, instead, compare your actual board with the pictures.

First of all, make a complete flash erase to ensure it lets you to do so.

[Cuboy]

You should flash ksger v3 fw. Ksger versions are confusing, because the mix hw/sw v2/v3 versions.
If you read the readme... It clearly states to not flash based on the version reported by the original firmware, instead, compare your actual board with the pictures.

First of all, make a complete flash erase to ensure it lets you to do so.

Will try this now, thanks

[Cuboy]

You should flash ksger v3 fw. Ksger versions are confusing, because the mix hw/sw v2/v3 versions.
If you read the readme... It clearly states to not flash based on the version reported by the original firmware, instead, compare your actual board with the pictures.

First of all, make a complete flash erase to ensure it lets you to do so.

Will try this now, thanks

Flashed, now its working as it should. How dumb am i:palm:

Now putting it at 450 celsius i get 250 celsius

[DavidAlfa]

"calibration". You keep ignoring the readme. Read it!

[Cuboy]

"calibration". You keep ignoring the readme. Read it!

Before i sent the post i calibrated, getting a calibration error. Im trying new tips.

I have read the readme and operation, as someone once said, read first, then post.

[DavidAlfa]

Then you should have seen something like "do not calibrate new tips until they become stable" 

[Cuboy]

Then you should have seen something like "do not calibrate new tips until they become stable" 

I had read that, yep.

Thank you, will let the tips bake for a little, then try to calibrate them.

[Cuboy]

I have flashed the last commit (10-08-2021) and it's working flawlessly. Tested 2 tips, t12-ku and bc3, calibration works great and no crazy spikes.

Thanks for all the help, I thought I broke the soldering station but i was flashing the wrong firmware.

Will keep testing tips and creating profiles, but for now its working great.

[ygi]

I know I'm nitpicking on cosmetic details but the time unit "mS" should be all lowercase "ms" (uppercase "S" is a unit of conductance).

https://github.com/deividAlfa/stm32_soldering_iron_controller/blob/master/Drivers/graphics/gui/screens/iron_screen.c
lines 411, 425 and 465

Feel free to keep it however you want after the // 

[DavidAlfa]

There's a 4th "mS" 

[tatel]

Loaded 2021-08-10. Now there are clearly less spikes at 450º; just some at first seconds after setting the temperature, then it gets stable with default PID values. So it's better now than yesterday.

But I still feel this behaves like a horse after feeding on psylocybes. I agree with other posts: FW about 07-31, 08-02 was "better". IIRC, then "PID tau" was missing, before coming back? What I remember is it was quite easy to get almost flat graphics, about 1-2ºC max oscillations, and nice ramps when lowering temps.

Please see attached picture. Left-most ellipse marks a peak on a from-350-to 300º descent ramp. Power bar didn't showed any activity, so temp should be getting lower without any disturbances, as before. Yet it's usual to see those peaks since some days ago. Remaining ellipses mark two instantaneous temperature changes, about 3º. I'm not -at all- sure about these. Perhaps it's a spike from NTC or so. But I don't think tip temperature can drop instantaneously. And I'm sure this behaviour wasn't present about a week -or two- ago.

So, while this FW is getting better and better, I think there is some regression in this aspect. Maybe there is some overreaction?

[DavidAlfa]

Those spikes are less than 5°C.
That's simply and plainly how the TC sensor reads.
Yes they can do very weird things.
There's nothing else now than plain average and %.
No "overreaction", "ntc spikes", "black magic".
Reduce KD if so, or increase filtering.

[tatel]

BTW, could somebody explain how do I restore an image saved with openocd's "dump_image filename.bin 0x08000000 0x20000"

I'm trying with "load_image", "program" and "flash write_image" but I'm just getting errors. Second time this happens to me... so calibrations losed (again)?

David, I don't know about black magic, but my NTC didn't read like that a week ago

[DavidAlfa]

What's wrong with the NTC? 32.9°C?
I won't spend any more time guessing values for 2°C oscillation that leads to nothing.
I willl try for the last time the old pid algorithm, but I'm leaving the project soon.

[mastershake]

are you considering it finished? or is anyone taking it over from you? i have not been able to test the last few builds so im just wondering.

either way thank you for the work and time spent on this!

[Cuboy]

Thank you for your work David and everyone who contributed into this, i know it isn't easy.

[tatel]

What's wrong with the NTC? 32.9°C?
I won't spend any more time guessing values for 2°C oscillation that leads to nothing.
I willl try for the last time the old pid algorithm, but I'm leaving the project soon.

Sorry if that made you feel frustrated. This is just feedback. As I see it, this new, more agressive PID, makes the system less stable, without giving any advantage that I could see, bugfixes aside. Old PID worked OK for me. Tips got hot more than fast enough. Small initial overshoot. Rapid stabilization. Passed the wet sponge test with flying colors. Easy fine tuning. I couldn't ask for more than that.

So, can last version be used without any problems? Yes, sure as hell it's good enough. But last week updates just gave between 3x and 8x the oscillation to me, without any visible advantage in any other aspect. Again, bugfixes aside. Again, sorry the bad news. Probably others could see it other way, and it will be helpful to hear about their experience.

Should you go back to old PID again, I'll stick to it like Tarzan to Chee... uh, Jane.