I've run into a bug where the EV3 will not play a sound with any of the sound producing functions. Below is the one of the codes that I am using. All it should do is play a scale, then increase each note in the array by an octave then play the scale again. This code was working in the NXT environment and I believe that I changed everything that I need to to get the code to work with the EV3.

EDIT: Code removed because it is a solution to a Lab assignment.

Thank you for you help and time,

Zack

Last edited by Zack on Wed May 14, 2014 9:46 am, edited 1 time in total.

Does anyone know if the Breakpoints in the IDE are suppose to work? I see that I can add them, and compile them, but when I go to put the program on the EV3 it says that the EV3 is no longer connected and then the EV3 is frozen.

Does anyone know if the Breakpoints in the IDE are suppose to work? I see that I can add them, and compile them, but when I go to put the program on the EV3 it says that the EV3 is no longer connected and then the EV3 is frozen.

Don't know if there's a new thread for 4.10 but I encounterd a problem with the IR-sensor in SEEK-mode. No mather what mode I select in 'Motor en Sensor setup' it keeps working in Proximity mode. When I use setSensorMode in my code it only works once in SEEK mode (using SensorValue). The next time when I call SensorValue it turns back to Proximity mode. To test it I use this simple code (toggle comment on lines with setSensorMode statement to see difference in values written to debug window):

Is it just me or is the color detection sample program has an odd behavior?

First time I start the BasicColorDetection.c program, runs fine.Second time : the color mode changes for some reason and doesn't return the right valuesThird time : runs fineFourth time : color mode changes again.etc.

I tested the same program with the color sensor (Basic_Color_Detection.c) and encountered the same problem. The sensor switches between color-mode and reflected-mode. In fact, it is the same problem I mentioned earlier in my post about the IR-sensor. There too, the sensor switches between two modes each time you stop and start the program, in this case the proximity-mode and seek-mode. I didn't test it yet, but I can imagine the same effect happens with all sensors right now. A work-around at the moment is to explicitly set the right mode for the sensor each time you read the value of the sensor by using SetSensorMode. Meanwhile I hope this bug (or whatever it is) is removed in the next beta .

Who is online

Users browsing this forum: No registered users and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum