search

BrianPeek / legoev3

LEGO MINDSTORMS EV3 API for .NET
Apache License 2.0
137 stars 72 forks source link

EV3 moves a little then later commands get lost #8

Open typemismatch opened 9 years ago

typemismatch commented 9 years ago

I have firmware 1.07H - I'm running the Desktop code on OS X.

I have the blue tooth pairing working and on the EV3 the iPhone/iPod/iPad is off.

When I send a command it goes through the first time, EV3 moves + plays sound. If I try again I get random behavior. Sometime it will move again, sometimes it moves a different motor (same code). Most times after it has moved around a bit, it ignores all future commands and requires a reboot.

I modified the tester to Disconnect after each run, batch seemed to work a little better.

Any thoughts? thanks

BrianPeek commented 9 years ago

I can't say this has ever been tested on OS X so I'm not sure where to begin with troubleshooting. Are you using network communication or something else?

typemismatch commented 9 years ago

I was trying to get it working over BlueTooth - really odd because it seems to want to work but it seems after the initial packet is sent it doesn't accept anymore. No big deal, it's a far out case :)

BrianPeek commented 9 years ago

A bit of a far out case, yes. :) Maybe mess around with the WriteBufferSize property on SerialPort?

FabioCZ commented 8 years ago

@typemismatch I just got my brick (v1.07H) set up on OS X 10.11 (Late 2013 rMBP 15"), Mono 4.0.5, and everything seems to be working ok (well, other than it occasionally doesn't want to connect to the brick, but if it connects, it works).

typemismatch commented 8 years ago

hey @FabioCZ good to know, I'll send you a pm and see what else I might have missed, thanks.

andiikaa commented 8 years ago

Hey, have you fixed the problem? We´ve ported this sdk to a native swift implementation for iOS but also have problems with the bluetooth connection. It seems, if direct commands are send one by one, the bluetooth stops working or the robot has some strange behavior. Our solution at the moment, is to wait a few milliseconds till we send the next command.