ISL94202 & MSP430 based BMS
Library for the BQ34Z100(-G1) IC from Texas Instruments for the Arduino platform.
Ralim/LA104 10
LA104 Logic Analyser from Miniware (E-Design) Updated Firmware Fork
Open Source MPPT for Lithium Batteries. Based on TI controller
Awesome CV is LaTeX template for your outstanding job application
A raspberry Pi zero powered mp3 player project
Ralim/Battery-Capacity-Tester 1
A User Interface for Battery Testing using a Re:Load Pro
DFU Bootloader for STM32 chips
FreeLSS is a laser scanning program for the Raspberry Pi. It allows a Raspberry Pi to function as the core to a complete turn table laser scanning system.
push eventRalim/ts100
commit sha 4496cfd41dec5de31c3c47183d56112bb5e84f0d
More hooks for hall effect
push time in 7 hours
push eventRalim/ts100
commit sha 64abe4d5dd6512bf56b3d5876a74647e3a338acd
Updated dutch translations
commit sha 0ffef8fd2d1768ed02f966176f5f47472946d8db
Merge pull request #709 from Pieterv24/master Updated dutch translations
push time in 3 days
PR merged Ralim/ts100
Please try and fill out this template where possible, not all fields are required and can be removed.
- Please check if the PR fulfills these requirements
- [x] The changes have been tested locally
- [x] There are no breaking changes
-
What kind of change does this PR introduce? I've updated some of the dutch translations. Some were not yet in dutch and others were incorrect/incomplete translations
-
What is the current behavior? (You can also link to an open issue here)
-
What is the new behavior (if this is a feature change)?
-
Other information:
pr closed time in 3 days
push eventRalim/ts100
commit sha f9813ec4943216eaa1a0ace66533542a8a4a8400
Locking Mode
commit sha 8e0c4ea9ad23d0c9a32462434a551c9e7c7c0304
Merge pull request #705 from Mel-kior/LockingMode Locking Mode
push time in 6 days
PR merged Ralim/ts100
This add a locking mode that lock the buttons when soldering to avoid accidental press.
A long press on both buttons toggle it (only on the soldering gui)
In the soldering config menu you can set it to :
- Disable (default)
- Lock except Boost mode
- Lock everything
Tested on TS100 only
pr closed time in 6 days
issue commentRalim/ts100
I haven't updated the converter tool since the python tool has completely replaced it and gone further in terms of features. If you attach your image or email it to me I can convert it you.
comment created time in 6 days
issue commentRalim/ts100
Hello, It is quite possible that you have generated your logo with an old version of the converted which used an incorrect location in the hex file.
If you regenerate your logo file with the python tool you should not run into this issue anymore.
comment created time in 7 days
push eventRalim/ts100
commit sha 77dbc9df56e00242c58ac4d3695c06bf337858c4
Update Makefile
push time in 10 days
pull request commentRalim/ts100
Hall effect sensor that hopefully (not guaranteed) will be placed where the tip goes into the iron to enable detecting metal stands (its hoped this can enable a better sleep mech as well as accelerometer).
comment created time in 13 days
issue commentRalim/ts100
Flash of firmware don't work with the usb device method
@grimpod1 Press both buttons or press and hold the rear button (near dc input)
comment created time in 14 days
issue commentRalim/ts100
Flash of firmware don't work with the usb device method
@grimpod1
They should be fairly easy. If you pause on one they have have help text as well.
I encourage you to just use it and experience how it works :)
comment created time in 14 days
push eventRalim/ts100
commit sha 3e62afc4556777f035de994e73df200fbb708d08
Move to nuclei compiler
push time in 14 days
release Ralim/nuclei-compiler
released time in 14 days
push eventRalim/nuclei-compiler
commit sha 7f27f2205fac285e93b11193c7967add3282408c
Update README.md
push time in 14 days
push eventRalim/ts100
commit sha c8182aa1925c0bcfd049dd2ff94c9db8158f1589
Debugging history.hpp compiling odd
push time in 14 days
push eventRalim/ts100
commit sha 7da04841d64c89dc291a3df372d5aae7b3b7c75a
Update Makefile
push time in 14 days
push eventRalim/ts100
commit sha 40cf09a910c66aae9dbad469d8da28feb8c582ed
Add support for dual speed PWM
push time in 14 days
push eventRalim/ts100
commit sha d380cd4b9e73bc89165906049bb75189928f59e7
Update setup.sh
push time in 14 days
push eventRalim/ts100
commit sha baef9264ff5377de881fbb4ba9f5bbbb45f6c220
Update setup.sh
push time in 14 days
push eventRalim/ts100
commit sha 5386dfdfaff1e0f34280016d2a79a6f317d1366f
Update setup.sh
push time in 14 days
push eventRalim/ts100
commit sha e72c884b62e001f6b9a12219393b9c334beda548
Update pr.yml
push time in 14 days
PR opened Ralim/ts100
This is not quite mergable just yet.
But opening this up for community comments as well as allowing me to keep better tabs on it.
pr created time in 14 days
push eventRalim/ts100
commit sha 2e4168be7324bef6dbf75569f12fc23978bf4300
Bulk format
push time in 14 days
push eventRalim/ts100
commit sha 03afdcdf205fddbba2a5d5702ff52d48e4da2fe4
Update push.yml
push time in 14 days
push eventRalim/ts100
commit sha 5b3bdf1939e60d7b4e5f26b542549f35fa29efb6
Fix BadTipString in Italian translation
commit sha 30be5e0de4eb3c68adcf7f8ee7dd0495f337e9c3
Introduce PWM freq switching so that power could be averaged on shorter intervals With this a TS-I tip is usable with a small netbook 19 V / 30 W PSU with power limit set to 40 W (38.9 W is reported during the heating up stage). Without this the device just reboots on attempt to turn on the heater (unless the power limit is set to 10 or even 5 W). This code doesn't affect maximum power available and allows up to 73 W when a beefy 24 V / 96 W PSU is used. Should be useful for all models, not just TS100. The fixed comments are based on calculations, not measurements! Fixes #693.
commit sha 471cd565b56c9d9dbee6abf6adc7bedd489ce0f2
Updated slovak translation
commit sha b18bea4d5ea3b2dd68eb5e0875c2457274769a92
Added 2 missing characters
commit sha 923989bf16e67e2e17dce3896122dfef43021126
Merge pull request #703 from DusanF/master Slovak translation
commit sha 301f03acd0ad473d37be4f2c845ca0f4fb5ebd30
Merge pull request #697 from paulfertser/poc-limit-power Limit maximum power more efficiently using dual speed PWM
commit sha 7cdf884eeaccf8c8d2269d9241a41b1cb19c1ebb
Merge pull request #700 from augustozanellato/patch-1 Fix BadTipString in Italian translation
commit sha 72e251aa9d77d8ada6e4744a44424aa612c77125
Fix a couple of typos creating bad links in the README file
commit sha 21121732144a438bb49d19d995259d81c73508fd
Merge pull request #706 from booleanvalue/fix-readme-typo Fix a couple of typos creating bad links in the README file
commit sha d2ac2800d05c990ac89e34560a47a2f0fb927f4c
Merge branch 'master' into pinecil
push time in 14 days
push eventRalim/ts100
commit sha 58c4ecaea66fefa269f689351e5da12a39564d2f
Starting hall effect support
push time in 14 days
issue commentRalim/ts100
Flash of firmware don't work with the usb device method
@Ralim I had opened device manager when I connected the device but nothing happens.
I feel that this is either your pc or the cables you are using I'm afraid
comment created time in 15 days
pull request commentRalim/ts100
Fix a couple of typos creating bad links in the README file
Thank you 😍
comment created time in 15 days
push eventRalim/ts100
commit sha 72e251aa9d77d8ada6e4744a44424aa612c77125
Fix a couple of typos creating bad links in the README file
commit sha 21121732144a438bb49d19d995259d81c73508fd
Merge pull request #706 from booleanvalue/fix-readme-typo Fix a couple of typos creating bad links in the README file
push time in 15 days
PR merged Ralim/ts100
Fixes a couple of typos that were creating broken links in the README file
pr closed time in 15 days
issue commentRalim/ts100
Flash of firmware don't work with the usb device method
@grimpod1 Can you open device manager when you connect the device? You should either see it show up as a storage device or show up as an unknown device. If you see neither its most likely your USB cable. As even broken firmware on the iron will still cause it to show up as an unknown device.
comment created time in 15 days
issue commentRalim/ts100
Flash of firmware don't work with the usb device method
@grimpod1 This is most likely your USB controller or software you have installed. Have you tried multiple computers and multiple USB ports?
comment created time in 15 days
issue commentRalim/ts100
@puzrin
I think protothreads would work really well for it; agree FreeRToS is overkill (it is sadly the main one that I know however).
Really it should be quite doable to make it all one task (plus IRQ's) and not require threads at all. Mostly trying to keep to this format to make debugging simpler while I figure out all of the compatibility issues.
@stiliajohny This was reported earlier, currently trying to borrow a charger to debug this. Per chance what model is your Apple charger?
Suspect I will need to just add PPS support for the apple devices, which will take a bit.
comment created time in 16 days
issue commentRalim/ts100
@stiliajohny Its mentioned in a few places, but TL;DR is to copy it again once the .ERR file shows up (aka try it again without unplugging the USB). Sometimes you may need to do a that a few times until the ok file shows up :)
comment created time in 16 days
issue commentRalim/ts100
@puzrin ❤️ I will order one now. For your project are you planning on using FreeRToS? I might try and break it out into an easier to use form
comment created time in 16 days
issue commentRalim/ts100
@stiliajohny Do the double copy trick and it should take.
comment created time in 16 days
issue commentRalim/ts100
@puzrin
I absolutely wouldn't say no to one though don't feel you need to; I'm ok to buy one in the future once donations cover it :) (I try to re-invest them in tooling where I can)
comment created time in 16 days
issue commentRalim/ts100
@stiliajohny
Please use the latest release for the TS80P. Also don't bother cleaning the DFU storage as that can cause odd bugs with the DFU mode, the files are there to stop your PC automatically making them :)
comment created time in 16 days
pull request commentRalim/ts100
A very very long time ago I made a test firmware with 10kHz signalling without sucsess. Have noticed some of the OLED units I have around here have just "degraded" and the panel itself starts to have issues driving properly.
This could be perhaps that those weaker panels need higher drive voltages / currents but that feels risky to try...hmm...
comment created time in 16 days
push eventRalim/ts100
commit sha 5b3bdf1939e60d7b4e5f26b542549f35fa29efb6
Fix BadTipString in Italian translation
commit sha 7cdf884eeaccf8c8d2269d9241a41b1cb19c1ebb
Merge pull request #700 from augustozanellato/patch-1 Fix BadTipString in Italian translation
push time in 16 days
PR merged Ralim/ts100
Please try and fill out this template where possible, not all fields are required and can be removed.
- Please check if the PR fulfills these requirements
- [X] The changes have been tested locally
- [X] There are no breaking changes
- What kind of change does this PR introduce? Small fix in Italian translation
"PUNTA NO" means "no tip", whereas "KO" means not ok
pr closed time in 16 days
pull request commentRalim/ts100
I generally dont think its the speed of the I2C bus itself. The OLED is rated to 400kHz and we are already running it a lot slower than that to provide more tolerance. :/
comment created time in 16 days
Pull request review commentRalim/ts100
static void gui_solderingMode(uint8_t jumpToSleep) { } for (;;) { ButtonState buttons = getButtonState();- switch (buttons) {- case BUTTON_NONE:- // stay- boostModeOn = false;- break;- case BUTTON_BOTH:- // exit- return;- break;- case BUTTON_B_LONG:- return; // exit on back long hold- break;- case BUTTON_F_LONG:- // if boost mode is enabled turn it on- if (systemSettings.BoostTemp)+ if (buttonsLocked && (systemSettings.lockingMode != 0)) { // If buttons locked+ switch (buttons) {+ case BUTTON_NONE:+ // stay+ boostModeOn = false;+ break;+ case BUTTON_BOTH_LONG:+ // Unlock buttons+ buttonsLocked = false;+ OLED::setCursor(0, 0);+ OLED::clearScreen();+ OLED::setFont(0);+ OLED::print(UnlockingKeysString);+ OLED::refresh();+ osDelay(1000);
Could we use the wait for button press or timeout rather than a hard delay?
comment created time in 16 days
pull request commentRalim/ts100
[PoC] limit maximum power more efficiently
Thank you for poking, looks great to me :)
comment created time in 16 days
push eventRalim/ts100
commit sha 30be5e0de4eb3c68adcf7f8ee7dd0495f337e9c3
Introduce PWM freq switching so that power could be averaged on shorter intervals With this a TS-I tip is usable with a small netbook 19 V / 30 W PSU with power limit set to 40 W (38.9 W is reported during the heating up stage). Without this the device just reboots on attempt to turn on the heater (unless the power limit is set to 10 or even 5 W). This code doesn't affect maximum power available and allows up to 73 W when a beefy 24 V / 96 W PSU is used. Should be useful for all models, not just TS100. The fixed comments are based on calculations, not measurements! Fixes #693.
commit sha 301f03acd0ad473d37be4f2c845ca0f4fb5ebd30
Merge pull request #697 from paulfertser/poc-limit-power Limit maximum power more efficiently using dual speed PWM
push time in 16 days
PR merged Ralim/ts100
With this a TS-I tip is usable with a small netbook 19 V / 30 W PSU with power limit set to 40 W (38.9 W is reported during the heating up stage). Without this the device just reboots on attempt to turn on the heater (unless the power limit is set to 10 or even 5 W).
This code doesn't affect maximum power available and allows up to 73 W when a beefy 24 V / 96 W PSU is used.
Should be useful for all models, not just TS100.
The fixed comments are based on calculations, not measurements!
Supposed to fix #693.
Please try and fill out this template where possible, not all fields are required and can be removed.
- Please check if the PR fulfills these requirements
- [] The changes have been tested locally
- [] There are no breaking changes
-
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
-
What is the current behavior? (You can also link to an open issue here)
-
What is the new behavior (if this is a feature change)?
-
Other information:
pr closed time in 16 days
issue closedRalim/ts100
Power limit is not doing justice to certain PSU
Observations:
Using a small PSU for Toshiba ac100 netbook rated for 19 V 30 W output. Original miniware tips: TS-I (measured 7.4 Ohm at room temperature with UNI-T T60A DMM) and TS-BC2 (7.6 Ohm). PSU output voltage is 19.0 V and the firmware is calibrated to it.
With TS-BC2, tipResistance = 70 and no power limit heating up works normally and the detailed screen shows up to ~47 W. With TS-I heating up leads to reboot unless power limit is set to 20 W or less (with unmodified tipResistance it required as low as 10 W).
Speculation:
Output PWM frequency is too low to usefully limit power drawn from PSUs with small output capacitors. I'd like to be able to play with the duty cycle but calculations involved are not outright obvious to me.
- Firmware Version: d75f361c4e274192dae5f7f1c16b7b46da296fbe
- PCB Version: TS100, v2
closed time in 16 days
paulfertser
pull request commentRalim/ts100
[PoC] limit maximum power more efficiently
@paulfertser Apologies, was not notified you had re-pushed 😓
comment created time in 16 days
push eventRalim/ts100
commit sha 471cd565b56c9d9dbee6abf6adc7bedd489ce0f2
Updated slovak translation
commit sha b18bea4d5ea3b2dd68eb5e0875c2457274769a92
Added 2 missing characters
commit sha 923989bf16e67e2e17dce3896122dfef43021126
Merge pull request #703 from DusanF/master Slovak translation
push time in 17 days
PR merged Ralim/ts100
- Please check if the PR fulfills these requirements
- [x] The changes have been tested locally
- [x] There are no breaking changes
- What kind of change does this PR introduce? Added/fixed slovak translation, added 2 characters into small font
pr closed time in 17 days
startedtejv/USBCx
started time in 20 days
issue commentRalim/ts100
Yeah you should be fine to get it going really. I will probably add PPS to this codebase when time permits.
The CY4500 was my next choice, but cant justify dropping the ~$260 on picking one up yet.
comment created time in 20 days
issue commentRalim/ts100
I definitely had some teething issues with getting it all up and running, some of that was FreeRToS related, some FUSB302 related, some with assumptions in the construction of the firmware.
If your only doing power receive you can simplify down the firmware a lot as well (I've done some of this)
1000% make sure you have a means of debugging the PD transactions, I used my Saleae Logic Pro for this, but its your choice :) PD is hard to debug blind.
comment created time in 20 days
issue commentRalim/ts100
@puzrin I'm not sure what you are referring to in terms of "original usb-pd stack"? None of the stack in this firmware is from Miniware. I didnt implement PPS at this point as it had no gains for the current use case.
comment created time in 20 days
starteddebauchee/barrier
started time in 21 days
startedmayeranalytics/pyUBX
started time in 21 days
push eventRalim/ts100
commit sha 2c626d7203119bfc9ccee0a5cc57453aada0578c
Refactor out the sleeping timeouts
push time in 22 days
push eventRalim/ts100
commit sha ed138d8db72463b1e65557c55b525a26a84546bd
Add GPIO for QC
commit sha fc5765ad2266bbf408483d9faeb6b581cd8ddbd4
Merge branch 'pinecil' of https://github.com/Ralim/ts100 into pinecil
push time in a month
push eventRalim/ts100
commit sha 8d0addd7f151b7d6409a1a836257f9b6d570c1b2
Fix build
push time in a month
push eventRalim/ts100
commit sha c9172f0f9b4034ca7a4ef3807654fc1f9004028a
Move to basic DMA I2C | handle poll FUSB better
push time in a month
push eventRalim/ts100
commit sha cd69dc1e4c4c5df33d091670baaf7986697af8d1
Save and restore settings
push time in a month
push eventRalim/ts100
commit sha 088516acea76b22dda13fd0000c66149c0cb8bca
Working auto orientation
push time in a month
push eventRalim/ts100
commit sha 89522027b7b79681c761bc276c751445f9b9c93d
Fix voltage on home screen
commit sha 42f643c40fea2f690da5ab2f4509eeaf47435108
Update I2C_Wrapper.cpp
commit sha e38da13306cc259acdd723792f303ecbb0f0f9bf
Rework _all_ of the I2C This moves all of the I2C code to IRQ based (not DMA _yet_). But it does drastically improve reliability, especially of reads.
push time in a month
push eventPropellerAero/buffstreams
commit sha 1892e71f9a5ffc78b090b02679240a7569fe7dd9
Silence logging
push time in a month
push eventPropellerAero/buffstreams
commit sha c1478480cd1f0bcc1efbb7d4ecad4287e7aec095
Handle adding var-encoded int header on response
push time in a month
push eventPropellerAero/buffstreams
commit sha 1afa8d0a8472d95877cb424926a065af1d8c60a7
Fix buffer offsets, signed length, logging
push time in a month
push eventPropellerAero/buffstreams
commit sha 6e7739cb3079cd639e2514a311236d47fe980713
Force 4byte header
push time in a month
push eventRalim/ts100
commit sha e6445491bb34ec1cd54ee9cdedbe863936fd374a
Move OLED to use bulk setup
commit sha 470cae2459954203cdf84f90f4640edcb33fbd7c
Remove I2C lock2
commit sha 60e3616c7992d07ccb59f41f9fbd5b891488adaa
Fix PD IRQ
push time in a month
pull request commentRalim/ts100
[PoC] limit maximum power more efficiently
With slight cleanup I'm definitely happy to get this merged in, thank you @Firebie for testing 😅
comment created time in a month
issue commentRalim/ts100
In regards to the usb-dfu replacement bootloader, it should work on all 3 miniware irons, though it is more "advanced" and if you don't really know what your doing I wouldn't say it's a good road to go down. As it's just much less user friendly to figure out.
I've been using some of my miniware tips since I first picked up the iron in 2016😅 so some definitely do last, but I try not to abuse them - I'm a big fan of the brass ball rather than wet sponge for tip life.
comment created time in a month
push eventRalim/ts100
commit sha ad8df08bb8f21cbd0386720ee1acc4f77f193625
Rough pass updating to add BMA223 support
commit sha 23b54526703b5c23a8c42a08073ff88624b7f5b8
Port across init reg helper
push time in a month
push eventRalim/ts100
commit sha f3747875647352e2742b56d711f2e318a947aaca
Simplify I2C initalisation
push time in a month
pull request commentRalim/ts100
[PoC] limit maximum power more efficiently
Not being an EE I naively assumed that you can imitate something close enough by limiting current with a lab PSU and adding a suitably sized capacitor at the output. I also thought you have one of those "more picky" QC/PD powerbanks.
So I own a bunch of power supplies but they are all linear basically so they just get massive voltage droop. I dont own any that "shut off" since I have replaced them
I did find it helped a bit with TS80@12V on a power limited power bank, but even this one isnt that picky. I've tried to buy random ones when I find them on sale, and so far I've been rather lucky.
I still have doubts my solution is useful to anybody but me but it complicates the code enough to hesitate adding it, IMHO.
I feel like this could give us an advantage in some heatup situations as well, and if we can reduce "time to hot" that more than justifies it too.
comment created time in a month
push eventRalim/ts100
commit sha 65ae7c8b13fffa99e87e46041cf3323f0c673535
Cleanup ADC
push time in a month
startedgnebbia/kb
started time in a month
push eventRalim/ts100
commit sha e92a81c2299aa5c89dc104e8e0c0251644220be6
Better Bulgarian language translations
commit sha 09ff363ae5ac4324ace19a9cfb0f3107a82e41f6
Update README.md
commit sha 5d358feee9df8e67bfa5f046ff8df19f0920786e
Small changes after detailed view on a display
commit sha e66fe461d2aa81e982f2e426d2fa57aed1c2145d
Merge pull request #680 from dimitroffs/better-bg-translate Better Bulgarian language translations
commit sha 76099406efa42a8cf1f455037e8c04bf4440cad1
Update FreeRTOS port-specific files to V10.3.1 This updates Cortex-M3 port files to version found in V10.3.1-kernel-only tag of FreeRTOS-Kernel. The new upstream release includes memory barriers which are essential for use with modern optimising compilers. Without those firmware certainly breaks with -O3 -flto and might be also broken with other optimisation configurations. Fixes: d59ec10c4ef5 ("Update FreeRTOS to v10.3.1")
commit sha 780f1f35ca47f2ba6b92e2fdd078ef0b81d550d9
Make flash and bootloader sizes configurable This patch makes allocating special pages automatic and flexible, allowing flash size and application start offset specification with linker command line arguments. It should allow easier porting to different targets and experimentation without adding code complexity. Many original STM32F103x8 chips have fully functional 128 kiB flash and so this additional space might come useful for experimentation, additional optional features etc. Tested on v2.51A board, including writing and verifying 128 kiB of random data. Make variables are added to control that, so to build for the full undocumented flash size and dapboot configured to start the app from 8 kiB offset one can run: make flash_size=128k bootldr_size=0x2000
commit sha c1dd88ba532bdc87d73eb82cd926a5cfc7848787
Allow SWD debugging when built with swd_enable=1
commit sha 25aee6b661ea239cd9a0b7e92fefc4429e780cd6
Move I2CSemaphore creation outside postRToSInit The code assumes that whenever scheduler is running I2CSemaphore is available. Initialising it in a task might lead to race conditions and is also not happening at all if the task is disabled (for debugging or due to lack of need for a particular usecase). The race condition can't happen with the current code though, as GUI task has lower priority than the MOV task, and they're the only tasks that currently use I2C. However, this might change in the future with the code refactoring or introduction of new features.
commit sha b331032f30a7686743824cc59ae36464ac4555a4
Makefile: remove duplicated code generation options from LINKER_FLAGS LINKER_FLAGS already includes CPUFLAGS via CXXFLAGS (and that's the right way to have the correct options defined at a single place).
commit sha 11f3eadfc9f3ec3926807374945a29bf758e17c8
Merge pull request #655 from paulfertser/temp-rfc-patches RFC patches
commit sha a64186d9a4d9496fdbd3612fbaf48ee71c7446c7
Fix key autorepeat timing This constant is in scheduler ticks so needs to be changed accordingly to keep the old timing. Fixes: e2c5e51fe19b2
commit sha 1d63a3d7bc19733994ff3632c56eea4efcdec32d
Fix temp change long step MAX value There is no space on the screen to output 3 digits, and the corresponding display function assumes the value is less than 100.
commit sha a2a23b575f7077294bd69ce76dcc212327a39d92
Pause for the last value in settings menus and blink the scroll thumb This radically slows down auto-incrementing (when the change button is kept pressed) of values when user reaches the maximum (last) allowed option. The scrollbar thumb is blinking to indicate to the user that the next keypress will wraparound (unless this value was already active prior to entering menu). Fixes #536.
commit sha 3d3799d4143b213d7e5b455e2a8c2126582b7410
Prepare v2.11 release
commit sha 372f8e35654694b77e0c3e754e3e945a5fe23410
Update Dockerfile
commit sha d9c05db05821843f6d0dcf0e9e09ef0e123d0d17
I2C wrapper cleanup
commit sha d48b27928a43d9aee83831cec64c8877fe64f9d1
Move I2C initalisations into more logical spots
commit sha 11e583be63a164b11d582d730c0721bd15bfbd1f
Fix interrupt race
commit sha 12cf20233836f2f0d4f85d6571e4a9613f7146fd
Remove reset handler
commit sha 8bacbe49fc722cd3b8479b3cf6101ea4d5c3b34f
Bring back PD 3.0
push time in a month
DataDog plugin to report sensors metrics
fork in a month
issue commentRalim/ts100
The calibration of 781 make sense, that is close to your offset. If you power cycle after the calibration is it still showing >500C when the tip is connected?
comment created time in a month
pull request commentRalim/ts100
[PoC] limit maximum power more efficiently
I have tried this on a few models & power adapters here with no regressions; though I dont have any psu's that "shut off" most of mine current limit.
comment created time in a month
startedskeeto/endlessh
started time in a month
pull request commentRalim/ts100
[PoC] limit maximum power more efficiently
I think if you just cleanup all timer operations for changing values to use calls behind BSP (so that other boards can be supported) then this should be fine :)
comment created time in a month
Pull request review commentRalim/ts100
[PoC] limit maximum power more efficiently
int32_t tempToX10Watts(int32_t rawTemp) { void setTipX10Watts(int32_t mw) { int32_t output = X10WattsToPWM(mw, 1);+ if (fastPWM && output == powerPWM) {
Absolutely agree it could be very confusing 😅 I'm happy to go with this implementation for now.
comment created time in a month
issue commentRalim/ts100
iron heats up in `[S and O]` - mode without being moved
Thank you all, @Firebie solved this before I even got back around to looking into this after work 😅 @discip If you need, you can easily use the artefacts that are generated from the merge for other irons should you need to. https://github.com/Ralim/ts100/actions
comment created time in a month
push eventRalim/ts100
commit sha 9edb7d47147b5264ff17d8abb7d387a09fc4dff6
Delay accelerometer for 2 seconds - fix for #696
commit sha aa7a035050b27c44982f1df233db33af612e099c
Merge pull request #699 from Firebie/issue696 Delay accelerometer for 2 seconds - fix for #696
push time in a month
PR merged Ralim/ts100
Please try and fill out this template where possible, not all fields are required and can be removed.
- Please check if the PR fulfills these requirements
- [x] The changes have been tested locally
- [x] There are no breaking changes
- What kind of change does this PR introduce? Fix for https://github.com/Ralim/ts100/issues/696
pr closed time in a month
push eventRalim/XTConnectors.pretty
commit sha 1d41f6315c21831ee25073e1ede8d52bcf0207d4
bump pins in slightly
push time in a month
issue commentRalim/ts100
Your rtip values are reading lower then normal, which most likely means that your iron does not use the exact same op-amp part as other irons, but with calibration should be in range as that should derive a lower calibration number for you that should compensate i believe.
comment created time in a month
issue commentRalim/ts100
It should only show that when the tip is disconnected :/
Have not been able to reproduce this at all across an entirely new set of tips..
Out of curiosity if you run the calibration when cold what number does it show you ?
comment created time in a month
issue commentRalim/ts100
Gah damnit.
:/
I might just have to order an apple power adapter to figure it out :/
Sorry about that
comment created time in a month
issue commentRalim/ts100
You just have good timing 😅
Double copy:
Connect device in DFU Copy hex file once Device reconnects and has .ERR Copy file again Device reconnects and has ERR and RDY
Extract: Just don't try and drag the .hex from inside the zip. Put the hex file in your downloads or somewhere. You don't need any of the other files :)
comment created time in a month
issue commentRalim/ts100
Hmmm.
No special magic that I'm aware of.
Are you doing the double copy, and also make sure to extract the zip first?
comment created time in a month
issue commentRalim/ts100
OLED Screen flickers as going to sleep
Is this issue still occuring for anyone? 😰
comment created time in a month