VDI-RODERICO

[kroman01]

this is my suggestion of another display that is more easily available, recently I have a problem with purchasing displays from KS0108 ...

[roderico]

you would need some kind of level converter for all the pins to use this display safely, however it could work well with pic24 which has the same operational voltage, but IMO changing from 5V to 3V the whole vdi (pic24+st7565) is not a trivial task and a lot of work with no clear improvement, the easiest thing IMO if you need another display would be to look for a display that works with 5V+parallel interface

[kroman01]

I hardly found catalog cards for displays that interest me, the first one has a SMD ZIF34 connector, the second is a THT pin28 connector

https://www.lcd-module.de/eng/pdf/zubehoer/st7565r.pdf

http://www.artronic.com.pl/o_produkcie.php?id=1113

http://www.blaberk.com.pl/arduino/DEM128064O.pdf

[roderico]

is the datasheet of the display available somewhere?

[kroman01]

The 3V3 power supply should not cause problems, the interface is SPI, but also 8-bit parallel

[roderico]

it would be possible by writing a new driver and changing the pins but the main problem is that it works with 3.3V and many of these displays only have a serial interface...

[kroman01]

hey roderico, I thought there would be a problem with compiling version 2.1 for a display with the ST7565R driver

[roderico]

I have opened the ide in kicad, and am working on creating some custom symbols for a couple of different flavors of PIC24's trying to keep the port definitions the same. What kind of display are you using?

currently it only works with a HD44780 compatible LCD or a 128x64 GLCD KS0108-based

So. make it a 4 bit interface, using D0-D3 (really simple in software). That frees up B6 and B7 for debugging, and gives you two spare I/O pins.

the parallel interface (8-bit) is important at least for the GLCD to reduce the latency of the display and memory requirements in the PIC

I would allocate RC0-7 as the data lines for the display, and use RB0,1,and 2 for the switches. This keeps them on consecutive bits at the ls 3 bits of the port, simplifying reading them. I would use RB3 fro K-, RB4 for RW, RB5 for rst, RA4 CS1 RA5 for CS2, and tie enable permanently active.

you would also save the 3 pull-up resistors but you would have a more complicated PCB layout

On a 44 pin PIC24, you also could set it up to use a SPI display, and indeed you could also use a spi display with the current connector, just use the D2 and D2 (pin 22 and 23) for the spi port.

if you have plenty of free pins in pic24 why do you want to use a serial interface?

What I want someone to do, is to add another sheet to this project, and move the connectors to it. I have not been able to figure out how to do that.

in the menu "Place" -> "Hierarchical Sheet"

[roderico]

they use different file formats: http://kicad-pcb.org/help/upgrading/

[scrungy_doolittle]

I made them under Kicad 4.0.5. 64 bit
I'll try to install KiCad 5, and see if I can open it.

[roderico]

sigh. yet another release without the source code. PLEASE ALWAYS include both the source and binary, so changes can be tracked. It helps folk understand the code.

this the source code for version 2.1 as it seems there is no additional bugs in version 2.1b4. It does not include kroman01's mod since it still needs some more work, it would be better for version 2.2 while fixing new bugs in version 2.1, in any case it can be used as it is in glcd_21beta4kroman01-5. The main changes w.r.t. version 2.0:

- fix width of integers in vdi limits
- expand range of minimum vdi to [-120,120] to exclude also positive vdi values
- fix sampling ending before 400ms (only the first 200ms were used in v2.0)
- implement axis scaling in histogram view
- remove ticks at +/-45 degrees in histogram view (kroman01's idea)
- exclude vdi values from the saturation region in histogram view (you might need 2x scale to be similar to v2.0)
- add C18 compiler compatibility and remove SDCC (too slow)
- extract vdi from histogram as mean +/- mean deviation
- highlight vdi when the uncertainty is small
- replace max(x,y) with maximum value from the histogram

The firmwares are compiled with Microchip XC8 in free mode since my demo licensed expired a very long time ago and the PRO license is very expensive, so I also built the firmwares with previous Microchip C compiler (C1 for testing and comparison...

[roderico]

I have just read the messages and I see there is a lot of progress in the pic24 port, but I cannot open the *.sch files either in kicad 5, maybe you already have an updated and working version so if you could possibly upload them again I could also have a look...

[scrungy_doolittle]

>>>>.that doesn't look too crowded if that is all there is. It actually looks very good and I can not see any value of splitting this onto multiple sheets.

Because 1. it is to cramped to add new features. There are some things I want to do with this, one of which is use the VDI to generate specific tones, but that requires a small amp and speaker. I agree that perhaps for the vdi this might do, but for me, this is just a starting point for other features.



[QUOTE]A little trick is not putting every name for each processor pin on it's schematic symbol. 2 or 3 primary pin names is enough to draw and show a schematic. The processor schematic symbol is then smaller (narrower, it can be 1/3 the current width) allowing more room. [\QUOTE]
When I pulled the 44 pin template in, that is how big it was, and I don't know how to fix that.

Then use Net Label/Names to label wires going to the processor that are specific to the design makes it very readable.

considering I don't know how to do that, it would be nice to have someone else clean it up.
I will note that there are a couple of changes that would have to be made to pin mapping in the current source code, but it should be a fairly painless port.
The main issue is that the OSC pin was in conflict, and the debug pins need to be separate.

Example: pin 19 can be simply "RA0/VREF+". The data sheet and a spread sheet is used if other pin functions are used. The way it is currently drawn it is not totally clear as what pin 19's internal function is. Pins 3, 2, 36,... are clear that these are digital inputs so use function RC7, RC6, RC3,...

[waltr]

Here is the pdf.
As you can see it is pretty crowded, which is why I would like someone to turn it into a multi sheet project (at least 3 sheets)

Thanks.
that doesn't look too crowded if that is all there is. It actually looks very good and I can not see any value of splitting this onto multiple sheets.

A little trick is not putting every name for each processor pin on it's schematic symbol. 2 or 3 primary pin names is enough to draw and show a schematic. The processor schematic symbol is then smaller (narrower, it can be 1/3 the current width) allowing more room.
Then use Net Label/Names to label wires going to the processor that are specific to the design makes it very readable.

Example: pin 19 can be simply "RA0/VREF+". The data sheet and a spread sheet is used if other pin functions are used. The way it is currently drawn it is not totally clear as what pin 19's internal function is. Pins 3, 2, 36,... are clear that these are digital inputs so use function RC7, RC6, RC3,...

[scrungy_doolittle]

vdi3

Here is the pdf.
As you can see it is pretty crowded, which is why I would like someone to turn it into a multi sheet project (at least 3 sheets)