New answers tagged ev3
I could not find this in the help file, but according to this thread "Another little known characteristic of MyBlocks is that they aren't re-entrant. No two copies of the same MyBlock can be running at the same time." I tried a few simple programs in EV3-G and confirmed that this is true. The order in which they run appears to be random.
First answer is google: FLL EV3 PDF EV3 and PDF are obvious. FLL is short for FIRST Lego League, which may or may not be for "playing field style robots". Clinics for coaches and kids at HighTechKids.org use FLL Programming 101 as a starting point. The EV3 is new enough, that some of the best programming advice for FLL is directed at the NXT.
You can consider this the "official" answer based on the EV3 firmware source code. This file is used for scaling the values that you see in "Port View" on the EV3 brick itself. The NXT Light Sensor is defined in these two lines: 2 0 NXT-REFLECT 1 1 3 0 2 119 0x32 3372.0 445.0 0 100 0.0 100.0 20 0 pct 2 1 NXT-AMBIENT 1 1 3 0 2 119 0x30 3411.0 633.0 0 100 ...
Code is works as the robot is behaving. The problem is that the first block is a sensor block, which is processed in the blink of an eye. The second block moves forward for 2 rotations at 50% power. So long as only one sensor is being watched, a wait for block is sufficient. Here is an example:
Are you sure that the button is being completely pressed? A quick test would be to hold the robot and manually press the touch sensor. If the wheels start turning backwards, then there isn't anything wrong, you just need to make sure the button gets pressed completely. If you're sure the button is being pressed, then it's probably a software problem. It ...
Making the assumption here that by analog, you mean something more fine-grained than just the 6 or 7 colors. Both the NXT and EV3 color sensors have the capability of reading the individual color components. The value read is not a voltage, but just a "percent" of reflected light of each color. For NXT-G, you can find a block here (the Color Range Block). ...
The NXT works fine with EV3 motors, and will read them as NXT motors. EV3 sensors, on the other hand, do not natively work with the NXT, with the exception of the touch sensor. The reason for this is that, touch sensor notwithstanding, EV3 sensors use a hardware communication protocol called UART, which is not supported by the NXT. The NXT only supports ...
Yes, it is possible to pass the port number as a parameter to a sensor or motor block via data wire. It's just that it's manually selected by default. To change this, go to the port of the sensor or motor block, and select the top-most option which has the plug icon on it: It will then create a data port for which motor port you want to use: The same ...
No, EV3 MyBlocks cannot be recursive. If a MyBlock contains a copy of itself, then the following error will be produced upon compiling: For some reason, LEGO's programming software has become progressively less immediate about notifying you that this cannot be done. In EV3-G, it waits until compile to let you know that you can't do this. In NXT-G (the ...
Copied from Github: I haven't heard of anyone using a microphone yet, but you have a couple of options. 1) a USB sound card/microphone or 2) Bluetooth headset/hands-free device. The built-in speaker uses an alsa sound driver, so theoretically, it should work with any linux program. If you are looking at purchasing something USB, make sure it does not ...
Since you are a C# pro, I would recommend MonoBrick. I know they have a plugin for Xamarin Studio/MonoDevelop that lets you do remote debugging. Not sure if they have one for Visual Studio yet.
Top 50 recent answers are included