Announcement

Collapse
No announcement yet.

VDI-RODERICO

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • kroman01
    replied
    VDI in case of no signal will show 00 STR will be 0.00V checked in XY view, when STR reaches 0.01V VDI will give reading, my suggestion of next change is not necessary "glcd_21beta4kroman01-4" is ok

    Leave a comment:


  • roderico
    replied
    but the vdi value should be cleared because it is undefined when there is no signal, and it would only show 0V for STR and no battery?

    Leave a comment:


  • kroman01
    replied
    "Glcd_21beta4kroman01-4" I checked, it's ok, I would like to add the third element in the frame "idle" only without displaying the battery, but with the display of VDI and STR during inactivity

    Leave a comment:


  • roderico
    replied
    try this one, it shows the battery as in the scope view:
    Attached Files

    Leave a comment:


  • kroman01
    replied
    I think the scope view is better than the histogram

    Leave a comment:


  • roderico
    replied
    histogram view uses a big font, so a possibility could be to add the battery ('B') and strength ('S') together like in the Lugatek vdi, check this other version (this might still need more tests):
    Attached Files

    Leave a comment:


  • kroman01
    replied
    it's the way I wanted it to be, but it's not worth adding the text Battery in the histogram and scope
    Click image for larger version

Name:	histogram.jpg
Views:	1
Size:	140.2 KB
ID:	354561
    Click image for larger version

Name:	scope.jpg
Views:	1
Size:	135.6 KB
ID:	354562

    Leave a comment:


  • roderico
    replied
    ok, try this one instead...
    Attached Files

    Leave a comment:


  • kroman01
    replied
    I used "glcd_21beta4kroman01-2" and it does not work with my display I need a version for the RA8808 controller

    Leave a comment:


  • roderico
    replied
    Originally posted by scrungy_doolittle View Post
    ...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......
    the space limitation is for PIC16F886 (16K) , PIC18F25K22 (32K) still has 40% free, a possible way to implement the stopwatch with PIC18 would be by using an external 32KHz oscillator to measure seconds but then some pins need to be reassigned, Y1 oscillator removed or a pic with more than 28 pins? this change would not be backwards compatible and the vdi should be moved to version 3.x and then it could be made compatible with PIC24 at the same time...

    Leave a comment:


  • roderico
    replied
    ok no problem, the files should work with kicad 5.x, I added a trimmer 3362P, a jumper and the ks0108 connectors since I couldn't find them in kicad at the time I made the schematics. v2.0 of the firmware + source code were released somewhere in the thread as SWL mentioned, but 2.1 is still in testing before releasing the final firmware with the source code...
    Attached Files

    Leave a comment:


  • SWL
    replied
    It has long been published

    Leave a comment:


  • scrungy_doolittle
    replied
    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......

    Leave a comment:


  • scrungy_doolittle
    replied
    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.

    Leave a comment:


  • scrungy_doolittle
    replied
    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?

    Leave a comment:

Working...
X