tl;dr
You made a bunch of noob errors because you suck at electronics right now.
Full answer
Conceptually you had Conceptually everything was set up correctly, but you made a lotnumber of basic mistakes that causedaffected the signal to go fubar. Here is the setup youset-up which should usebe used to record the signal from one of the encoder outputs:
If youA set it up exactlylike this way, without any errors, you should getresult in a a clean signal if your motor/encoder is not broken. Once it's up and running, seeing the signal is simple. It's as easy as checking the square wave coming off of any common function generator: fiddle with your oscilloscope until it looks good (or just hit autoset and any good oscilloscope will do it for you, or read the excellent post by Chuck for more help on thatread the excellent answer by Chuck for more help on that).
YourThe underlying problems seemedseem to stem from an accumulation of rust when it comes to dealing with real, wire and breadboard, electronics projects:
- You forgot that theThe top/bottom of the breadboard power rails are typically separated, assumingso you cannot assume continuity between them. Always keep a multimeter handy and do simple continuity tests before doing more esotericdeeper troubleshooting. When stuff's busted, never assume continuity. Test for continuity.
- The fact that the green wire from theBe careful not to confuse motor is ground confused you, and you swapped your connections to the green and blue jacks (encoder Gnd andwith encoder Vcc) on the motorground, so this trashed your signal. Checking that your wires are connected correctly is pretty much the electronics equivalent of "Is your computer plugged in?". Just like you should always make sure your computermotor ground is plugged in and turned on, in the world of circuitslikely to be electrically very noisy, always make surem which will corrupt your wires are attached in the correct spots (especially if you are prone to get disoriented when using non-black ground wires)encoder signal.