[PD] pduino/comport w/ arduino freezes keyboard and trackpad on Macbook
Hans-Christoph Steiner
hans at eds.org
Thu Oct 19 02:19:16 CEST 2006
That sounds more like a driver bug then. Try updating the driver:
http://ftdichip.com
A short circuit in the board itself is possible, so it'd been worth
inspecting the board. But if it only happens with the /dev/cu.*
devices, its most likely a driver bug. The "cu" interface is old and
deprecated anyway.
.hc
On Oct 18, 2006, at 11:14 AM, David NG McCallum wrote:
> I think I made the mistake of mentioning several setups in the same
> e-mail.
>
> What I should say is that when *nothing* is plugged into the arduino,
> I still get the lockup.
>
> Curiously enough, it freezes when I select the "cu.usbserial-XXX"
> devicename (the one that the arduino software itself uses), but not
> when I select "tty.usbserial-XXX".
>
> I assume this has something to do with the problem...
>
> Thanks for the suggestions!
>
> D
>
> On 18/10/06, Hans-Christoph Steiner <hans at eds.org> wrote:
>>
>> The arduino draws very little power, probably less than 100mA, any
>> USB bus should power it fine. A short circuit will shutdown any USB
>> bus. It could shutdown a poorly implemented USB bus forever.
>>
>> The problem you describe sounds a lot like an intermittent short
>> circuit to me. It could also be the motor drawing too much current
>> under certain conditions. If running a motor, I'd run an external
>> power supply.
>>
>> .hc
>>
>> On Oct 16, 2006, at 10:59 PM, David NG McCallum wrote:
>>
>> > Drawing too much power might have had something to do with a
>> motor I
>> > was running. But I had no problem with the motor using my own
>> arduino
>> > code.
>> >
>> > The situation with mis-wiring the pot was independent of the
>> comport
>> > object freezing my kbd and mouse, though. The kbd and mouse
>> froze when
>> > everything was wired up fine (which worked w/ my own arduino code,
>> > just not with comport).
>> >
>> > It's now mysteriously worked, the last time I tried it, but the
>> wiring
>> > was all the same as before. So I have no idea, now that it's not
>> > really reproducible...
>> >
>> > D
>> >
>> > On 16/10/06, nick weldin <nick at padarts.idps.co.uk> wrote:
>> >>
>> >> If drawing to much power from the usb socket is the problem
>> then you
>> >> need to provide power for the arduino either by going through a
>> >> powered hub, or if you are drawing to much power on the arduino to
>> >> run it off usb switch the power jumper over on the board and
>> provide
>> >> power for the electronics on it seperately, rather than drawing it
>> >> from the usb bus.
>> >>
>> >> HTH
>> >>
>> >> Nick
>> >>
>> >> >Hi HC,
>> >> >
>> >> >I've had the problem of the USB bus being killed because to much
>> >> power
>> >> >was drawn, but it was because I plugged a pot into the wrong
>> ports.
>> >> ...snip...
>> >> PD-list at iem.at
>> >>
>> >> _______________________________________________
>> >> PD-list at iem.at mailing list
>> >> UNSUBSCRIBE and account-management -> http://lists.puredata.info/
>> >> listinfo/pd-list
>> >>
>> >
>> >
>> > --
>> > __ _ _ _ __ _
>> > http://sintheta.org
>> >
>> > _______________________________________________
>> > PD-list at iem.at mailing list
>> > UNSUBSCRIBE and account-management -> http://lists.puredata.info/
>> > listinfo/pd-list
>>
>>
>> ---------------------------------------------------------------------
>> ---
>>
>> Man has survived hitherto because he was too ignorant to know how to
>> realize his wishes. Now that he can realize them, he must either
>> change them, or perish. -William Carlos Williams
>>
>>
>>
>
>
> --
> __ _ _ _ __ _
> http://sintheta.org
------------------------------------------------------------------------
¡El pueblo unido jamás será vencido!
More information about the Pd-list
mailing list