Permanent pressure on the steering wheel then
Permanent pressure on the steering wheel then
Maps aren't going to solve your 'pseudo' problem. The ability for the self driving car to ask questions however, is.
I have had plenty of taxi journeys to obscure places where the cabbie has asked wtf are we going, even in my home town. It's not unusual to ask, and being able to reply will help loads.
Add mapping to that and it should be a bonus on knowing where to go. The article makes it that databases should be queryable for anything, and that's not practically possible. Asking questions back is, and generally gets you places (please excuse the pun). any system that can do this is basically going to earn the $$$$
Not bugs - if their adapters start sending random crap over CANBUS, what can I do?
If their adapter dont work ok J1850-PWM (what fords use for the diagnostic bus) what can I do? people instinctively blame the app, rate it bad or (in the best case where I can reply) send an email.
The hardware they copy is buggy, it's well known (ok you may have to search a bit for 'clone ELM237 buggy J1850' etc, but you'll get there if you dig)
The software has been made to work with the buggy adapters, but there's only so much you can do. If you send '0100' and the adpater goes '0102' to the ECU, wtf can I do?!
Heh, that's actually a good one that I had completely missed! I haven't a clue about how much fallout there would be, or if it was spread over a wide enough area (hopefully due to pieces burning up) if the residual would be enough to worry about!
Many more pieces, with a lot more surface area to:
1) burn up with.
2) decelerate with.
One big problem becomes less significant the smaller it gets.
It's not the first time they've had problems with chutes either, however this is the biggest one they've done so far, and things don't always scale up (you need thicker fabric, etc to handle larger stresses)
From the limited video footage, the chute looked to be already torn at deployment, so it may have been doomed to fail well before it opened (though NASA have had tearing problems before, one wonders if they had built anything in to mitigate that known risk into the design)
(*i am not an expert, just an average thickie)
Unfortunately you can't trust electronics in space (see the other headlining article about cubesats rebooting from stray particles every 6 weeks).
One of those particles hits your flash chip, given the size the dies are now, then it's going to effect a large number of cells potentially and corrupt the filesystem quite badly.
Electronics in space have to be uber radiation resistant, this is why it's still 100MHz (etc) stuff that's being used and not the latest GHz stuff, because, reliability in an adverse environment!
You appear to be both wrong.
This is all well and good having self driving cars, however, (ok, so this is through reading the unfortunate things that happen to people through stupidity, and malice on reddit, liveleak, etc)....
Hopefully we'll never get to the stage where you just 'pop the infant' into the car and tell it to go to grandmas (assuming grandma is there, and nothing happens along the way). Sad, far fetched, but you can bet that this will happen somewhere and some unfortunate may be hurt as a result in something entirely preventable).
This was a waking dream this morning. Sad thing to wake up to. Hopefully never happen.
I'm sure someone has already mentioned this (and I tried posting on the RPi forum but it's having a 'senior' moment)
This is likely just RF overload.
Stick some foil over the RAM and CPU (and voltage reg) and see if things improve - you mentioned flipping the board over so I would imagine that RF (Radio Frequency) is the culprit (as the xenon flash is basically a wideband (all frequencies) radio transmitter). That close is probably going to couple with some squiggly bit of the silicon and do 'interesting things'
Very interested to see if the foil improves things (alu tape would be a good start)!
'Design' would have curved the screen so it fit more comfortably. In their website you can see in the pictures just how awkwardly it sits on the wrist. A bit of a let-down to be honest.
Similar thing with other clones - the bluetooth mac is the most duplicated. there's a valid-looking one (which has basically been used
The re-pairing issue may be an android/bluetooth as well as a combination with the adapter (or it may have been worked around in later versions of android) I'm not sure. Again, it's another headache that developers have to deal with
That right there, you nailed it.
But the USB PIDs are explicitly licensed, so does that not negate it in this instance?
It is, and it is evidently not working in this instance, is it as FTDI would have already pursued this (and the costs would likely have been prohibitive for little recompense).
Some people have looked at the driver and it writes the EEPROM for every device (I am told). Clone chips apparently are broken by this. Malicious or not, they shouldn't have been using FTDI's driver (they have had every opportunity to have written their own and even use their own device IDs, or license from FTDI properly)
It is masked but always present. I don't know who built to it. It came before the first kernel.