[Long] TS80P Thread #630
[Long] TS80P Thread #630
Comments
|
Ohhhh ... how I have been waiting for this!
Nevertheless I think you (and everyone contributing to this) are going to make this thing even bigger than its predecessors including the TS100. a big THANK YOU in advance |
|
@discip Ah awesome :)
I'm hoping mine will turn up soon. Once it does expect me to start poking at its support |
|
@Ralim
I am looking forward to this, almost impatiently. regards |
|
Well I've retired! All the virus stuff has given me the opportunity to jump ship on very good terms. |
|
@Ralim My focus is to get a reasonably small, well build (quality wise) and not to pricey one. Regarding the specs of the unmodified TS80P, its max power draw amounts to I hope you got my point. Since there are plugs providing up to thank you in advance |
|
@discip I have a 30W adapter here that I have totally pushed to 35W (gets a bit warm, but its done it for like 2 years now). So there is probably some room in there too. I would pick either 45W/35W/30W depending on size and ease of picking it up :) |
|
@Ralim This depicts the pins of the top and bottom of the same side of the power cable: This shows the pins, top and bottom, of the irons inlet: This is obviously the top side of the PCB: And here is the corresponding bottom: This was really not easy to achieve. Especially taking the pictures of the USB-C sockets / plugs was some tedious work. regards |
|
Glorious! Looks like a dedicated USB-C PD IC, so compatibility should be good Those USB-C plugs are like I thought, no high speed signal pairs (USB3/thunderbolt).
Which is great as it looks like any USB-C cable will work, nothing "special" other than the nice silicone outer. Interesting to see PD+QC on the same plug on the adapter as, as far as I know, you not "meant" to do that |
|
@Ralim |
|
Look forward to. My TS80P got into trouble, something went wrong while trying to change the bootup picture. It seems I accidentally messed up the firmware. When connected to a power source, the soldering iron does not work - only the default bootup picture lights up and nothing else happens. When connected to a computer, I see a virtual disk, the boot module for updating the firmware works, but there is no hex file for TP80P to flash it. A huge request - as soon as you have a soldering iron, lay out first of all the native firmware. Thank! |
|
Mine hasn't arrived yet but when it does ill definitely be racing to get a tester firmware up. |
|
I would be guessing that its just the OVP protection in the USB-C interface being used for marketing? In the past there hasn't really been PCB revisions (other than the "upgraded" clone irons that are missing protection circuitry). |
|
|
@Ralim ps: What do you think about GaN technology in general, do have any experience in this field yet? thanks in advance |
|
I have a GaN charger (2USB-C/100W, 2QC/18W). Works wonderfully for all my USB powered equipment. Haven't received my TS80P, yet, but should be here in the next couple of days. I'd expect it to work fine with that charger. From my limited experience, I can absolutely recommend GaN technology. |
|
@discip. Hopefully the manufacturers have learned and improved their kit to expand the list of compatibility - but certainty ... only when you have one plugged in making the iron melt lead can you say yes for certain. Small with big currents and voltages is never going to be a good idea - it also depends on your standing voltage. The US use 110v, you can virtually lick the prongs to test them - but UK, EU and Aus uses 240v - that will give you a very hard slap if you extend your tongue, it will even ump the wall to get to you - with 240v you need physical separation and ideally big air gaps between tracks to ensure safety. |
|
@discip By my eye that looks like it will work 100% fine. Its USB-PD spec compliant, it has the 12V option, and it has adjustable voltage (which is nice). I see no reason against it. I've only used some GaN chips, and for all of the power applications I have used them in they have worked perfectly no noticable issues at all. So i wouldn't be worried about it. If there are issues with the charger its probably due to other stuff At least PD is a fairly good spec, so they all should work :) |
|
@gutschke |
|
Today, firmware for a soldering iron has become available for download: |
|
I fully understand having a life away from stuff like this. I am just wondering about progress on this. |
|
@brencerddwr Working:
Not yet working:
Have been focusing on the USB-PD and its just a nightmare to debug with the setup in the iron; I have ordered a breakout board for the FUSB302 chip inside the iron; but also will continue to test it as I have time. Handle temp sensor is odd; not sure if they have moved the pin or changed something in the schematic. Will most likely need to trace the connection to figure that one out; but should be fast. Main reason its a pain is that the FUSB302 is just a PHY so it doesnt actually contain any of the logic for talking to the power adapter; that all has to be done firmware side. |
|
@Ralim |
|
@Ralim, when you get to the point of the USB PD and handle temp sensor working, I would be willing to beta test for you. If I understand correctly, since it uses DSU to update firmware, it should be almost impossible to brick my TS80P. |
|
I'm excited that PD is implemented in software. In the long run, that should give a lot more flexibility. But in the meantime, it's just a lot of extra work. On the other hand, I suspect that an initial release without PD would still be useful. Even if only QC is enabled, the device could be used. Features would be a little limited, but that's OK for beta testing. |
|
@gutschke it depends. It gives more flexibility in negotiating the PD parameters, but at the same time the firmware is going to need extra space in the STM32's flash. STM32F103T8U6 has 64KB flash. Current TS80 firmware size is 36KB + 16KB for the DFU bootloader. This leaves "just" 12KB. Some of it is also used for storing user configuration (probably not very much). I hope @Ralim finds a way to fit everything there :). |
|
On Sat, Oct 17, 2020 at 10:35:59AM -0700, Marcin Jaworski wrote:
How is it broken by design? Do you mean that MiniWare wanted to make
a broken DFU intentionally?
Impersonating UMS for firmware update purposes is defective by design.
|
You got me. I didn't think that through. So how are they doing it? Are they assuming that Windows would write the blocks of the file in order? No matter how they are doing it, I wholeheartedly agree with your second statement:
|
|
@paulfertser well, I don't do anything like that. On my system I'm simply dragging file in Nautilus from my drive to DFU's mount point. Nothing less, nothing more. It has always worked for me. I'm not changing any system settings, I'm not emulating how Windows does this etc. |
How come you're not using unbuffered I/O? If my above guess of how the DFU works is correct, the writes to the output file must not end up in the cache where they could potentially be reordered. AFAIK, bypassing the cache is called direct I/O. Also, your block size is 512 Kilobyte! So the whole file is transferred in a single write call. This command would use direct I/O and omit the sync call:
|
This has never worked for me! Probably due to the fact that Linux has the cache enabled for USB drives by default. |
|
@skoehler if you need me to check some settings on my OS then don't hesitate to ask. I'll try to provide whatever I can, because my system is definitely an example that it can and does work. Regarding my dd command, I've forgot |
|
Maybe it's a language barrier (English is not my primary language), but if I understand correctly the phrase "broken by design" means that it was author's intention for breaking this deliberately so it won't work anywhere than on Windows. Do you really think that was MiniWare's intention? Or is it just a lack of proper QA and testing on different systems? Unfortunately software design and software support in Chinese products is what it is, but I would go as far as to assign them bad intentions in that regard. Sorry for the rant. |
UPDATE 2: I gave up on Windows 10 and switched to my Linux machine. By writing the firmware twice I was able to get a .RDY |
|
On Sat, Oct 17, 2020 at 02:34:52PM -0700, mdroberts1243 wrote:
with the latest Ralim firmware I was able to get better results
using the USB-C port with it running for a least a few minutes vs a
But then it still turns off? Are you using the power limit setting?
|
|
@skoehler can you check your mount options when you connect your TS80P in DFU mode? I've just noticed that udisks2 adds a flush option in my system. This causes immediate write of data to the drive. This is a vfat fs mount option. |
|
I can't get the custom logo to work, the iron will not boot, any ideas? |
I suppose you did try the python script and you got a hex?? are you getting an ERR or a RDY file after you copy the hex and last :) is this the process you follow ? https://github.com/Ralim/ts100/blob/master/Documentation/Upgrading.md |
Ok, I was using the windows GUI, python worked great, Thanks! |
|
I've missed this chat, I've had so much going on(negatively, unfortunately) that I haven't even made one attempt in the last couple of months to upgrade my firmware. I kept getting notifications to my email about this chat, and every week or two, I'd go back to wanting to come back and read every message and spend hours responding to everything relevant. I still haven't even used my device yet, and I've got numerous tasks that have been staring me in the face., really wish I had ordered a brass ball from Ali already. I didn't have too much free time to do this message, but I have full intention of going back through the last few months, tagging and responding to everyone who responded to me or made a suggestion to my issue; as well as bringing up any interests I have in what's already being discussed. I hope everyone has a Merry Christmas/Happy Holidays and a solid New Year. |
|
@SantiCO19 I just spent a while and couldn't seem to find them, do you have a link possibly? Also, what thought process behind disregarding"liquid silicone" and "liquid silica gel" is there? |
Absolutely. I can't imagine there being cables superior to these, for our application. They are top mechanical, and materials, quality, and very reasonably priced [cheap!] Here are the ones I can vouch for, since I purchased from these exact listings: A to C - C to C PD- Here are some others that I would wager are legit, but I have not purchased: A to C - Regarding my warning about "liquid silicone," each cable I purchased with this description turned out to be some nasty stiff cheap plastic cable. Further, they did not pass the spec'd current, so weren't even good for a standard use cable. And if you dig down in the listing deep enough, after calling the material 'liquid silica gel,' 'liquid glue,' and other things, you will see they finally labeled in one instance as, "PVC." If I'm not mistaken, that stuff makes highly toxic fumes when heated, so definitely not good for any electrical application. Here is an example to STAY AWAY FROM: DO NOT BUY (confirmed) - Hope this helps! Think I had spent my budgeted time on my original post, hence no links in the first place. |
@Beyond246 Pay a little extra and get in the UK/elsewhere from RS Components(next day collect or delivery), CPC, amazon/ebay. The brass ball is wonderful, although a wrung-out sponge serves well enough. Good luck taking the plunge and using it for something... Also I enjoyed this thread like a long running gossip column / hackaday comment section about my favourite new toy the TS80P, so thanks and happy holidays to all. |
|
Do hope the PD compatibility can indeed be improved somepoint, I actually picked up a small PD battery pack recently that seems to not be negotiated with at all ( but laptop does negotiate to the specified 18W ), but forrtunately it does have QC3 that works and actually gives out 12v at about 2A, but I'd prefer to be able to use the silicone C-C cable directly without adapters. |
|
It can definitely be improved, however so far I have not been able to find any units that my iron will not negotiate with |
|
Happy to help try and test anything against the powerbank I have ( also have apple 87/96W power supplies that can test against somepoint if something new to test there, I recall they needed some work still too ) |
|
Confirming that I’ve still been unable to reliably power my TS80P from my 96W MBP 16” supply |
|
Actually, just retested the powerbank again and it does actually work, it just took longer to negotiate than I maybe expected! Though it does seem not entirely reliably, hmm. |
|
How expensive is the power bank? If it's cheap I might pick one up to test |
|
It was pretty cheap from Lidl here ( think regular price was 15e, but I only paid half as were clearing them off ), so not going to be an easy availability one. Once it's going it works fine and actually supplies more power apparently than official rating says, at least iron says taking ~26W at 12V, bank is supposed to be 18W rated. I was just using it for an hour or two soldering some light strips just now, but seems to be touch and go whether it negotiates first time before bank cycles off, but if just leave it, it power cycles and then successfully seems to negotiate second time round. |
|
Ah, so that may be the fun of not all power supplies "yell" their specs for long enough for us to get through the miniware boot code as well. if PD fails with CRC errors, the power supply will reboot and re-try which is possibly whats going on. |
|
Sounds possible, if there's some simple stuff that could be tested easily I can help, already got cubeide installed for some other project stuff so I can change variables and recompile most likely to iterate something, and if there's some easy way to hook up debug stuff I have a j-link too. |
|
Btw. with the dfu flashing, what status/error does .NOT indicate? not ready or not right firmware? edit: not right firmware I guess, forgot it was the .hex and not the .bin supposed to copy. |
|
|
|
Just finally updated to Pencil release from official firmware v1.23 because
my Innatek charger (60w) kept resetting the TS80P. Got away with dragging
the hex from the zip :)
New firmware looks good, love the Extra info screens.
Had one reset so far and a few times starting at 5V rather than the 12V
set. Seems reliably at 12V now every time so I'll have to keep an eye on
it.
My saving grace so far / best purchase was the Ravpower PD Pioneer 20ah 60W
powerbank (RP-PB201) as it works flawlessly with any firmware/device.
…On Thu, 31 Dec 2020 at 13:23, Ben V. Brown ***@***.***> wrote:
.NOT means that it was not interpreted as a valid HEX file is my guess so
far. Generally only had that issue when I've sent a hex in invalid address
range or accidentally senta bin or elf instead.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#630 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTBZ42WZ4ZN65X6TMVO43DSXR3OLANCNFSM4NHYDSSQ>
.
|







Creating an issue to track the upcoming TS80P.
So anything said here is speculation at the moment😁
My current understanding I have pieced together is that it is possible to just add support for the USB-C to the current TS80 build. I believe it is a USB-C interface attached to I2C, so expecting adding support shouldn't be too hard as will only require handling its configuration.
My plan is to acquire a TS80Pas soon as possible and get to work on the firmware side.
I have tried and we are not getting schematics soon (will eventually exist apparently).
I'll update this top message as things happen.😆
Try to keep on topic in the comments
Edit 13/06/2020:
My unit has arrived, and I'm looking into support carefully now.
Looks like quite a few small changes (few resistors have changed), so will need to re-calculate some of the equations as well.
Not 100% sure if will make a different FW build, or if make TS80 firmware auto-detect.
USB-PD is just as complex as I remember it, still a bit of work here to go I'm afraid :(
USB-C
Edit 28/07/2020
Beta firmware is out, hopefully this works a fair bit better for everyone.
ROM space is a bit tight so still will probably do some cleanup before deploy but want feedback on PD.
The text was updated successfully, but these errors were encountered: