ptdreamer / stm32_soldering_iron_controller

Custom firmware for the chinese ksger soldering iron controller

stm32_soldering_iron_controller

Custom firmware for the chinese ksger soldering iron controller

Check http://www.ptdreamer.com/chinese-stm32-oled-soldering-controller-reverse-engineer-custom-firmware/ for more information

stm32_soldering_iron_controller's Issues

low value of calADC_At_200 causes power output to be stuck at 100%

(I have yet to upgrade to 1.1.2, but taking a quick look at the commits, nothing seems to have been changed since 1.0)

I recently got a new 1403 t12 tip and calibrated this tip with the tip thermometer resulting in the calibration values 175, 1075 and 2147. This resulted in accurate temperature measurements, but also caused the output power to be stuck at 100%, quickly heating my iron to above 500C (which it displays correctly).
I managed to find the debug menu and found out that a higher value for calADC_At_200 alleviated the issue.

(When I had increased calADC_At_200 a bit the soldering iron operated normally unless the temperature was set to a value lower than 140C. I did not investigate much longer as my tip already has a purplish to blueish color from the brief exposure to the high power output.)

Port to other STM32- CPUs (as used in the various T12 controller modules)

First of all: THANKS for your reengineering project and thanks for publishing your readings. I am sure all of us do appreciate that!

Of cause you do not have any personal advantage therein, but in order to increase the community of people using your code it would be of big advantage, if you would add the other CPU types been used so far (for those STM32 soldering controllers) to your code thus making it flexible enough to select which cpu to use for the destination controller.

Mine (dual controller for soldering iron and air gun) came with a STM32F101CBT
The newest (2018 New STM32 OLED T12 Digital Electric Soldering Irons Solder Station Controller Alloy DIY Kits V2.1S ) model comes with a STM32F102C8

Show supply voltage for battery operation

It would be nice for battery operation if the supply voltage could optionally be shown on the display.
Ideally there would also be an adjustable low voltage warning or shutdown via the menu.

Reset Calibration to Default menu option

I managed to to trap myself with false calibration settings that caused the iron to heat above 650°C for the 400°C step. It would be nice if there was a way in the software to reset cal without erasing the chip completely.

Hardware issue - JBC stand contact

Hi Jose,

I have encountered another issue that makes absolutely no sense to me.
When trying the sleep stand contact there was a mighty flash (well, a tiny spark) and the transil diode D3 was gone along with the trace connecting it. The 2k2 did protect the STM so that's something.

Further investigation showed that the outer sleeve is pulsed to +24V as the power is on.

I triple checked, and triple checked again the connections per your diagram and they are correct.
If I reverse the middle and inner contact the outer sleeve will remain at ground potential, but the polarity of the thermocouple voltage is then reversed and I get no valid temperature reading.
(The center pin makes a positive voltage against the middle contact when the tip is heated).

I have seen a ground-open picture of the JBC tips, and the center rod is welded to the outer sleeve directly. The middle contact goes to the end of the heater coil. Therefore I am not surprised my outer sleeve gets pulsed to +24 if the center rod is connected to the Mosfet, but I see no way how this could work? Either the thermocouple voltage has the wrong polarity, or I get +24V at the outside as the Mosfet is on.

Please advise if there is anything I am missing here.
You wrote in your blog that you connect the outer sleeve to GND via a switch, but I just don't see how this is possible without shorting out the heater?
Please check on your tips if there is a connection between the center pin and outer sleeve.

Thank you.

ST

Schematics R14, R15

Hi, I have been redirected from your blog site https://www.ptdreamer.com/ where you posted a schematics. Well the resistor R15 is misplaced. With R14 they should form a voltage divider, so that gate voltage doesn't goes above Vgs max. In your scenario this is 24V and slow turn off time (R14+R15). In my opinion the R15 goes in series with T1's collector.

A small ask - can enable 'git lfs' feature? Thank you

Hi PTDreamer!

For this project (STM32 Controller)... I wish to store git LFS object reference in my fork. For archiving supporting materials. To keep them safe and available when people do git clone. The reason is to avoid needing to store assets with a larger file size right next to the source code itself. Instead just only a reference is saved. So that adding further assets does not blow up the size of the git repo. Which is not desirable for others checking out / downloading. etc.

For example:

One of the resources I wish to backup (using the git LFS feature) are your blog posts all about this STM32 project. Just in case your personal wordpress blog breaks / fails one day. This then makes sure the project continues. And without missing docs which is referenced etc.

My problem:

Github does not let me enable the git lfs feature on my fork. Unless the original repo (yours) is first enable with git LFS feature:

git-lfs/git-lfs#1449 (comment)

If you can enable this feature. Then it would be a great help, & thank you. Because [otherwise] I do not actually wish to unlink my repo from yours. It's nice to keep them connected on github. So that people can see in the network graph, check the activity across the forks. And find the other active branches, do merges / etc.

Sorry to have to ask you to step in here, it is silly, and should not be required. However if you can enable LFS in your repo. I believe this is the known workaround:

git-lfs/git-lfs#1449 (comment)

So pushing a dummy file, added as an LFS object reference. Then I can fork the repo again but this time with LFS object inside it.... Then you can remove that dummy Git LFS reference in a subsequent commit.

That would save me a whole heap of problem. Because it's better (for sharing the code) to keep my repo status as a fork of your original repo. It is better for the open source visibility. Thanks for considering this.