Hey Juan! Sergey just let me know that he's currently working on an A/D tutorial - it takes us awhile to take his tutorials, prep for the videos, and then shoot and publish the videos, but it's in the process!
these were good videos.. I am glad people still use Assembly, it really helps to understand how the micro works and gives you an understanding of what's going on. I use C, but for really getting to know the chip, I use Assembly to play with the registers and understand how the internals work. I wouldn't want to do production in Assembly, but the teaching of a micro controller should ALWAYS start with Asm and getting to know the chip and what it can do. Thanks for the video, should do another round with chips that have some more peripherals on it. PIC16F or PIC18F series.. Thanks for the hard work and I subscribed as a thank you.
Thanks Mike, I appreciate the feedback! Before Sergey started in on these, I was most familiar with the PIC16F series with C, so this has been quite the learning experience for me as well. We're still trying to figure out what Sergey's next series will be on but it would be nice to be able to stretch our legs on something a bit more powerful and less restrictive.
@@CircuitBread Oshonsoft PIC IDE Simulator is an Awesome learning tool for Assembly, lots of information displayed and can even hookup virtual devices like LCD/LED/UART Term/Virtual Oscilliscope etc.. I am not advertising, but i use this tool a lot and it makes a great teaching tool and is not expensive at all. Well worth every penny. I think $33.00, but well worth the price for what you can do with it. Sorry.. I really like the tool and it beats hooking up a bunch of hardware to test things.
Hey Mike - thanks for the tip, I'd never heard of that simulator, I'll ask Sergey if he has. And I have fond memories of the 16F877A - I'm too embarrassed to go into details but when I was in the Navy, I created a motion alarm system that had wireless arming/disarming and would play "The Song of the Seabees" (I was a Seabee, so this makes sense) when it was triggered, based on the 877A. It was impressive when it worked, which wasn't very often.
@@CircuitBread That's something to be proud of.. Anything WE create is just plain fun, but when it works there is a satisfaction with that. You can say "I made that!" and be proud.. :)
With all due respect, this tutorial is so much easier than the PWM blip effect(part 7). I spent a whole day trying to grasp it. Then parsed it to C and completed it. It was around the same number of instructions, 33 vs 20 in assembly. I dont have an oscilloscope, so i can't see the graph. I will buy one sooner. Whats your name again sir? you never mentioned it in any videos. I learned a lot watching your videos as a newbie.
Yeah, the difficulty of the tutorials starts to vary quite a bit with these later tutorials. And sometimes the challenge is getting the physical aspect down (I don't know why I struggled/struggle so much getting the robots to work). But I think it's awesome how far you've come and hope you've also been reading Sergey's tutorial to get even more in-depth. Good luck moving forward with the rest of the tutorials! And my name is Josh 👋 I haven't been as good at answering questions recently but I'm hoping to get back into the groove soon. JB or Laren will sometimes answer comments on TH-cam as well but most responses are from me.
I'm trying to replicate this using 12f683. Up until this lesson everything worked fine. I'm using gpio 0 and 1 for LED and 2,3 for buttons, but all I get is both LEDs light up as soon as power mcu and stay lit, no reaction to button pressing. Are there any major differences between 12f683 and 10f200?
I haven't jumped into the details but I've found, when moving things from one similar MCU to another, that if there's a problem, it's almost always because there are other features assigned to a pin. I'd double check the pin assignments between the two and make sure that the 12F683 doesn't have additional roles for the pins in usage that need to be disabled before they can be used.
I Really like this tutorial on Microcontrollers. I am a newbee to microcontrollers and would really like to learn, However, I have a great knowledge in electronics and repairs.... With that in mind, I am repairing a piece of equipment that the PIC16F877A controller is faulty and I bought a replacement PIC16F877A and a PicKit 4 programmer and as I said I am new to microcontrollers and the Pickit4. Can you show me how to read the data off the old PIC16F877 and load it unto the new PIC controller using the picKit4 programmer so I can complete the repairs and send it off to the customer. The old PIC when you apply a little heat it work fine but once it cools off it does not work. I would really appreciate your help on this. Also do you have a learning channel on programming PIC/MCU on your website that I can access? Thanks for your intersting Videos.
We do go over the process of programming an MCU in other written and even video tutorials (using the IPE - Integrated Programming Environment). If you start at the beginning of this series, it should build the foundation you need to do this. In regards to pulling code off the old MCU and putting it in the new one, there are two things I should warn you about. 1) Many people put code locks on their MCUs when they go to production so that you can't do exactly what you intend to do. I'm certain there are ways around these code locks but I've never even delved into it, so if it is code locked, I'm sorry. 2) Even if you pull the code off, it will just be in a hex format, or something only a computer/MCU can read. If you want to make any changes to the code itself, it won't be given to you as assembly or C or anything you can easily make sense of.
Hi Patricia, that's an excellent question! But no, the signals coming from other devices are assumed to be clean enough that you don't need to clean them in any way.
HI, i wanna know if there is any way to connect this microcontroller to a bluetooth module so it can be connected to a mobile app. if its possible, how would you do it?
Hi Patricio! Yes, there is! Sergey has created a tutorial for doing exactly that, but we just haven't gotten it ready for publication yet. It builds on the UART tutorial which we have published on CircuitBread (www.circuitbread.com/tutorials/communicating-with-a-pc-using-uart---part-11-microcontroller-basics-pic10f200) but we haven't done the video for this UART one or published the written portion of the actual bluetooth one yet. We should be able to at least get the written bluetooth tutorial up on our website, it should be early next week.
We use the debounce routine to get rid of spurious signals and to also clean up the physical imperfections of all switches - where instead of a single switch from one state to another, it sometimes bounces a little bit between the states before settling on its new state.
Such a great video, it really helped me !
Asuka Supremacy
@@ryotakeshi6680 ok boomer
I am so confused...
I really like your tutorials. Keep them coming. Looking forword to a A/D tutorial based on PIC10F200. ;) Good work!
Hey Juan! Sergey just let me know that he's currently working on an A/D tutorial - it takes us awhile to take his tutorials, prep for the videos, and then shoot and publish the videos, but it's in the process!
these were good videos.. I am glad people still use Assembly, it really helps to understand how the micro works and gives you an understanding of what's going on. I use C, but for really getting to know the chip, I use Assembly to play with the registers and understand how the internals work. I wouldn't want to do production in Assembly, but the teaching of a micro controller should ALWAYS start with Asm and getting to know the chip and what it can do. Thanks for the video, should do another round with chips that have some more peripherals on it. PIC16F or PIC18F series.. Thanks for the hard work and I subscribed as a thank you.
Thanks Mike, I appreciate the feedback! Before Sergey started in on these, I was most familiar with the PIC16F series with C, so this has been quite the learning experience for me as well. We're still trying to figure out what Sergey's next series will be on but it would be nice to be able to stretch our legs on something a bit more powerful and less restrictive.
@@CircuitBread PIC16F877A is better yet not too complicated. A lot of people use it in their tutorials, if that is any help..
@@CircuitBread Oshonsoft PIC IDE Simulator is an Awesome learning tool for Assembly, lots of information displayed and can even hookup virtual devices like LCD/LED/UART Term/Virtual Oscilliscope etc.. I am not advertising, but i use this tool a lot and it makes a great teaching tool and is not expensive at all. Well worth every penny. I think $33.00, but well worth the price for what you can do with it. Sorry.. I really like the tool and it beats hooking up a bunch of hardware to test things.
Hey Mike - thanks for the tip, I'd never heard of that simulator, I'll ask Sergey if he has. And I have fond memories of the 16F877A - I'm too embarrassed to go into details but when I was in the Navy, I created a motion alarm system that had wireless arming/disarming and would play "The Song of the Seabees" (I was a Seabee, so this makes sense) when it was triggered, based on the 877A. It was impressive when it worked, which wasn't very often.
@@CircuitBread That's something to be proud of.. Anything WE create is just plain fun, but when it works there is a satisfaction with that. You can say "I made that!" and be proud.. :)
With all due respect, this tutorial is so much easier than the PWM blip effect(part 7). I spent a whole day trying to grasp it. Then parsed it to C and completed it. It was around the same number of instructions, 33 vs 20 in assembly. I dont have an oscilloscope, so i can't see the graph. I will buy one sooner.
Whats your name again sir? you never mentioned it in any videos. I learned a lot watching your videos as a newbie.
Yeah, the difficulty of the tutorials starts to vary quite a bit with these later tutorials. And sometimes the challenge is getting the physical aspect down (I don't know why I struggled/struggle so much getting the robots to work). But I think it's awesome how far you've come and hope you've also been reading Sergey's tutorial to get even more in-depth. Good luck moving forward with the rest of the tutorials!
And my name is Josh 👋 I haven't been as good at answering questions recently but I'm hoping to get back into the groove soon. JB or Laren will sometimes answer comments on TH-cam as well but most responses are from me.
I'm trying to replicate this using 12f683. Up until this lesson everything worked fine. I'm using gpio 0 and 1 for LED and 2,3 for buttons, but all I get is both LEDs light up as soon as power mcu and stay lit, no reaction to button pressing. Are there any major differences between 12f683 and 10f200?
I haven't jumped into the details but I've found, when moving things from one similar MCU to another, that if there's a problem, it's almost always because there are other features assigned to a pin. I'd double check the pin assignments between the two and make sure that the 12F683 doesn't have additional roles for the pins in usage that need to be disabled before they can be used.
I Really like this tutorial on Microcontrollers. I am a newbee to microcontrollers and would really like to learn, However, I have a great knowledge in electronics and repairs.... With that in mind, I am repairing a piece of equipment that the PIC16F877A controller is faulty and I bought a replacement PIC16F877A and a PicKit 4 programmer and as I said I am new to microcontrollers and the Pickit4. Can you show me how to read the data off the old PIC16F877 and load it unto the new PIC controller using the picKit4 programmer so I can complete the repairs and send it off to the customer. The old PIC when you apply a little heat it work fine but once it cools off it does not work. I would really appreciate your help on this. Also do you have a learning channel on programming PIC/MCU on your website that I can access? Thanks for your intersting Videos.
We do go over the process of programming an MCU in other written and even video tutorials (using the IPE - Integrated Programming Environment). If you start at the beginning of this series, it should build the foundation you need to do this.
In regards to pulling code off the old MCU and putting it in the new one, there are two things I should warn you about. 1) Many people put code locks on their MCUs when they go to production so that you can't do exactly what you intend to do. I'm certain there are ways around these code locks but I've never even delved into it, so if it is code locked, I'm sorry. 2) Even if you pull the code off, it will just be in a hex format, or something only a computer/MCU can read. If you want to make any changes to the code itself, it won't be given to you as assembly or C or anything you can easily make sense of.
Mr Circuit bread, do we need the Debounce software when PIC microcontroller interfaces with other digital TTL CMOS devices.
Hi Patricia, that's an excellent question! But no, the signals coming from other devices are assumed to be clean enough that you don't need to clean them in any way.
@@CircuitBread thanks
HI, i wanna know if there is any way to connect this microcontroller to a bluetooth module so it can be connected to a mobile app. if its possible, how would you do it?
Hi Patricio! Yes, there is! Sergey has created a tutorial for doing exactly that, but we just haven't gotten it ready for publication yet. It builds on the UART tutorial which we have published on CircuitBread (www.circuitbread.com/tutorials/communicating-with-a-pc-using-uart---part-11-microcontroller-basics-pic10f200) but we haven't done the video for this UART one or published the written portion of the actual bluetooth one yet. We should be able to at least get the written bluetooth tutorial up on our website, it should be early next week.
Is that tactile switch
Yes it is!
Why denounce routine how to use it as a regular press
We use the debounce routine to get rid of spurious signals and to also clean up the physical imperfections of all switches - where instead of a single switch from one state to another, it sometimes bounces a little bit between the states before settling on its new state.
Good to know that thanks
Hmmmm…bush?