5 ms·
Hey, I worked on the touchscreen at the end of the armrest. Internally at John Deere it was called GSix (6th generation). Built with Qt, WindRiver Linux, ran on
by throwaway894345 7y ago
Hey, I worked on the touchscreen at the end of the armrest. Internally at John Deere it was called GSix (6th generation). Built with Qt, WindRiver Linux, ran on a custom board (that 1"+ thick display is _just_ the monitor), resistive touch screen, speaks CAN/j1939/etc. One of the things it talked to was a buggy Bosch radio over a home-grown protocol that didn't actually expose the radio's state, so the display was forced to make educated guesses. This was a huge pain, especially WRT bluetooth pairing (at one point we had an error screen that told the user to just power cycle the radio because the display has already tried everything we could think of to get the radio back into a good state).
The contractors for whom I originally took over apparently had a contract to write unit tests, probably for a certain amount of test coverage or something. There was a bunch of dead code buried that was only executed by the tests, apparently to bump up their unit test coverage. This was one of many such horrors. We ultimately told management that it was cheaper to rewrite the thing than it was to fix their backlog of "must have" bugfixes, and it was a huge success. Still didn't fix the radio issues, however.
- whylie 7y agoThanks for your personal story - I love reading stuff like this.
- EvanAnderson 7y agoI've done a few projects interfacing embedded devices, and the "I must guess at the device's state because the manufacturer didn't think communicating that was important" scenario fills me with sadness and rage. I'd love to slap around every developer who thought that making such a device was a good idea.
- Gibbon1 7y agoThat's a problem with abstraction layers and hiding state, observability goes into the toilet. Interesting thing I learned about designing production test equipment. If you show the operator all the nasty state information they quickly learn to associate trashy diagnostic output with corrective action. That janky message means, run it again, it'll pass. This other one means that row of pogo pins needs to be replaced.
- tonyarkles 7y agoHopefully if you ever end up working on a device with firmware I’ve written, you’ll end up pleasantly surprised. I’ve worked all over up and down the hardware/software stack from mobile UI down to gate-level design, and one of the biggest principles I’ve picked up over the years is that observability is absolutely a hard requirement. I’ve felt your pain myself and refuse to design systems that inflict that pain on others :)
- fermienrico 7y agoYou're a gem in the embedded world of almost pure coal and dirt mixture. I also want to stab embedded developers with a pin header if they ever try to use a touch screen. About the only place a touch screen makes sense and is provably better is your phone. Any other application of a touch screen needs to be eradicated from this planet.
- mirimir 7y agoHow about those Microsoft tabletop things?
- fermienrico 7y agoNo, your hands are gonna get tired after about 3 mins of using surface. All these futuristic videos showing what the future entails - everyone using a touch screen or a gesture - is ergonomically aggregious and completely out of touch(no pun) with reality.
- mirimir 7y agoIt'd be cool to touch virtual objects, no?
- defterGoose 7y agoOnly with some sort of approximately-tactile feedback. Some VR systems fall completely short of this (most dataglove type devices) while other "cruder" ones (like console controllers) actually do a better job because interfaces like buttons and triggers are analogous to many real world sensations.
- anitil 7y agoMy other pet peeve is in-band communication without escape codes. Oh, the radio connected you so now you're talking to the other end. Oh, the link got dropped so now you're talking to the radio itself. What could have been a simple search-for-sequence filter now becomes a best-guess filter. Gaaaah makes my blood boil even 5 years later. Honestly after my experience in firmware and manufacturing I'm amazed anything every works
- OJFord 7y agoI graduated EE with ('understanding' but) bafflement that radio works. Like just plain old amplitude or frequency modulated radio. Madness. I work with software now/currently. I'd be surprised it all works if only it wasn't so frequently clear that it doesn't! I suppose the idea of updates has been quite quickly ingrained in the consumer mind - software bugs are somehow more acceptable, seen as just 'to be fixed' rather than 'broken' or 'poorly made', 'not very robust'.
- da_chicken 7y agoHey, it's Goodhart's Law! "When a measure becomes a good target, it ceases to be a good measure." https://www.sketchplanations.com/image/167369765942 https://www.sketchplanations.com/image/167369765942
- rrss 7y agoSee also Chapter 29 of Hamming's "The Art of Doing Science and Engineering": http://worrydream.com/refs/Hamming-TheArtOfDoingScienceAndEngineering.pdf http://worrydream.com/refs/Hamming-TheArtOfDoingScienceAndEn... You get what you measure.
- philwelch 7y agoAs they say, in the mneomic that I use to remember Goodhart’s Law, you end up getting that measure “good and hard”.
- amluto 7y agoWas having a relay to power cycle the radio an option?
- throwaway894345 7y agoNope, unfortunately it was not. :(
- throwaway19211 7y agoIf you still work at John Deere all of your customers in the UK would love it if you could improve the anti-theft systems in the Greenstar units. It's becoming an epidemic, I've personally had 2 stolen, and know of many others, if you forget to take them out of the cab for one night they're gone. We believe they are being stolen to order by perhaps an organised group here. Please take a look at this forum: https://thefarmingforum.co.uk/index.php?threads/greenstar-units-stolen-from-e-dorset.288646/ https://thefarmingforum.co.uk/index.php?threads/greenstar-un...
- throwaway894345 7y agoI’m terribly sorry to hear that. Unfortunately I don’t work there any longer. I sincerely hope they get this issue resolved; this is awful.
- kabdib 7y ago> There was a bunch of dead code buried that was only executed > by the tests, apparently to bump up their unit test coverage. I've seen this trick used before; puff up the code base with just-gotta-work type filler (e.g., adding layers of abstraction and tons of parameter checking and re-checking) in order to hit some code-coverage metric. I mean, who's going to argue about a layer of abstraction, it's an automatic good thing, right? And parameter checking is what separates us from the animals! Encountering code like this is usually a Bad Sign.
- paypalcust83 7y agoNice. I worked on Trimble packet radios and other products that shared the firmware codebase. Autonomous steering and "TCAS for vehicles" of JD, Cat and Case equipment had working prototypes in 2000. Back then, horizontal blade angle was doable using kinematic GPS with antennas on each end of the blade.