Dave, your video is unlisted on YT. On purpose?
Some similar projects are scams, in that the guys leading them KNOW their idea sucks and that they will never deliver.
I don't think that's the case for Vion. I think they were just a bunch of well-meaning people, but inexperienced and not knowing anything much about electronics in general, safety and metrology in particular. Looks a bit like a bunch of pure software guys willing to develop a hardware product.
Some similar projects are scams, in that the guys leading them KNOW their idea sucks and that they will never deliver.
I don't think that's the case for Vion. I think they were just a bunch of well-meaning people, but inexperienced and not knowing anything much about electronics in general, safety and metrology in particular. Looks a bit like a bunch of pure software guys willing to develop a hardware product.
But the software sucks
They stated back in the February update that the Vion case is "fusion bonded", I hope they have some non-destructive means to open every housing, repair the faults and stick the thing back together in accordance with the certification.
If anyone was a backer then worth posting my video in the comments.
Some similar projects are scams, in that the guys leading them KNOW their idea sucks and that they will never deliver.
I don't think that's the case for Vion. I think they were just a bunch of well-meaning people, but inexperienced and not knowing anything much about electronics in general, safety and metrology in particular. Looks a bit like a bunch of pure software guys willing to develop a hardware product.
If anyone was a backer then worth posting my video in the comments.
New video:
More likely than not, the first concept drawing had two free-wheeling probe tips, without the need to connect them with a clumsy wire.
Looks a bit like a bunch of pure software guys willing to develop a hardware product.
Also that Nordic MCU they have used is great for Bluetooth Low Energy support but it does not support classic Bluetooth - could that be why some people have issues connecting to the device? I don't see BTLE being requirement mentioned anywhere. But then it could have also been a simple bug/crappy programming because it is unlikely the older phone would have been working and a new one not.
I typically are not a fan of these tear people apart videos, but I think this is a case where it's very much a needed and justified. There's no way they had the knowledge or should have been developing a product that was advertised as suitable to measure in lethal environments and had the balls to fake meeting electrical standards. I'm all for the give then a chance camp until they pull this kind of shit.
Going for BLE only in the 121GW meter was a big mistake. We thought we could just implement a simple serial protocol and that would be it, but BLE doesn't properly support serial interfaces like the full bluetooth stack does. It was a massive multi-month effort by David2 to get it all working as seamlessly as it does, and he's a gun programmer (although had no experience in BLE). Expensive mistake.
(BTW, same thing has happened again with USB-PB on the uSupply, it makes the BLE problem look like a cake-walk)
Looks a bit like a bunch of pure software guys willing to develop a hardware product.
vMinimum viable product. Lean startup. Ship it and then we improve based on the feedback.
Going for BLE only in the 121GW meter was a big mistake. We thought we could just implement a simple serial protocol and that would be it, but BLE doesn't properly support serial interfaces like the full bluetooth stack does. It was a massive multi-month effort by David2 to get it all working as seamlessly as it does, and he's a gun programmer (although had no experience in BLE). Expensive mistake.
(BTW, same thing has happened again with USB-PB on the uSupply, it makes the BLE problem look like a cake-walk)
Going for BLE only in the 121GW meter was a big mistake. We thought we could just implement a simple serial protocol and that would be it, but BLE doesn't properly support serial interfaces like the full bluetooth stack does. It was a massive multi-month effort by David2 to get it all working as seamlessly as it does, and he's a gun programmer (although had no experience in BLE). Expensive mistake.
(BTW, same thing has happened again with USB-PB on the uSupply, it makes the BLE problem look like a cake-walk)
Ah that seems not too surprising, USB-PD seems absurdly complex for what you get. QC3 can be done with four resistors and 2 I/O pins.
Of course USB-PD is the way to go for PC based compatibility and future use, just fun to compare the two..
Yep, and David's still working on USB-PD...
It has involved both hardware and software USB protocol decoders (both of which had bugs that hindered progress) and countless hours. It's not just USB-PD though, it's HID and all that other stuff and getting it to work as driverless and as universal as possible.
It's why the TS-80 soldering iron uses QC3 instead of USB-PD
What does USB-PD have to do with HID?
HID is a major pain in the butt, especially given the millions of ways the same thing can be encoded in the descriptor but only one or two work in Windows (so the standard is not really the spec but "whatever Windows accepts"). But I don't see why that would be a reason why a soldering iron would use QC3 instead of PD, given that HID is totally unrelated to it.
What does USB-PD have to do with HID?
HID is a major pain in the butt, especially given the millions of ways the same thing can be encoded in the descriptor but only one or two work in Windows (so the standard is not really the spec but "whatever Windows accepts"). But I don't see why that would be a reason why a soldering iron would use QC3 instead of PD, given that HID is totally unrelated to it.
Because daves power supply needs to communicate with the PC, presumably for the SCPI control. HID = comm, USB-PD = lots of power.
The TS80 does not use HID, but uses comparatively simple QC3 to get the high USB power transmitted. Implementing PD would add cost and development time.
But USB-PD does not depend on HID for anything (and neither the other way around).
You can use HID + QC3 or you can use HID + USB-PD or whatever other combination. The two technologies are totally unrelated, heck they don't even talk over the same wires (HID runs over standard USB or Bluetooth, USB-PD uses the CC pins of the USB C connector).
USB-PD is a complicated mess but it is a different mess than the HID protocol. That's why these statements don't make any sense to me.