If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
it works! After connecting to the LCD DB0-DB3 it was still necessary to connect the R / W on my PCB there is an error R / W is shorted to GND
I will write tests how it works during the weeken
-
great project .. words of appreciation .. LCD backlight works under SW3 just as I wanted
Regards
I see from the last two pictures that you do not connect all LCD pins as in the schematics, i.e. it looks like that there are some pins that are not connected to the pcb, if it is so it won't work becasue this version drives the LCD in 8-bit mode for lower latency since there was enoungh free pins in the pic16f886, could you connect all the pins of the LCD as in the schematics and try again?
LCDs that I have do not require RT1 enough one 2k resistor to GND .. but I connected RT1 to the contrast on the pins .. this display worked well with previous VDI on PIC16F690 .. on the pictures you can see when PIC16F886 clean and programmed
-
R1 and R2 have changed values, it is a voltage divider for measuring BAT voltage, such values have been checked in an earlier version of VDI on PIC16F690
very nice pcb, I guess the problem is related to the lcd connections (e.g. lcd contrast), you don't have any measurements in the external oscillator because it is not used (you could have saved the components but it won't stop the vdi for working), would it be possible for you to attach an image like VDI.jpg or VDI_.jpg but with the components labels, i.e. R1, R2, etc for an easier comparison with the schematics?
I programmed again using PICKIT3 and MPLAB IPE as well as JDM and WinPICPgm and each time the same ... you can see that it runs, but the lack of content on the screen I designed PCB based on the scheme may be an error in the diagram
in the log file you copied I cannot see any message where the test firmware is loaded, if you are using MPLAB IPE after connecting the device you need select the firmware where it says "source" and then push program... I tested it with a pic16f886 I have and it worked fine, however I haven't tested it on the fields, could you try again and/or if you already managed to program it could you show your pcb?
Blank Checking...
Blank check complete, device is blank.
2018-08-04 11:56:42 +0200 - Device is blank
2018-08-04 11:56:46 +0200 - Programming...
Device Erased...
Programming...
The following memory area(s) will be programmed:
program memory: start address = 0x0, end address = 0x17ff
configuration memory
EEData memory
Programming/Verify complete
2018-08-04 11:56:59 +0200 - Programming complete
Pass Count: 66
2018-08-04 11:57:03 +0200 - Verifying...
Verifying...
The following memory areas(s) will be verified:
program memory: start address = 0x0, end address = 0x1fff
configuration memory
EEData memory
User Id Memory
this is a test firmware that was missing for PIC16F886 with a LCD, I added the following changes:
- VDI lower and upper limits for each VDI interval
- backlight control (on/off/SW3/ 0 < VDI < VDI_upper_limit)
- change style of strength bars for better readability
to test it with the sample pcb:
- Y1, C12, C13 are not necessary for PIC16F886
- short R15 for LCD contrast to work
- pins VEE, CS1, CS2 and RST are not used for LCD
- 78L05, R11 and Q1 depend on the LCD model
- SW4 (for reset) and the pin header (ICSP) are optional
95% of the code can be reused and you don't need to rewrite the program for every new model, only the specific part. PIC16F886 is in production and it is quite cheap, it would not make much sense to buy a pic with 128KB when you only need 14KB, for a GLCD I would say any pic with 32KB would be sufficient, e.g. PIC18F25K22, however an old model as the PIC18F252 would also work very well... it depends on the availability of the chips and the particular problem
Leave a comment: