This exercise asks students to troubleshoot a program to get LED controls and buzzer controls working. I feel like it is either really challenging or so simple I’m overthinking it. Any help or suggestions on how to help students (and me) get through this one?
I think you might be over thinking it, lol.
Are you able to view the exemplar in the teacher panel?
Thanks. I kind of thought that. I’ve been trying to troubleshoot comparing the blocky code, but I think I need to switch over the text and go through it again. I’m assuming it’s just a few little things that I am missing.
If you’ve been changing the code, it’s possible that you’ve accidentally introduced new, more difficult bugs. You might try clearing your version history to start from the beginning again.
I’ll try that. Thank you for the suggestion.
This is my first year through the curriculum, so it’s been a learning experience for me as much as for the students.
It seems to me that for this unit there is an issue with labels. It states short for the buzzer but when I click the buzzer keeps sounding without a pause and when I move the slider to long, the buzzer beeps. When the terms long and short are used, do they apply to the buzzer or the pause?
Great question - I’m confused as well, I printed to the console log to see what the values are and the “duration” variable is less when towards the “short” label, and higher value towards the “long” label.
I’ll pass this on and we’ll hopefully get an explanation soon.
I’m not sure what’s happening because my board gives a short beep when I move the slider to short and a long been when I move the slider to long. Have you made any changes to the code? Can you remix what you have and post it?
Also, what OS/browser combination are you using?
I was testing the Example Solution after I noticed the same thing was happening with the students and the result was opposite of the labels. I am using PC’s with Windows 7 and Google Chrome.
Although sometimes regular Chrome will work with the Circuit Playground API, Chrome itself doesn’t actually support the tools that it needs to connect anymore, so we suggest that everyone who is on a Windows or Mac machine to use the Maker App, as is described here: https://studio.code.org/maker/setup.
Unfortunately, Chrome changed what it supported after we had already developed the curriculum, which is why we needed to make the standalone app.
We are using the maker app as I was instructed to do in the training. All of the computers in the lab have the maker app installed and I am using it to test the Example and student code.
Sorry Myra, but just to be clear, when you were running this app, you were NOT using the Chrome browser to access Code Studio. You were instead using the Maker App as your browser?
If that’s what you are saying, then can you submit this as a bug? I will check with the engineering team and let them know that you are having this issue.
I am using the app as I was instructed to install on all of the lab computers.
Hi Myra, were you able to put in a bug report? Or was your problem solved? It might be helpful if you could send a screenshot of what the broken Example Solution looks like in the Maker App, with the entire app shown, even the toolbars at the top.
I will get to it tomorrow. I am in the middle of eSports tournament and APs.