Announcement

Collapse
No announcement yet.

Arduino based VDI!

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

  • Richlsdorfite
    replied
    A good alternative to Moteino could be Teensy 3.2 (MK20DX256 - 32 bit ARM - Cortex-M4 - 72 MHz).
    37 ksps for 16 bit ADC, seems to be quite good for VDI purpose.

    I find this VDI made with PIC 18F4520 : http://www.aspeluut.nl/metaaldetector.php

    Leave a comment:


  • ivconic
    replied
    Hello Don!
    Any news, upgrades?
    With huge delay i got my UNO on the bench...

    Click image for larger version

Name:	DB_VDI_3.jpg
Views:	1
Size:	921.1 KB
ID:	343624

    Leave a comment:


  • Davor
    replied
    Originally posted by Krzysztof View Post
    http://www.wino-board.com/
    Best regards Chris.
    I'll see about this one. Wireless may be interesting, yet it usually means using lots of energy.

    Leave a comment:


  • Davor
    replied
    Originally posted by Daren View Post
    Depending how VDI is done. Most of the time I can tell what coin it is before I dig it with TGSL + my VDI. I can also tell if the object if irregular (foil like) or more compact like coin (foils give jugged signal profile) . This is not absolute info but just hints that help you to decide if you want to dig. (You may not want to keep digging cents, but you will quarters).
    Power usage is not really an issue with Arduino Mini Pro, also make sure you don't run LCD backlight LED at full blast.
    I think VDIs are really useful. There is a lot more info that can be given to the user than just a VDI number. The profile of RX signal as coil passes over the object is very informative. Show strength and phase of the signal in time. When all that info gets compressed in to a single VDI number a lot is lost. Another idea is to use the RX strength to control sound strength and RX phase to control sound pitch. That may be even more useful, you should be able to train you brain/ear to different target responses much easier than keep looking at the signal/strength plots. Plus this can be done easily in analog circuitry, no MCs needed.
    I'd say there is a hope for you and the like-minded people. Your ears are completely capable of discerning lots about the target geometry, and you don't need a VDI to simply hear it.
    I searched for 4 channel ADC with 24 bit resolution that may be used with Arduino, and I found ADS1253. It should provide some serious advantage over Arduino's own ADC.
    It is supposed to suck little power and have good dynamic range. Price should be around an Arduino board, so it is OK.
    You are right about doing it all in analogue circuitry. Some people call the pitch setting according to the conductivity - an audio VDI. Since that's precisely what I need, I'll most probably go with analogue anyway. Arduino with a proper ADC may have some serious edge over analogue in a multifrequency solution.

    Leave a comment:


  • Virdi_248
    replied
    I leave my files for all who wish to use.

    I do not use decoder. My LCD illumination is controlled by a switch. On/off only.

    GEOTECH thanks especially to members

    Prospekteur Darem.


    TGSL EDU_Arduino_Vdi part 1.rar
    TGSL EDU_Arduino_Vdi part 2.rar

    Missing two libraries necessary for Arduino. They have to search for the network.
    LiquidCrystal_I2C
    MenuSystem


    Coming soon will show a video. greetings

    Leave a comment:


  • Daren
    replied
    Originally posted by Davor View Post
    My strong opposition against VDI so far was that it is a mere gimmick and a power hog. Low power MCU variants tend to eliminate the power hog argument though.
    Depending how VDI is done. Most of the time I can tell what coin it is before I dig it with TGSL + my VDI. I can also tell if the object if irregular (foil like) or more compact like coin (foils give jugged signal profile) . This is not absolute info but just hints that help you to decide if you want to dig. (You may not want to keep digging cents, but you will quarters).
    Power usage is not really an issue with Arduino Mini Pro, also make sure you don't run LCD backlight LED at full blast.
    I think VDIs are really useful. There is a lot more info that can be given to the user than just a VDI number. The profile of RX signal as coil passes over the object is very informative. Show strength and phase of the signal in time. When all that info gets compressed in to a single VDI number a lot is lost. Another idea is to use the RX strength to control sound strength and RX phase to control sound pitch. That may be even more useful, you should be able to train you brain/ear to different target responses much easier than keep looking at the signal/strength plots. Plus this can be done easily in analog circuitry, no MCs needed.

    Leave a comment:


  • Krzysztof
    replied
    Originally posted by Davor View Post
    The whole idea of an arduino is to have a simple programmable sensor module ...

    Best regards Chris.

    Leave a comment:


  • Davor
    replied
    The whole idea of an arduino is to have a simple programmable sensor module capable of performing some data crunching and networking. Convincing an ADC to perform beyond its bit depth is challenging the purpose of the exercise. I can make an arduino act as a whole discriminating detector, even as a multifrequency one, but the very notion that performance will be crippled due to a stupid ADC says: don't do it. It can perform as a nice VDI though.
    My strong opposition against VDI so far was that it is a mere gimmick and a power hog. Low power MCU variants tend to eliminate the power hog argument though.

    Leave a comment:


  • Daren
    replied
    @Davor
    you should take a look at STM32 line of MCs. You can do 5Msps @12 bits (F3 F4 models). Low power models can do 1Msps 12 bits. (low power line is L0 and L1)
    I worked with STM32 F1 and F3 F4; all very nice MCs. It will be more difficult to program them than Arduino, but ADCs are much faster on SMT32. (I think I posted this into before, mabe in other thread...)
    IAR embedded workbench works very nice with them. StmCubeMX lets you configure the pin easily..
    Teensy 3.1 is another nice MC, but ADC can do 800Ksps at 13 bits

    Leave a comment:


  • Davor
    replied
    I've gone through similar links before, with mild disappointment. Playing with interrupts and sleep modes works in case you have little to do, say measure temperature, but not for real time data. This Moteino uses low power variants of processors (with "p" suffix) instead. So I can have a cake and eat it too. If I wanted a powerhog, I'd simply buy an used ...you know what.
    10bits ADC at 15ksps is not much for, say, software defined detector, but may work well in motion mode after synchronous demodulators. Such detector could do VDI (Visual Discrimination Indicator) and audio output with VCO-like Audio Discrimination Indicator.
    Too bad there is no proper ADC to match with Arduino and do it all in software.

    Leave a comment:


  • Koala
    replied
    Originally posted by Davor View Post
    I'm considering Arduino platform for some experiments, but the original Arduino uses too much power for my taste. Raspberry is even worse.
    I found Moteino clone to be much better in terms of power consumption and capabilities, but I have no experience with Arduino. Does anyone know of, or maybe uses some Arduino clones designed for low power? Preferably with wireless connection.
    Thanks.
    You might have already seen this


    link1
    link2

    Leave a comment:


  • Davor
    replied
    I'm considering Arduino platform for some experiments, but the original Arduino uses too much power for my taste. Raspberry is even worse.
    I found Moteino clone to be much better in terms of power consumption and capabilities, but I have no experience with Arduino. Does anyone know of, or maybe uses some Arduino clones designed for low power? Preferably with wireless connection.
    Thanks.

    Leave a comment:


  • ricalbertvig
    replied
    where I can find this version? you need to make

    Leave a comment:


  • Koala
    replied
    Even Deus users dig deep horseshoes so no detector is that good when towards the end of its depth. Makes sense as not much signal change to detect.

    Leave a comment:


  • gtdavid
    replied
    I think your right at the 50% to 75% range as I have managed to stabilize my vdi at that point.
    I also found that including negatives in the sample trigger also helped to improve the vdi stability.
    eg.
    if ((sensorValuex > 5 && sensorValuer > 5)||(sensorValuex < -5 && sensorValuer < -5)){
    ...
    }

    Leave a comment:

Working...
X