DemineUA.org MD V1 - free and open source PI metal detector based on RP2040

[Eddy71]

I think this part should be placed with the bottom on a hot table when printing

[ivconic]

demineua.org I have one question.
How do you enter the basic parameters in the detector?
Via a Python script? "Configuration Tool"?
This requires installing Python and additional tools.
The last time I manipulated Python was back in 2017.
I remember that back then Python versions were not "legacy" and that scripts written in an older version could not be executed in a newer version and vice versa.
I tried to find my way now and somehow start the "Configuration Tool" but I didn't succeed.
I think you should write in some DOC or PDF text a "step by step" procedure how to install everything needed to be able to start and use the "Configuration Tool".
Because who doesn't regularly work with Python (I haven't since 2017 for example) ; he will have a lot of trouble finding his way.
Write a tutorial "for dummies"... literally step by step.
Be sure to specify the software versions to be installed.
Python is powerful, but it's a lot of work for someone who uses it for side jobs.
Everything that doesn't have its own IDE (maybe it does but I don't know) and everything that is executed via the CMD command line (or terminal in Linux) is very tiring and boring for someone who doesn't do it regularly.

[demineua.org]

I tried to find my way now and somehow start the "Configuration Tool" but I didn't succeed.

Basic parameters or "base" parameters are encoded in the firmware upon building it. Changing them in the field is not really intended.

Please open up README.md - it contains commands you need to run in linux or virtual machine (possibly even works in windows with WSL).
We wrote this tool for internal testing use, so the experience is not yet very user friendly. The communication with the metal detector can be done over wifi, if an ESP01 module with uart bridge has been installed, at which point it could be useful to have a phone app.
Theorethically the end user never should have or need to change anything on a detector with this tool, so at this point packaging it for ease of use is of low priority.
It has not been packaged for "ease of use" yet in a binary, but running it locally in a linux physical or virtual machine will 100% work.

Similarly to building the FW - check README.md for instructions on how to build it.

[ivconic]

Oh ok, then there's no need to do that for now.
I ask this because I asked a friend (from another place) who has an RP2040 module to write the code into the processor and check the basic functions.
He informed me that for now only the LED is working and that there is a sound at the output, but that there is no TX pulse signal at the output.
He said that the RP2040 in module form might not be suitable for testing because GPIO25 on the module is used for the signal LED and doesn't have that pin out on the pin row.
That's why I thought that maybe the code does not have pre-written parameters for TX out, because the pin does not output a signal.
I'm assuming the RP2040 module is useless until some hardware changes are made to the module.
Anyway, in the coming period, I plan to send to China to have at least one piece of original PCBs made for my personal hobby and testing.

[daluka]

[daluka]

[ivconic]

I managed to make it run:

[ivconic]

demineua.org how do you ground balance this detector?

[Carl-NC]

demineua.org how do you ground balance this detector?

From post 11: "No ground balance has been implemented as of yet, if you have any direction pointers for this - please let us know."

[ivconic]

I missed that. Despite the 24" monitor and glasses... I often overlook some things.
Ok. There's room for improvement, here's a good reason to elaborate on this topic in the forum.
Although the author said that there is no need to install the "Configuration Tool" and that the compiled code already contains
the set parameters; it might be a good idea to explain that in detail as well.
I believe there are plenty of members who would like to see everything.
I successfully installed everything, it's actually very easy and simple... I'll write a method for "dummies"...

.....................

a) Check if your computer has Python installed and what version it is.
My computer had Python installed but the wrong and old version.

b) If there is, uninstall both Python and Python Luncher (in Add or Remove programs in Windows).
In the first attempt, I didn't uninstall the Python Launcher as well, so I had problems because of that.
Therefore, it is necessary to remove the Launcher as well.

c) Find on the Internet and install "python-3.11.0-amd64.exe"

d) Open current folder 'pigui' in CMD.

e) Type (Copy&Paste from here) venv\Scripts\activate

f) When the command is done, type (Copy&Paste from here) pip install -r requirements.txt

g) Wait for the libraries to be installed, may take some time.

h) After installation, close the CMD window.

i) In Notepad Copy&Paste the following text (edit the port number to the USB port where your RP2040 is atttached)
and save it as "Start.bat" in the same 'pigui' folder:

python main.py COM3
pause

j) The GUI will not start if you do not have an RP2040 connected to a USB port.
I don't currently have an RP2040 with me, but I tried to "cheat and lie" it by attaching an Arduino UNO to the port.
And it worked, the GUI started!

[hykj888]

I come from China, and I understand JLC's charging rules. Since the goal is to minimize production costs, I will share my on how to reduce production costs:

1. Some PCB vias use 0.4/0.2mm sizes. These small vias are difficult to produce and the PCB production cost is more than twice that of normal PCBs. I noticed that the PCB component density is very low, so there's no need for small vias.

2. Identical components on the BOM are not grouped together. This will increase the SMT processing cost, as each component type inc an 8 yuan material change fee.

3. The two PCBs should not be connected together. The longer the PCB, the higher the production cost