The Final Revision
- Thread starter EvilDragon
- Start date
Caine
Hardcore Member
Oh no. This is the start of another youtube journey through British comedy sketches. I just know it.
God Ginrai
Godmaster
Pyramancer
Fairly Idle Member
- Joined
- Feb 4, 2017
- Messages
- 232
- Age
- 124
You're missing the "title" text from this comic [1]: "Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shit."
[1] https://xkcd.com/927/
[doublepost=1534387470,1534386321][/doublepost]I've been idly thinking that the Pyra really needs a VGA connector. And a 25-pin RS-232 port could prove useful. And a kitchen sink would also be a nice-to-have, so that we can brag it's got one. And a connector for a docking station. So many interesting things to think about for an imaginary future version!
Last edited:
levi
Still fresh, damnit!
You can find many examples of USB RS232 adaptors, and 15-pin VGA adaptors too. I'm not aware of any USB kitchen sinks, but it's fair to say I've not actually checked. And I've never come across 15-pin RS232 either; it's always come on a DE-9 or a DB-25 where I am.
ClockworkCoder
Chaotic Neutral
Pyramancer
Fairly Idle Member
- Joined
- Feb 4, 2017
- Messages
- 232
- Age
- 124
Indeed. But they don't work reliably (I've tried both FTDI and Prolific chipsets), especially with slower devices with which reliable flow control is essential.
Yup, that was a typo. I've corrected it now. Thanks. (I've been using a full-sized keyboard for a few days, and coming back to the compact keyboard on my laptop, my "2"-finger reaches the "1" key!)
[doublepost=1534418390,1534417295][/doublepost]
Strictly speaking this overvoltage design flaw is a consistent issue that was intermittently observered, rather than an intermittent issue. What a _huge_ relief that it can be worked around in software! (A board revision and another year's wait would have been A Very Horrible Thing.)
One can't help feeling, though, that this mistake should have been discovered when the prototypes were being tested last summer. Perhaps there is a lesson to be learned here and the test procedures can be made more thorough/complete.
Last edited:
ClockworkCoder
Chaotic Neutral
To be fair, practically 100% of hardware/software issues can be predictably recreated once the underlying issue(s) are identified. The hardest part is usually identifying those root causes.
And yes, it is a huge relief
Regarding any "should have": hindsight is a great thing in terms of identifying what _could_ have been proactively done, but what matters most is that the issue has now been identified and fixed.
