?Is there a way to test whether someone has done these steps correctly before moving on? I think that would help and it also might be good to put that information in a question for passing the tutorial.
Give the US frequency, 900 odd MHz. Don't leave the reader to intrepret was CS and RST pins are. It is always good to spell out acronyms the first time like IoT or SPI. It would be good to link to a short description of SPI as well. Or you could copy over the blocks from the SD card tutorial.
I believe we have a Google drive space for the MakerE which is publicly accessible. For longer code it might make sense to link to a .txt file there. Or even better we can set up a Github site for all the code.
If we can make the challenge more specific we can write a quiz at the end. For example what value is set when the phototransistor is covered up? Maybe there are some other things that can only be learned by completing the tutorial or challenge.
Having a link or more instructions for step #2 would be good. I would get tripped on on that one. It would also help in one of the earlier steps at the beginning to outline what someone is going to be doing. I am sort of learning the goal as I go along and it helps to have that clear at the start.
It might be good to make this more of a test that that have to complete to show they did this succesfully.
?Is there a way to test whether someone has done these steps correctly before moving on? I think that would help and it also might be good to put that information in a question for passing the tutorial.
Give the US frequency, 900 odd MHz. Don't leave the reader to intrepret was CS and RST pins are. It is always good to spell out acronyms the first time like IoT or SPI. It would be good to link to a short description of SPI as well. Or you could copy over the blocks from the SD card tutorial.
It might be good to provide links to the other tutorials needed if they are not already linked up at the top - i.e. Feather and neopixel
I believe we have a Google drive space for the MakerE which is publicly accessible. For longer code it might make sense to link to a .txt file there. Or even better we can set up a Github site for all the code.
It is sort of weird to have the dev boards hanging off the edge of a breadboard Would it be possible to use a bigger breadboard so they fit?
If we can make the challenge more specific we can write a quiz at the end. For example what value is set when the phototransistor is covered up? Maybe there are some other things that can only be learned by completing the tutorial or challenge.
Can you give me some more details on how I can access the data after it is uploaded? Also remember to add some steps about checking account balance.
This step seems out of place. Should it be earlier before sending light level data?
Having a link or more instructions for step #2 would be good. I would get tripped on on that one. It would also help in one of the earlier steps at the beginning to outline what someone is going to be doing. I am sort of learning the goal as I go along and it helps to have that clear at the start.
Page 1 of 3
Next