Add support for SEQURE S99, and new Rev. of S60P#1920
Conversation
Co-authored-by: discip <53649486+discip@users.noreply.github.com>
Co-authored-by: discip <53649486+discip@users.noreply.github.com>
|
Hia, This is great progress. The black screen at startup is odd. PD negotiation shouldn't block boot. Is it possible its being restarted rapidly with flaky USB-PD? (Do you have any tools for debugging USB-PD)? I haven't really worked on the |
|
Hey, yeah. It seems to restart rapidly. It seems to be especially with the Apple Chargers. Another charger I tried let the iron boot straight up. Sadly I don't have special USB-PD tools. Maybe I need to get something or build something to hook a logic analyzer on? As I could see with the debug menu, when it comes up it gets all available PD modes, but stays in 5V mode. I think I need to take a look at the measurement of the tip for the power calculation? Maybe you can give me a hint on that? |
|
@Ralim I'm currently digging a bit through the code and debug outputs of the iron. I wondered why it reports Regarding the PD negotation problem with my Apple 60W USB-C PSUs I tried to increase the PROTOCOL_TIMEOUT to 200 ms, which helped. The Iron boots instantly. PD Debug First Shows I hope I can make some progress tomorrow. |
Ah heck, yes that will fix the issue
|
@Ralim It's a bit unclear to me. In the Settings.cpp
How did you determined the value for the OP_AMP_GAIN_STAGE? |
Ah sorry, I think we raised the default later on.
In the S60, its two sequential op-amps chained. Input op-amp has feedback resistors of 9.31K and 1K. (therefore gain is 10.31) So 10.31 * 50 = 536.12; so the define is set to 536 |
* Enable PD Options * Make PDNegTimeout configureable * Add default value for PDNegTimeout, also for S60 and S60P * Add basic DC detection / correct debug readings while powered via DC * Add basic ThermoModel for C245 Tips * Modify op-amp gain
| bool getIsPoweredByDCIN() { return false; } | ||
| bool getIsPoweredByDCIN() { | ||
| #if POW_PD_EXT == 2 && defined(POW_DC) | ||
| if (!FS2711::has_run_selection()) { |
Ralim
left a comment
Ralim
left a comment
There was a problem hiding this comment.
This seems sane to me at a read.
|
Let me know when you are happy with this by marking it ready for review 🙇🏼 |
Nice! |
|
I compared the temperature at a setpoint of 320°C to a original JBC station. In my eyes the coefficient is okay for a first shot. Then I observed that the name and description for PDNegTimeout and USBPDMode are not shown in the menu. I quite don't get it. The menu Item is here I got a second S99 which is V1.5 instead of V1.4, it seems that they changed something. Although a FS2711 is used, it does not negotiate PD. I quickly took two picutes: |
|
@Ralim, I tried your increased pwm speed. Works great on the S99! No more restarts, even with power limit set to 60W on a 60W USB-C charger. What I got so far regarding v1.5
|
|
I do have issues with PD bootlooping the iron on specific chargers (mainly QC compatible, I can post a PD detection image later),PD state keep bouncing between 0 and 1 really quickly, that do not happen with the original firmware. On the Steam Deck charger however it does seems to behave correctly. |
|
What's the hard requirement for having to split hardware revisions? |
|
Can we somehow have a new build in GH Actions so we can try the latest? |
I'll update it later. |
|
@jonasius sadly no new build. Is this because of requested changes? |
|
Sorry, had little time lately. I have to figure out why the build breaks. I'm working on it. |
|
It seems that the build for S60P in JA_JP is failing due to size issues: If I'm looking at the bootldr_size in the Makefile, the S60P has the biggest. |
|
Any news on a new build? :) |
|
Hello. I tried this on my S99. It worked on usb-c but when i used a 20V 10A power source to test it at the maximum possible power and the MOSFET switching the tip failed short causing the tip to glow red hot. So it might be a good idea to limit the maximum power even in DC. |
|
Hey, any news regarding this? I wanna install it on my S99 :) |
|
Added a few commits on a fork to
Tested only on my available hardware (s99 stock tips), build bin are available in the ci artifacts for those that want to try it |
|
Hi! How usable is this? I ordered the Sequre S99 yesterday, and the tip set is 2.5 ohms |
|
In general the S99 is useable. But with original jbc tips and the high switching frequency, the MOSFET inside gets so hot that you can feel it on the outside of the case. Image recorded with removed cover: |
|
Thanks for the reply! I decided to cancel the order and get the Alientek T90 instead. The difference is only $6 ($24 vs $30). Good luck with firmware development! |
|
Doe's this firmware support power limitation (For example, cutoff at 65W)? |
|
I received my S99 today, can I use this firmware for everyday use? |
I would be interested in learning this too. Could one of you devs please post a summary of the current shortcomings (bugs or unimplemented features) to make it easier for us users to decide? |
So, I decided to give it a try myself, assembled it, and flashed it myself. It seems there are some minor display and interface issues, at least on the main screen. I have two cartridges, the included 5 Ohm one and an additional 2.5 Ohm one. It heats up fine with the included 5 Ohm one, but when using the 2.5 Ohm one, things get worse. It starts to heat up and then goes into protection mode after a few seconds. Power limiting doesn't help. I tested it with a good 65W power supply. I connected a USB tester to it, and I didn't notice any peak current at shutdown, no more than 1.4A 20.1V. Another interesting issue with the stock firmware: from what I've read in reviews, it should also have tripped protection when using a 2.5 ohm cartridge. I didn't notice any such issues. However, I encountered another issue: after turning it on with the factory firmware and setting the target temperature to 300 degrees, the display readings would fluctuate between 340-380 degrees, but as soon as I inserted a 2.5 ohm cartridge, the 300 degrees remained steady. 
|
If I remember correctly that 20 is the input voltage, so 20V. But most of the time I used the detailed screen (can be changed in the options), so maybe indeed there is a issue. As far as I remember power limiting worked for me. But maybe it's also depending on the specific power supply used. I observed that some cables also can cause shutdowns. My main interest was to use the S99 with original JBC tips / 2.x Ohm tips. So I think I never again tested it with the 5 Ohm tip. |
|
Yeah, I probably shouldn't use this screen on my TS100 either (its case started cracking, so I decided to replace it with an S99). I have a detailed screen set. I just happened to set it to around 200 while testing. I used the original Apple iPhone Type-C cable. I only have one power adapter with PD, so I can't test it with another one, but I haven't had any issues with it. I use the TS100 with it via a trigger or a miniature bottom heater, a simplified version of MiniWare. I'd be happy with most of the 2.5 ohm soldering tips offered on AliExpress, but as you can see, my soldering iron keeps turning off. Is there a way to lower the PWM frequency to reduce the MOSFET's heat? Unlike its C245 counterparts, I liked the S99's size and the way it fits in my hand, like a pen. The stock firmware, while functional, is somewhat confusing to configure, starting with something as basic as setting the operating temperature. After seven years of owning a TS100, I've become very accustomed to IronOS. |
Just got my s60p this thing is so cute and tiny compared to my hakko fx888d, and after trying multiple fw sources, @blamas's actually made the iron usable thx, but why does S60P not have tip type selection enabled
another thing I wanna point out is the constant overshooting of PD adapters' OCP, like when setting something like 50W, the iron doesn’t cap it properly and shoots up to like 70W. That’s fine when using a 100W adapter, but would be a problem if someone tries using a 65W adapter. Also, in the code, I see we have a 98W limit when using a 100W adapter, V x I - 2W. is this due to inrush current or maybe i feel like PID overshoot or PWM Duty Cycle or something like that, either way i know our hardware in kinda limited, but maybe we need to implement some sort of soft start or something, tho i did notice it drawing 17W when the power limit was set to 5W, so maybe it was not inrush current idk atp, or could it be that the tip resistance is lower than 2.0ohm hmm that would kinda make sense why it takes more power then the set limit. p.s. sorry if I yapped a lot, haven't slept since i opened this thing |
|
Yesterday I was experimenting with the firmware with my part-time colleague (Claude Code), I made a choice between a 2.5 or 5 tip, with 5 it worked fine, but with 2.5 the soldering iron still restarted, in the end I got a more or less result that it turned off and consumed about 3.5-4A at 20V, the soldering iron itself showed a stable 80W, but during stability tests (I dipped the tip in a mug of water), it suddenly showed 500 degrees and I realized that this was the end of it, after rebooting it stopped seeing the tip, and the tip itself was heating up non-stop, I came to the conclusion that the MOSFET switching the soldering iron tip burned out and it remained in the open state, I ordered a similar MOSFET for replacement on the local marketplace, I will receive it in about a week 
|
@teuchezh |
|
with my own tests on the s99 my only main concern is the mosfet heating up quite a lot due to the faster pwm especially with 2.5ohm tips. lowering power limit doesn't help much (if at all) in reducing the mosfet heat. any chance of having a compiled version of the firmware with the latest changes, but using slow/slower pwm instead? as much as i'd like to do it myself unfortunately it's beyond my skill level. |
It won't be here, since this firmware was compiled from the code of this PR. And I experimented with choosing the tip type locally; I didn't upload this code anywhere. |
20 participants
What is the new behavior (if this is a feature change)?
IronOS booting on Sequre S99
Other information:
Currently work in progress.
Problems / Todo
State 0 0 21multiple times, with blinking/resetting screen, after a while showingState 4 1 21.OP_AMP_GAIN_STAGE 536needs to be adjusted according to the 22k resistor instead of 51ksource/Code/BSP/Sequre_S60folder should be renamed toSequre?