Follow Slashdot stories on Twitter


Forgot your password?
Slashdot Deals: Deal of the Day - Pay What You Want for the Learn to Code Bundle, includes AngularJS, Python, HTML5, Ruby, and more. ×

Comment Re:Faster? BECAUSE THEY DON'T RUCKING TEST IT! (Score 1) 65

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?! :)

Comment Re:I know a lot of this is cutting edge... (Score 1) 41

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)

Comment Re:Seriously? (Score 2) 366

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! :-)

Comment Self driving babies and kids (Score 3, Interesting) 408

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.

Comment likely just RF coupling to broadband RF (Score -1) 192

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)!



Comment Re:Computer Missues Act 1990 (Score 1) 572

Similar thing with other clones - the bluetooth mac is the most duplicated. there's a valid-looking one (which has basically been used /everywhere/ for that paticular bluetooth module

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 :-)

Comment Re: Computer Missues Act 1990 (Score 1) 572

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)

Comment Re:Computer Missues Act 1990 (Score 1) 572

You mean the USB ID was reset to un-allocated because the non-ftdi chip was using a licensed PID that it had no right to.

The devices were not damaged, they still work - they have no driver. This would be the case even if FTDI didn't change the ID, and simply refused to work. You would be in *exactly* the same situation with a device you could no longer talk to as you have no driver.

Get a driver for the device, and it'll work. Won't be an FTDI driver though.

Comment Re:Computer Missues Act 1990 (Score 1) 572

They didn't break chips though - they simply moved them off their USB id.

All you need to do is get new drivers for the USB ID of 0. then things will work again. The clone chip isn't ever going to work with FTDI's drivers though, so you're going to need the clone chip manufacturer to release drivers for their device (instead of using FTDI's which they had no agreement to use)

Linux sorted this out in a patch pretty quick. their ftdi driver works with those devices now, so all you'd need to do is release and pay for a driver to be sent out over windows update.

"People should have access to the data which you have about them. There should be a process for them to challenge any inaccuracies." -- Arthur Miller