Mindboards

There is a bug with BricxCC Project Manager, it does not include with relative paths. Technically, this is just a "not yet implemented" feature rather than a bug. I would recommend for the time being just keeping all your source files in the same folder as the library files, though you do...

It is not clear to me which API function you are testing, RotateMotor or RotateMotorNoWait. The best thing to do is try to get the low level routines working. Try OutputStepSyncEx with one motor. It should return false now, no motors turning, no crashing. Try OutputStepSyncEx with three or more moto...

Try these changes: void RotateMotorNoWaitEx(byte Outputs, char Speed, int Angle, short Turn, bool Sync, bool Stop) { if (Sync) { byte Layer, tmpOuts; tmpOuts = Outputs; DecodeOutputs(&tmpOuts, &Layer); if (tmpOuts == OUT_AB || tmpOuts == OUT_AC || tmpOuts == OUT_AD || tmpOuts == OUT_BC || tm...

* opOUTPUT_STEP_SYNC: Runs two motors regulated and syncronized, duration as specified by tacho cnts * opOUTPUT_TIME_SYNC: Runs two motors regulated and syncronized, duration as specified by time Hmmm. It does look like d_pwm.c expects that these two opcodes are only used with multiple motors. * op...

I tested the same thing with RotateMotorNoWaitEx, and again, it works with OUT_AB but doesn't with OUT_A. RobotcxCC only bundles the tools for communicating with the ev3, right? Because than codesourcery just compiles to native linux opcode which runs on the brick's OS - I boot it with the standard...

So I am very curious how RotateMotorNoWait works or does not work. It does not wait until the motors finish their rotation so an additional wait after the call would be appropriate. Here's the very simple code for RotateMotor: void RotateMotorEx(byte Outputs, char Speed, int Angle, short Turn, bool ...

What is not clear to me is what environment are you guys using to execute your code? Are you running with the VM shut down? In order to properly diagnose problems of this sort it is crucial to know every detail, no matter how trivial you may think it is. I can tell you, for certain, that if you are ...

The NXT and EV3 large motors are both detected as TYPE_NEWTACHO, iirc.

John Hansen

The logic is as shown below. Perhaps the value of Value5Float can be affected by batter voltage levels? Do you see different results with nearly dead batteries vs brand new alkaline batteries? if (OutputPort[Port].Value5Float < OUT5_BALANCE_LOW) { if (OutputPort[Port].Value5Float > OUT5_MINITACHO_HI...

If I get sufficiently motivated then all of the API layer will be completed and documented but at the moment I am feeling very unmotivated. Regarding 1, I hid it in a file named after the NXT Command module, i.e., ev3_command.c.h. I didn't think it fit anywhere else. That is where you find Wait in t...