VDI-RODERICO

[kroman01]

I think that after switching off the battery display, the "hold" option should remain unchanged, but after the time of the last result should be reset and wait for the next measurement, as shown on the Lugatek DM-1
https://youtu.be/OY7gQPSx4vU

[scrungy_doolittle]

Pic 24 has a lot more memory, better resolution on the ADC, and the ability (for those with DMA) to digitize the signal much more quickly and efficiently, in addition it has a JTAG debug interface, 3 comparators/opamps (which might allow the replacement of the OPAMP, with the built in opamps). Some versions have CLC (configurable logic on board) take the PIC4f16KM102, and PIC24FJ64GA702 for example. The PIC24F08KM202 is a 28 pin part, but only has 8K of memory, while the PIC25F16KM202 has 16K of memory, 2 opamps, 2 DACS and a 12 bit 200Ksps ADC, but no PPS, but it does have 2 CLC modules. The schematic would have to be re-done for this one. The dsPIC33 family has built in opamps, as does the PIC24FJ128GC010 which also has a 16 bit ADC, and comes in a 100 and 64 pin versions. of course it is more expensive, but it has everything one would need for a digial detector and/or a vdi. And I don't like the weird 6 bit word and 12 bit address of the 8 bit pics. The circuit design doesn't have to be redone, because the PIC24 has PPC mapping, so it is trivial to match the pin connections. All that really needs to be done, is to make sure the footprint on the board will work. I.E. through hole vs qfp vs whatever. You could also switch to a dspic 33 of needed. Being an old embedded programmer with 40+ years experience, I know that the more memory you have, the better. The PIC24 is unique in that the pinout for a given pincount is identical. So you can take a PIC24FJ16GA202 and remove it and put in a PIC33 if you want to. Indeed I took a dsPIC33 off the chipkit 32 board and replaced it with a PIC24FJ1024GA110 directly, and it works just fine. So you have a complete migration path from 16K to 128K just by replacing parts. https://www.microchip.com/ParamChart...8196&popular=1

[scrungy_doolittle]

One thing that should be in the VDI is a time since turn on. It would also be nice to be able to set a time for searching, and have it notify you. The use case here, is using it during a lunch break. Set the timer for however long you want to hunt, then when it times out, beep and or flash the screen. That way, you can hunt for a specific amount of time. I would
find that extremely helpful....

[scrungy_doolittle]

That is a sweet detector. Wonder if the firmware and schematic are available?

[roderico]

I think that after switching off the battery display, the "hold" option should remain unchanged, but after the time of the last result should be reset and wait for the next measurement, as shown on the Lugatek DM-1
https://youtu.be/OY7gQPSx4vU

ok, I see, just to clear the contents and left the frame and/or axis for the next measurement... other possibility could be to add another view e.g. similar to the Lugatek (without the animations) but for v2.2?

[roderico]

Pic 24 has a lot more memory, better resolution on the ADC, and the ability (for those with DMA) to digitize the signal much more quickly and efficiently, in addition it has a JTAG debug interface, 3 comparators/opamps (which might allow the replacement of the OPAMP, with the built in opamps). Some versions have CLC (configurable logic on board) take the PIC4f16KM102, and PIC24FJ64GA702 for example. The PIC24F08KM202 is a 28 pin part, but only has 8K of memory, while the PIC25F16KM202 has 16K of memory, 2 opamps, 2 DACS and a 12 bit 200Ksps ADC, but no PPS, but it does have 2 CLC modules. The schematic would have to be re-done for this one. The dsPIC33 family has built in opamps, as does the PIC24FJ128GC010 which also has a 16 bit ADC, and comes in a 100 and 64 pin versions. of course it is more expensive, but it has everything one would need for a digial detector and/or a vdi. And I don't like the weird 6 bit word and 12 bit address of the 8 bit pics. The circuit design doesn't have to be redone, because the PIC24 has PPC mapping, so it is trivial to match the pin connections. All that really needs to be done, is to make sure the footprint on the board will work. I.E. through hole vs qfp vs whatever. You could also switch to a dspic 33 of needed. Being an old embedded programmer with 40+ years experience, I know that the more memory you have, the better. The PIC24 is unique in that the pinout for a given pincount is identical. So you can take a PIC24FJ16GA202 and remove it and put in a PIC33 if you want to. Indeed I took a dsPIC33 off the chipkit 32 board and replaced it with a PIC24FJ1024GA110 directly, and it works just fine. So you have a complete migration path from 16K to 128K just by replacing parts. https://www.microchip.com/ParamChart...8196&popular=1

The question was more about if you build both versions ( PIC24 and PIC18 ) using a firmware with the same features would you expect a clear improvement in the vdi (there is no doubt that PIC24 is better)?

[roderico]

One thing that should be in the VDI is a time since turn on. It would also be nice to be able to set a time for searching, and have it notify you. The use case here, is using it during a lunch break. Set the timer for however long you want to hunt, then when it times out, beep and or flash the screen. That way, you can hunt for a specific amount of time. I would
find that extremely helpful....

this might be an example for a better PIC ( e.g. PIC24 )...

[roderico]

That is a sweet detector. Wonder if the firmware and schematic are available?

many of the IDX-PRO components could be replaced by functions in the firmware as well as the vdi simplifying the detector...

[roderico]

I think that after switching off the battery display, the "hold" option should remain unchanged, but after the time of the last result should be reset and wait for the next measurement, as shown on the Lugatek DM-1
https://youtu.be/OY7gQPSx4vU

I moved the backlight to the main menu and defined a new entry in the display menu called "idle", setting this to "frame" it will retain the frames/axis and move the battery voltage to the vdi place, this still does not look good so probably for version 2.2 but you could give it a try anyway:

[roderico]

One thing that should be in the VDI is a time since turn on. It would also be nice to be able to set a time for searching, and have it notify you. The use case here, is using it during a lunch break. Set the timer for however long you want to hunt, then when it times out, beep and or flash the screen. That way, you can hunt for a specific amount of time. I would
find that extremely helpful....

this would require a larger display, and then a better PIC as the PIC24 as you suggested, however, it might not be very practical because sometimes you turn off the detector e.g. for a break, and then you would need to start over by setting the correct time for lunch, a simple stopwatch or a mobile phone with alarm would do the job better and more reliable IMO. I believe the main improvement of PIC24 for this vdi could be in the math operations since they are implemented with 16 bit integers but they are not very demanding so a mid-range pic can do the job, IMO the only way to know if there is a noticeable difference in performance would be to build both and compare them directly, PIC24 memory could be used to upgrade to a larger display, otherwise it would be wasted as this vdi does not require a very large amount of memory...

[dbanner]

One thing that should be in the VDI is a time since turn on. It would also be nice to be able to set a time for searching, and have it notify you. The use case here, is using it during a lunch break. Set the timer for however long you want to hunt, then when it times out, beep and or flash the screen. That way, you can hunt for a specific amount of time. I would
find that extremely helpful....

I use an ancient device called a wristwatch. But that's a cool idea for incorporation into the VDI. Sometimes the time does run away unnoticed.

[scrungy_doolittle]

It would give more code space to improve the vd, and 12 bits of resolution vs 10 bits. Build one with firmware with the same features, but now you have room to do a lot more things, including some digital processing of actual signals prior to the X/Y tap.
That being said, I seem to remember seeing that the VDI2 schematic was done in KICad. Can you zip the KiCad schematic, and board files for 2.1 and place them in this thread?

[scrungy_doolittle]

Please release the source with the binaries... Being an embedded firmware engineer by trade (>40 years), I always have to, in my current job, zip the source and the binary at the same time. That way there is always a way to rebuild the current binary.

[scrungy_doolittle]

It would be very practical. Personally I'd have the vdi on a separate power source... independent from the detector, and arranged such that when you turn off the VDI it also turns off the detector, but when you turn the detector off, the VDI doesn't, if your usecase is correct. But for me, when I'm out hunting during a lunch break, I would like the timer on the display. And it would not require a larger display.
Just a way to set it. A menu option to show it, and let it run. When the time is up, it then displays a message on the screen. Even with a 2x20 display this would not be to big a deal to do. As for memory, you mentioned that you took the names out to save memory, so you must be getting close to the limit. Remember, code expands to fill the available space......

[SWL]

It has long been published