LCD Code Improvements 🔴 PIC Microcontroller Programming Tutorial #24 MPLAB in C

[@BinderTronics]

Full playlist on the PIC microcontroller Programming kzbin.info/www/bejne/gYSsZ5mwhLWJsJI If there is anything you would like to see let me know.

[@trysxit2236]

I will see your videos, the problems your videos are direct to pic, and I work with atmega, but it's like the same but for learning its a litle dificult, but no problem, can you tell me anithing about 5x8 dot and 5*11 dot, can I set fonte size 5*11 on the DDRAM character ou just can use 5*11 on character generator ??

[@ravenstone01]

These tutorials have been FANTASTIC.. I have a couple Aurdino boards, but I am addicted to the PIC chips.. I don't know if people let you know, but you have been a big asset for the PIC microchips.. I wish more people did videos on these chips, they really are good chips and sometimes more fun than the Arduino because you can get more involved with the chips.. Thank you for your time and support.. You are the best.

[@philbourdon9855]

Seeing a project with NRF modules (they use SPI communication) would be awesome. Anyways, I have been transitioning from arduino to PICs and your videos have been helping me out a lot, so I just want to say Thank you so much🤙🏼

[@BinderTronics]

It's on the list. Working on an basic SPI tutorial at the moment. Will look into it after that.

[@charlescarnes6982]

I got it working but I couldn't / don't know to display a floating point value. I tried (%1.3f , 1234) and a couple of other things. Thanks for a good video.

[@ravenstone01]

Also forgot to ask what programmer you use..? I have the PicKit3, but am looking at getting the PicKit 4.. Any opinions on the 4th version?

[@BinderTronics]

Using a PicKit3. Don't really have strong opinion on the PicKit4. Would probably buy one if I run into a chip that i can't program with the PicKit3 or J-link. Depending on your budget I would recommend buying the latest hardware if you can.

[@trysxit2236]

hello friend, nice project and good explanation. I'm started in embedded system, I already have some sub-routine work for controller lcd 40x02, with atmega 328p with ST7066 driver. but I have a problem with the "function set" I can't choice the fonte size 5*11, only can work with 5x8 dots font size. can you help me please try understund with can´t put the function set work correctly? thanks for your time

[@BinderTronics]

Post the binary value you are sending as the function set, including your RS and RW.

[@ethanarchambault2133]

How are you sending the data via PuTTY to the PIC? Nothing I type in my PuTTY terminal appears to get sent to the PIC.

[@BinderTronics]

kzbin.info/www/bejne/poHQdoqifr51r9E

[@Actinuon]

So I noticed that you #define variables to alias your LATxbits. When I do this, they are "Not Recognized" during debugging making it a headache to troubleshoot. If I predefine them above the #defines AND add a bool between the #define and the variable. Then they resolve perfectly, but that makes the compiler very angry, but still spits out my code. Is there a solution for this that you're aware of?

[@BinderTronics]

You are going to need tp show me what you are doing that the compiler is displeased with. It sound like you are redefining the values and that is why the compiler is complaining. !define LCD_DATA(x) do{ LATB = x;}while(0); may make GDB resolve the macro correctly. Just note I am replacing `#` with `!` because the comment filter does not like the `#` symbol (creates a hyperlink).

[@Actinuon]

​@@BinderTronics Well honestly, I loaded the program back up today, and it compiled, but did not work at all. I was definitely double defining it. It did however allow the GDB to resolve the macro... for a time. What IS working to run the code, but NOT allowing the GDB resolve the macro is this. !define Data1 LATCbits.LATC5 What DID work for a time was this. (albeit warnings) bool Data1; !define Data1 LATCbits.LATC5 Would your solution of do{LATB = x;}while(0) help the GDB resolve this? I'm defining each bit to allow me to run a straight wired bus to the LCD to keep the board nice and tidy. If it could help, would it be written like this? !define Data1 LATCbits.LATC5 do{LATCbits.LATC5 = Data1;}while(0);

[@BinderTronics]

Do it like this. It may or may not help. !define Data1(x) do{LATCbits.LATC5 = x;}while(0); how to use: Data1(1) // same as LATCbits.LATC5 = 1; Data1(0) // same as LATCbits.LATC5 = 0; Honestly surprised this compiles bool Data1; !define Data1 LATCbits.LATC5 This will break something. never tried something like this. If GDB refuses to resolve try using LEDs on the data lines or if you got a logic analyzer use that or watch the IO registers instead of the variable.