Ethernet VS tutorials

arduino.cc has a lot of tutorials!

I was gonna say the arduino.cc site but that works too.

When you write your code and compile it, what environment are you doing it in? Are you using an online cloud service like arduino.cc's IoT cloud? Or have you downloaded and installed the Arduino IDE application from arduino.cc's software download page?

There are tons of libraries for the Arduino platform that people have written and there are many available for use with this module, so you don't have to do any super heavy lifting programming-wise. In the Arduino IDE you can download from arduino.cc I installed a couple of libraries just now as a test. The reason I installed them is because almost every library comes with several short example programs showing how to use the various features that their library offers.

Did all of it make sense? Could you do the projects he shows by yourself without starting and stopping the video? That might show areas that you would want to brush up on. Another great idea is to go through all of the commands on the arduino.cc language reference page. Make sure you instinctively understand what each function listed does and experiment with any that you aren't familiar with.

There are also IoT cloud style dashboards at places like arduino.cc that let you add various widgets for dials and controls to represent the data you have locally with your Arduino.

Mentioned at arduino.cc. Designed to generate a periodic interrupt, I'll have to code a little state machine to change the interval at every firing.

Without a good explanation from them I really wouldn't put much stock in it. If anything they're probably just trying to steer people away from CH340 devices in part because they are problem children and because arduino.cc themselves don't use them.

Ontop of this, step 3 and 5 are a must in learning. And don't think "it's just blinking, lame" think more of "what can I do with this?" Use arduino.cc for reference.

// See https://github.com/arduino/tutorials/blob/master/ArduinoZeroMidi/PitchToNote.h

#include "MIDIUSB.h" const byte TOTAL_BUTTONS = 16; // All the Arduino pins used for buttons, in order. const byte BUTTONS_PIN[TOTAL_BUTTONS] = {2,3,4,5,6,7,8,9,10,11,12,A0,A1,A2,A3,A4}; // Every pitch corresponding to every Arduino pin. Each note has an associated numeric pitch (frequency scale). // See https://github.com/arduino/tutorials/blob/master/ArduinoZeroMidi/PitchToNote.h const byte BUTTONS_PITCH[TOTAL_BUTTONS] = {36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51}; // Current state of the pressed buttons. byte currentRead[TOTAL_BUTTONS]; // Temporary input reads to check against current state. byte tempRead; // The setup function runs once when you press reset or power the board void setup() { // Initialize all the pins as a pull-up input. for (byte i = 0; i < TOTAL_BUTTONS; i++) { pinMode(BUTTONS_PIN[i], INPUT_PULLUP); } } // The loop function runs over and over again forever void loop() { for (byte i = 0; i < TOTAL_BUTTONS; i++) { // Get the digital state from the button pin. // In pull-up inputs the button logic is inverted (HIGH is not pressed, LOW is pressed). byte buttonState = digitalRead(BUTTONS_PIN[i]); // Temporarily store the digital state. tempRead = buttonState; // Continue only if the last state is different to the current state. if (currentRead[i] != tempRead) { // See https://www.arduino.cc/en/pmwiki.php?n=Tutorial/Debounce delay(2); // Get the pitch mapped to the pressed button. byte pitch = BUTTONS_PITCH[i]; // Save the new input state. currentRead[i] = tempRead; // Execute note on or noted off depending on the button state. if (buttonState == LOW) { noteOn(pitch); } else { noteOff(pitch); } } } } void noteOn(byte pitch) { MidiUSB.sendMIDI({0x09, 0x90, pitch, 127}); MidiUSB.flush(); } void noteOff(byte pitch) { MidiUSB.sendMIDI({0x08, 0x80, pitch, 0}); MidiUSB.flush(); }