CFW for KSGER/Quicko STM32 Soldering Stations

[ricktendo]

Forgive me if this has been asked and answered, I looked in the Operations Instructions and FAQ but did not find the anser

Is there a Boost mode setting/feature, if not is it possible to add this to the feature requests?

[DavidAlfa]

The main thing I wanted in the fw was to keep it minimalistic, away from a lot of adjustable widgets in the main screen and having to navigate beween them, selecting, deselecting... that's a mess.
That's why it's done that way. Every encoder action has its own function.
So,there are no free actions for the encoder in the main screen. All of them (click, long click, rotate, click and rotate) are used.
Anyways, why? When you can simply turn the encoder. It'll be worse to have to go somewhere to select it or doing some long-clicking thing.

Call me old grump, but I always saw the boost as a stupid thing. Depending on the board you'll need different boost temperature and time.
Having to adjust any, will be more annoying than just cranking up the temps.

Otherwise, something will need to go. Like the temperature plot graph.

BTW, how many ºC are represented by each step in the graphic? Just curious...

It draws +-20ºC from the set point reference. So if you set 300ºC, the drawable range is 380-320ºC.
The plot height is 40 pixels , so it's 1px/ºC

[ricktendo]

The main thing I wanted in the fw is to keep it minimalistic, keeping the main screen away from alot adjustable widgets, having to navigate beween them, selecting, deselecting... that's a mess.
That's why it's done that way. Every encoder action has its own function.
So,there are no free actions for the encoder in the main screen. All of them (click, long click, rotate, click and rotate) are used.
Anyways, why? When you can simply turn the encoder. It'll be worse to have to go somewhere to select it or doing some long-clicking thing.

Understood

But for whatever reason it were to be implemented it could be a increase in degree setting (example 50) from the current temperature setting (example 350, boost would increase to 400)
I think double click would be a good boost shortcut and maybe single click to exit (or use the dial in any direction to go back to set temperature and maybe adjust up/down in the direction the dial has turned)

[DavidAlfa]

Hmm you gave me an idea. Maybe selecting the setpoint, and quickly doing a long-press...
The main thing is to not cause trouble with other settings. There are a lot of checks everywhere.

[ricktendo]

Isn't long press already used to get to settings from the main screen?

I think double click from the main screen is a good option, because click right is already taken by tip selection, click left for standby/sleep

[DavidAlfa]

Edit: I made it even easier.
When you adjust the setpoint, there's 1 second timeout before returning back to normal screen.
If you click within that time, boost mode will be enabled.
Instead of a fixed temp, I made the boost mode as an offset which is added to the actual setpoint. Here we start again, people will want one or another.
I think this way is better. If you are soldering a sensitive board, you'll want a lower temperature, and boost relative to that setpoint.
Then you take a 4mm board with thick traces, you aren't going to enable boost time after time, instead, you'll set the temp for the average needs of that board.
If you find something hard to solder, it'll be better to boost the actual temp.
Otherwise youll have to go to settings and change it every time.

Options added to IRON settings.
Click while the setpoint view is enabled to trigger boost mode.
Click at any time in main screen view to exit sleep, standby, and boost modes.
View modes (Numeric or graph) can't be switched unless it's running in normal mode (The first click will exit the mode).

The flash is struggling really hard. Althought I removed and simplified some code, I saw 232 bytes remaning in one of the builds! That's only ~115 instructions!
Since the reserved flash for the settings can't be less than 2KB (Page size), and less than half of it was used, I increased the tip capacity to 20.

Does anyone know how to create Makefiles, so I can run an automated build for all targets?
The biggest issue is to run cubemx code generation automatically.

Building by hand is a tiresome job!

BTW, I was planning to literally lie dead in the sofa and relax for a while.  You had to mention the boost thing, didn't you?


Try this pid: 60-60-10, Imax 0.50, filter 2.


Builds updated!

[StephenR0]

BTW, I was planning to literally lie dead in the sofa and relax for a while.  You had to mention the boost thing, didn't you?

I know that I speak for everyone when I say, please take care of yourself.  We love the work that you do, but you have to keep yourself in a condition to do it.  Please, be selfish about this! 

[illiac4]

Today I have first time flashed the iron. Have used Ksger 2.x bin file. At quick look I have find one thing that is not working.
- It does not lower the temperature when it goes into the STBY mode.

Also some things that I liked in original firmware:
- When in SLEEP mode it would be nice to still see/display the temperature beside HOT!.
- I kinda liked the quick rotation of the encoder left to manually put it into the stby/sleep mode.
- Quick rotate it right to put it into boost mode.
- Press and rotate to select the tip.
- Also I liked the way the shake/button press was handled. When in STBY mode the shake can waken the iron but when in SLEEP mode the shake will not waken it but only button press. This way it will avoid accidently waken it when working on the bench and tilt it and burn something.
- For screensaver I am not sure but any info should not be static on oled display to prevent burn in. I know it will sound funny but original one has a moving Sleeping and displaying temperature at the same time.
The board I have flashed it was with original firmware HW: 2.1S; SW: 2.11

TNX

[DavidAlfa]

It seems you need some reading! Most of those features already exist.
You're right about the standby temps, a new bug that appeared after adding boost.
Fixed, I'll wait a bit before making another builds just un case more issues are found.
Screen saver is not needed since it lowers the display brightness to the minimum.

[wickated]

if i need "boost mode" i can just adjust pid so it will overshoot under heaby load

[DavidAlfa]

Please avoid the silly comments.... 

[illiac4]

I have 6 hours old build.

[wickated]

Please avoid the silly comments.... 

genuine jbc stations literally do this.

[DavidAlfa]

Yes, but in a controlled manner, not with a such weird hack  .

I removed the sleep screen.  Now everything is normal, but the screen is dimmed as before.

[wickated]

Yes, but in a controlled manner, not with a such weird hack  .

I removed the sleep screen.

if it work why not. there are tons of hacks everywhere

no dvd ? NOOOOOOO

[DavidAlfa]

New builds. Hopefully all issues are sorted now.
I'm updating the documentation to follow the current fw.

[Strand17]

Hello,

First, many thanks to DavidAlfa, dreamcat4, floobydust and all other contributors to the custom firmware. Truly excellent work! I have a controller with a T12 iron happily running with your firmware  since a few weeks.

I have a few questions about connecting JBC C245 cartridges to a v2.1S original version (green PCB) controller board. The C245 can be connected in two ways. Either 1) like the T12, with the sensor in series with the heater or 2) JBC 245-style with the heater and sensor separate, requiring some small hardware modifications.

- What are the pro's and con's of the two different connection methods?
- If connecting a C245 like a T12, should the T12 or C245 iron profile be used?

Thanks in advance!

[illiac4]

I am trying to flash another KSGER 2.1 and it says that Can not connect to the target. Is it possible that the flash is defekt on this board? I have checked and there is connection with clock and data to the STM32 pins from the flashing port.

[wickated]

JBC 245-style with the heater and sensor separate, requiring some small hardware modifications.

this. even though tc in genuine jbc tips can withstand this power temp accuracy will suffer with oscilations and other awkward reading like with t12

[wickated]

Yes, but in a controlled manner, not with a such weird hack  .

i suggest then much simpler and reliable turboboost implementation. in tip menu u select power % which add temp +offset. so it will automatically boost when heating big things.

[DavidAlfa]

I am trying to flash another KSGER 2.1 and it says that Can not connect to the target. Is it possible that the flash is defekt on this board? I have checked and there is connection with clock and data to the STM32 pins from the flashing port.

Because in stock fw trhe debugging pins are disabled. Connect nRST to the programmer.
Another way is to manually short the reset pin to gnd with the tweezers, click on erase, and release after 1/2 second. Though you'll need some tries.

[illiac4]

TNX. I have inspected under the microscope and there was a cold joint out of factory. Now it works.

[tatel]

There's still something in the "Edit tips" menu. Created new DFLT and BC2 tips. Then got into BC3 to delete it. Result: last created tip (BC2) gets deleted instead.

[DavidAlfa]

Not happening here.
After factory reset, I created "2","3","4","5"... Deleting BC3(1st tip), deleted exactly that one.
Deleting any other tip also worked as it should.

Please describe the exact procedure to reproduce the issue.
Ensure you're using the latest, made few hours ago.
Since I've been doing multiple builds daily, it's a little confusing.

[Cuboy]

Not happening here.
After factory reset, I created "2","3","4","5"... Deleting BC3(1st tip), deleted exactly that one.
Deleting any other tip also worked as it should.

Please describe the exact procedure to reproduce the issue.
Ensure you're using the latest, made few hours ago.
Since I've been doing multiple builds daily, it's a little confusing.

Hello David,

Today I stumbled with the project, I have to say you are doing a great job.

I was wondering what is happening with the PID algorithm, are you having problems with it? I see that you pushed an old version, what's happening with the new version?

Thank you.