Thank you for the firmware update Iwanushka! Will you share the source code also? It would be awesome to have it on a Git repository, so that i can link it in my documentation repo
Hello mate,
I will update gitlab project, in around a month, still need to do the following: 1. write proper readme/wiki that details how to connect all irons, 1.1. read trough entire thread and collect all info into a wiki, like known issues and work arounds, most common mistakes and how to solve them a.k.a trouble shooting section, I've asked quite a few guys to do this, but until now only Doomedahab is helping me out. 1.2. collect all request for new features. 2. collect other open projects that could be useful for improving UniSolder, 3. make proper universal BOM, 4. cleanup source code, at the moment I'm codding without debugger, it's traveling from china for quite a few months, most likely lost, due to "COVID-19. 5. Also I want to finish a few things before sharing source, right now it's a mess 'cause Im coding blind, and only Doomedahab is testing firmware and reporting bugs.
Doomedahab again and again, thanks for helping me out!
P.S. before I said that I'm not taking any donations, but in current situation with the lockdown, no job too, I have high risk to end up 6feet under if I catch that crap so i stay at home, non of the damn companies like engineers working from home so no job) , Thus I changed my mind, due to my current health situation (can't even get treatment for my very severe pain because hospitals are closed for non dying patients,, and they can't prescribe IV meds nor give them to be me to take home so I can do infusions at home because you need special equipment and you cannot use them without anesthesiologist monitoring you so Im in so much pain, and I can't do all those tasks listed about except for programming alone). Also I keep all development stuff on private server, etc that costs ~27e-month, which I don't have so most likely will have to close all services and use free services, that don't have features that I need to speedup development).
NOTE: if you have any complaints or new features feel free to enter them here or in the gitlab (if you have permissions to do so, if you don't PM me): https://gitlab.com/unisolder-5.2/unisolder-v5.2
NOTE2: if you have iron that is not supported, you can always send it to me and i will add support [don't forget to include at least 1 cartrage/tip], please note that will won't happen in a way. In this case crowd funding for the Iron would be best option I think,
NOTE3: Doomedahab knows what I have in mind, regarding UniSolder we daily discuss over the phone what's needs to be done, etc. so he might provide you with more details, I limit my PC time only to develop firmware, that's it, and typing all this stuff using smartphone is real pain and I mean it literally my my entire spine is messed up including neck have 2 level herniation which cause severe pain, in entire spine + my hands hurt like hell and I'm not even talking about them being numb or no strength in them or them shaking like crazy.
Conclusion: all donations are welcome, so if you are interested into new and improved UniSolder (first will fix what can be fixed with firmware only, after that I will working on hardware changes) it does not matter if it's 1€/1$ or 100 feel free to donate, my paypalme link: https://paypal.me/MPranukevicius?locale.x=en_US or use email mantas.pranukevicius[at]paypal.com
change log: Changelog v5.2.0.1 1. added option to swap most left {Up/+) button with most right (Down/-) button In settings menu - CTRL ORDER parameter: L->R option - left button Down/-, right button Up/+ R->L option - left button Up/+, right button Down/- 2. general code fixes/improvements, does not affect behavior, just increases development/debugging speed
Next version will have option to change temp adjustment step.
Also we might need separate forum thread for discussion regarding project development or we can try to do it here + gitlab issues feature. Also sorry for all misstypes, using mobile phone to write notes, and I just copy paste them here
Regarding public repository on gitlab it's a valid point and opening it to the public has lots of advantages e.g. 1. Everyone can sumbit bug reports 2. Everyone can submit tickets for new features 3. Everyone can see what progress is made. 4. Everone can see on which task we are working and "weight" a.k.a priority of the issue. But as said before first thing we need to prepare repository accordingly to industrial standards (I had to oversee international team of QA (testing) and developers, that involved in software, firmware, and hardware development) from experience I know how it is to deal with all this if the rules for development are not set correctly. Before opening it to the public we need to so the following:
1. Split project into sub projects: A) firmware has to be split into bootloader and into actual firmware that does all the "magic" B) software has to be split from firmware, taking into account for protocol changes between firmware and software. C) schematics and PCB has to be split.
2. Project must contain proper instructions for developers: A) how to sumbit code and what to submit. (only source code, compile time stuff and binaries should not be in repository). B) all work should be done in separate branch (one branch per issue). C) code from branches must be tested by QA before merging into master branch. D) if we have support for multiple components (e.g. different drivers for Screens) all drivers should be in the same repository not in 10 different ones, specific driver selection should be done using compile time compiler commands. E) developer should never merge his own code into master branch, other developer should do code review and if everything looks okay then merge it.
3. All dvelopers should use same development environment ( I will setup dev virtual machine for this and host it somewhere like dropbox) this avoids problems that arise because of different setups.
4. Project must contain proper instructions for entering new tickets into the system.
5. We need somewhat semi-proper wiki that explains this for end users: A) how to compile software and firmware. B) how to assemble boards, we had some many issues regarding this. C) how to connect different soldering tools D) how to calibrate system E) how to add custom profiles for new tools.
When this is done everything will go public, please bear with me, I still don't have working set (damn customs messed things up), also because of above I'm not 100% guaranteed that I setup gitignore files accordingly (you either will have compile time files in the project that are usless, or you might be missing some files and you can't compile a thing.
If I missed something others can pitch in and leave comments.
Regarding donations, it would really help, especially when things will be hosted on private server to pay for it, but for now let's postpone it. Also we need to decide how developers will share the donations. Until one one pays you you do it either to improve your own tool, or your skills, etc. But when money gets involved we might end up with 200devs that do nothing just play in the sandbox for the sake of the money
OK , let us know when it becomes public repo, I would be interested to follow (since I have gitlab account
As I mentioned above, keeping dev stuff private from non dev people is safer, we don't want to burn your hardware or house, tested firmware will be uploaded to dropbox or something like that, I can give reported access to anyone who wants to test firmware and make new tickets for current issues/new features, also on gitlab we keep source code only, which including built firmware after its tested will be available to public, ofcourse if you can compile firmware and are willing to test it let me know will add you to gitlab project.
Also if there are others who want to join in developing firmware let me know.
P.S. regarding Altium its not against sharing the project files, there is only one condition you need Altium license to use/open/edit that project, I have altium too, sparkybg just didn't want to share project most likely as protection from all those ebay/ali sellers, who want to redraw schematic/PCB/firmware to tweak it for better sales..., but that is not an issue for us we can redraw schematic, we can generate PCB project from gerbers using Altium, which is in todo list, but firmware comes first
P.S.2 yes gitlab is much better, also when things start moving along (need to add wiki, etc) I will move project to my dedicated gitlab server which allows you to compile and deploy firmware directly from gitlab project, github don't have this option...
I'm setting up gitlab project for keeping our work (software, firmware, hardware) and issues, at the moment project is "private" until I finish setting everything up, and make sure that there are no problems with it, after that it will be open to everyone, but right now want to make sure that we don't break existing hardware.
At the moment we have 4 volunteers: Developers (can add/edit issues, upload SW/FW/HW changes) 1. Alexandr a.k.a Talkos 2. Mihrz 3. Tim a.k.a TimFrankenNL Reporters (can add/edit issues) 1. Doomedahab - Main person who made this possible by donating hardware for me!. if you need more permissions please let me know and I will update your account.
if there is anyone else who wants to help in any way e.g. please pm me with your gitlab.com account and in which way you want to help and I will add you to the project. 1. testing firmware and reporting existing issues (in this case bugs) in gitlab. 2. creating "issues" with suggestions what needs to be proved or what new features we need, etc. 3. software, firmware, hardware development.
P.S. you can also report bugs and new feature request, etc. here too if you for some reason don't want or can't use gitlab. I will add them myself in bug tracker on gitlab.
short howto for development will be like this: 1. someone enters a bug or a feature, we review and verify it (bugs only) 2. someone fixed bug in a branch, then we do code review, perform QA if everything is okay we merge code into master branch. 3. binary files will be uploaded to dropbox and added to the forum. why separate place for binaries? because keeping compiled code in git is complicates and slows down development process plus it uses valuable space, + as I said before slows down commits and complicates matters.
for new features process is the same except, in step 1 we have to decide weight for the feature (how complicated it is to implement it, how useful it is), thus most important things will get top priority - specially if it's an easy task to do. Note: implementation time for requests that ask to add support for new devices, will depend on device availability (e.g. if non of the developers have the tool nor need that tool himself at the moment, we will either need to borrow device from someone or crowd fund purchase of it (if majority needs support for it), or wait until developer(s) decide that they need that tool for some project and the tool would pay itself)
P.S. sorry if something makes no sense its 4AM right now. also if you have any other suggestions let me know.
P.S. when things start moving forward I will move project from gitlab to a private server so we can have automated firmware deployment (automatic compile of firmware on that server, so you can test changes in real time, even if you don't have development environment to compile firmware and you don't want to wait for developers to compile and upload firmware manually)
According to your BOM you plan to source Q2, Q8, Q10, Q11 from Aliexpress. I would strongly advise against it. The chances of getting fakes are very high. Farnell has these in stock. Yes, these are a bit expensive but getting fakes is far worse.
Hey mate, you can trust Chinese Fets as far as you can trow them, 99/100 it will be 1/10th spec used Fet with new engraving
Also if you can please upload all your firmware/hardware modifications as original CAD/etc files so I can mare them in mainline firmware/hardware, my opinion is we make separe branches for all changes and then we merge them into single firmware/hardware, we will just add checks so people can enable/disable that stuff if they need it, keeping multiple firmwares/hardwares would be a nightmare to maintain the P.S. sorry for any misspelling/nonsense, I haven't slept for 2 days and I need to be at hospital again for tests in 5 hours
Guys please register at gitlab.com and tell me your email addresses and nicks so I can give you access to our development system, also I will setup slack so we can communicate regarding development in real time and ofcourse to keep this thread clean of brainstorming ideas and other clutter also we will have dropbox to keep compiled stuff, documentation, etc so we won't end up with lots of clutter in gitlab and in this thread, later on I will move all of this to my personal server to make sure that things won't het lost. Thanks a lot P.S. when you send me gitlab info please let me know if you will be a reporter that reports issues, aska for new features or are you will.be taking a role.as a hardware/firmware developer
Checked what I have from Irons list below: 1. JBC PA120, same tips as T210, so can be used to test T210 changes 2. JBC T245 3. Hakko T12 both org and clone irons 4. Bunch of hakko 936 clone irons (TC) 5. Original Hakko FX888 Iron (PTC) ---------------- My background: was working 8 years at US access control company as SW/FW/HW engineer.
My main hobby is making controllers for temp control and temperature measurements (ovens, soldering stations, pre-heaters) - I never buy any stations only non electronic parts l, everthing else is DIY (Im not rich to pay 10-20x more for controller vs Iron that I can make myself)
Seco hobby making access control, security, building automation solutions
I think I've built my first TC based fully analog soldering station in like 5th grade (I'm 32y old),
Second one was digital solution with analog sampling done in 2008 as part of my CS Engineering thesis also as part of that I've made fully digital temp controler with TC using MAXIM converters, but sampling rate is too long even for good old TC irons, so this works only for pre-hearers/ovens, but again analog frontend with ADC is way cheaper.
Also I have all tools for debugging hardware and firmware.
Regarding firmware changes in unisolder I did fix TC profile for generic TC irons, and some overflow issue, which Sparky fixed himself too
If you have a list of bugs/features let me know I can look into it, but don't forget that I can't mess around with stuff that deals with temp control without testing it, because if your house burns down I will be held resposible and I will never do this nor planing to do it, after all I spent to many months working on like hardware at gas&oil plants and safety first!
Also if we are doing this I will need list of all bugs/issues/new features. We can use my gitlab sever for this.
P.S. if I reply to posts PMs only after a few days don't worry I'm still here, finishing one HW project that needs to go to Fab house as soon as possible, paying bills comes first
P.S. if you want to see some of my projects I can show only my University project for soldering station, else ended up commercial even if its one off can't share schematics, etc. Best Regards, Mantas
I can send a set to you on the promise you will make a serious effort to improve the firmware. Let me know if you want to follow up on this via PM. Shipping costs would be on you.
Anyone who wants to donate a small amount to lessen the cost for me is welcome to do so, but let's first get this going
I will send you PM this evening after I check what Irons I have and my experience in electronics/embedded C,
Getting someone well versed in C programming interested in Unisolder would be great :-). I would be willing to donate a set to such a person in exchange of firmware development if that is what it would take.
Hello, Firmware upgrade and fixes was in my todo list there are a few issues in it, but my dc/dc blew up and all boards got fried by 400V, if you are willing to provide working set, we definitely can improve firmware, we just need to compile a list with was needs fixing, and a list with new features from memory I was planning to add auto sleep/hibernation, hotswap for the tips and ofcource rotary encode.
You can wait I can to we when I get new parts/pcbs, but that wont be earlier than 2020 september (completely busted my back and lost of other things so no money, living with 200eur a month is no fun) P.S. maybe someone have altium project files? Sparky refused to share original files because "altium is not free stoware
, let us know when it becomes public repo, I would be interested to follow (since I have gitlab account 