VDI-RODERICO

[roderico]

did you correct this
strcpy(name, "cooper "); should be "copper" in vdi.c

in these tests the names were removed because there is no enough space in PIC16F886 and they are misleading

Thanks for the code. I'm going to try porting it to a PIC24fj series part, since that is what I use in practically everything these days.

have a look at these two files: _18f25k22.h and _18f25k22.c these are the only files you would need to adapt to make it work...

[roderico]

you might also need to change more files e.g. see eeprom.c, eeprom.h and mcu.h and the GLCD/LCD drivers since they are 8bit...

[SWL]

Hello! The circuit and the pcb are different. Have you changed the scheme? Thank!

[roderico]

this avoids different saturation levels for channels X and Y after the MCP602, it was found by kroman01 after the first version of the pcb (2.0) but the pcb was never updated only the schematics, in any case the firmware should work well in both versions 2.0 and 2.1 (in version 2.0 you would have an earlier clipping in channel Y when the op-amp is in saturation)...

[SWL]

Ок...

[kroman01]

I did not have much time for testing, although I see that soft 2.1 works well, good work, there are new features or there will be a problem with adding to the MENU the battery voltage measurement on or off when no indication

[roderico]

since the display menu is already full that new feature should go into a new tab alone (no good) or to an existing one (not very good IMO) so this might not be in version 2.1, however you can have it for testing e.g. in the main menu...

[scrungy_doolittle]

Would you mind doing a package operation in the MPLAB X ide and sending it to me?
Did you use MCC to define the pins?

[roderico]

probably it would not work well with my settings, it would be easier for you to create a new project in MPLABX, select your pic, the compiler, simulator and then add the files to your project: _18f252.*, eeprom.*, fpu.*, mcu.* and the files in the lcd directory if you are going to use an LCD display or in the glcd for a GLCD. You would also need to set the pins manually in the files _18f252.* as the mcu's are not pin compatible and since pic24 is 16bit you would need to do some work to adapt the drivers (e.g. ks0108 ) and the peripherals (e.g adc, eeprom, ...)

[scrungy_doolittle]

Just thought I'd ask.
I'm considering a 28 pin PIC24FJ64GA series probably the 202 since it has DMA, a 12 bit adc and 3 built in comparitors. 28 pins matches the number on the schematic, though the GA204 would be a better choice for actually using to build a fully computerized detector. And Yes, I know that either one of these are overkill for a simple VDI, but the fact remains that I'm more comfortable with a 16 bit part than an 8 bit one.

[roderico]

I would suggest you first redo the circuit design... what improvements would you expect to have with PIC24 vs PIC18 in the vdi?

[kroman01]

it works glcd_21beta4kroman01, but instead there is a blank screen, at which time you can display the set options

[roderico]

yes, the battery voltage is not shown when you select "none" in the display entry ( in main menu ), I don't fully understand the question...

[kroman01]

when the battery voltage is not displayed, you can display the currently used X-Y HISTOGRAM or SCOPE all the time

[roderico]

ok, I think I understand now, there is an option in the display menu called "hold" where you can set the time in seconds that the display is hold before changing to the battery voltage from 1s to 30s, and what you would like is if it would be possible to set this value to e.g. "unlimited" for always showing the last vdi value?