Building an Inductor Meter without External Comparator | Arduino Nano 

I think going over the code that's already written, in functional steps, which can sometimes involve skipping around where necessary, is better than going down through it in a very linear fashion "as you write it". But still educational as it is.

I appreciate the feedback

You need split your code to modules/functions. Then give each module and each function the most understandable unambiguous name. Then do it with each variable. Instead of comments, try to give variables and functions the most understandable names. Add comment to the code only if there is no other way to make the program more understandable. The quality of the code needs to be measured by WTF-meter. 1. Give your code yo another human. 2. Check WTF count. Lower WTFs is better.

It wasn't too long, but (for me) a tad quick. Manipulation of the registers could be more in depth in a separate video maybe?

I think a thorough explanation is good and, as you did, allow viewers to skip if they want. I've been teaching adults for nearly 4 decades. Everyone wants different things with this; the math, the code, the schematic, etc. The only way you can get close to pleasing everyone is to do the lot but provide skip points. Excellent description of your project, thanks!

True, quite the eye for details!

More related details: With the right rounding error the value of _power_ can even become 255, in which case you could probably just display "H" as the unit which you don't show in any case. More theoretical perhaps, but generally a wrong unit will be displayed when (power >= 12), but you will have other numeric problems as well at this point... (perhaps even with ns-level calculations) The _divisor_ can also become 0 which you might want to just treat as an erroneous measurement.

Hi, thanks. Hopefully I understand your question correctly; the standard libraries like are installed along with the compiler in a path that the compiler knows. The lcd.h is a custom one that must be added manually, therefore it is included with " ". It's path should be where the compiler is called, otherwise specified explicitly. I'm not an expert on this subject so hope this helps.

Thanks, I'll try to get that done, maybe with a GitHub account

@@5VLogic Thankyou

The code is now available on GitHub! Link in the description

Hi, I'm glad you were successful in building the project! Although I don't have any SMD inductors to test, I'm relatively sure it's because they have high series resistance. Being so small they have to pack a high number of turns in there, and the wire has to be very thin. This means that the energy is lost quickly before it has time to oscillate enought to give a reading. I think the program discards measurements with less than 4 oscillations maybe(?), it's been a while... Also I don't know the value of your inductors, but low values are also not read, for similar reason, not enough energy is stored in them to oscillate enough and the Q factor is also lower, creating the same result. You could measure series resistance with an ohm-meter to verify the hypothesis if you'd like.

Thanks! I thought of the PCB idea and but will wait until I add the capacitance and resistance measurement. For the max inductance, I've tested the low mH range and it works, but haven't pushed the limit.

@@5VLogic maybe the 5v are OK as voltage, as long as the mosfet and the psu can allow some amps to flow. Why not try with some transformers laying around? The pcb can be done even diy, you can provide an idea of the layout.

That's correct

Hi, I use avr-gcc as a compiler and avr-objcopy for the hex file. My makefile (and the whole project) is on GitHub and you can check it out and/or download everything there (link in description). In my case I run everything on Linux, but I think it should work on all OSs if the necessary utilities are installed.

​@@5VLogic thank you I compiled with avr -stdio and put the hex into the arduino nuno And I closed the circuit and it says open on the LCD, and when I connect the inductor to the circuit, the board makes a connection! Maybe the problem is with my compiler, please upload hex file 🙏

Finally got it done, hopefully it's correct because I stopped working on this project since I turned it into the LC meter in my following video, but it should work. I'll upload the hex file for that one too in case you'd like to try it.

@@5VLogic tank you 🥰

When connecting the inductor to the circuit, it draws up to 1 amp and heats up the bd137 transistor and writes >open< on the LCD.

@@erfanblaze4524 Hi, it's very difficult helping people through the internet debug circuits, but what I can do is give a few pointers and recommendations: 1) Check your transistor, if it's truly a BD137 and not a PNP. 2) Check the overall wiring. If you have and oscilloscope, probe all voltages around the transistor (the base in particular). 3) See if compiling your code and using my .ihex file gives the same result, if not there could be a problem in the code (potentially mine as well, although I don't think so). 4) Check the integrity of the arduino and it's pins, try an other GPIO to be sure, or test the one you're using with an LED to confirm it's working properly. Ideally check that it's capable of both sourcing and draining current. 5) Try swapping the transistor, in case it was bad or it got damaged. A MOSFET should work fine, but use a series resistor to limit the drain-source current. Place it on the drain side, not the source because it won't turn on properly. Unfortunately if the problem is hard for someone working on it in person, it's REALLY hard for someone over the internet. The general approach I recommend is to progressively excluding all possible faults and faulty components, one at a time by testing or swapping them. I really hope that helps, good debugging!

My circuit worked correctly and the problem was using the software >avrdudess< to put the hex code on the arduino nano, when I connected it directly to the atmega328 with the stk500 programmer and programmed the hex code, the problem was solved and the circuit worked correctly. he does Anyway, thank you very much for your advice 🥰🙏

​@@5VLogicMy circuit worked correctly and the problem was using the software >avrdudess< to put the hex code on the arduino nano, when I connected it directly to the atmega328 with the stk500 programmer and programmed the hex code, the problem was solved and the circuit worked correctly. he does Anyway, thank you very much for your advice

There is only one problem that it reads all the inductors, but it has a problem with small smd inductors like size 1206 and it doesn't show a number! I mean, where does the problem come from?

Hi, it's already available on GitHub, link in the description.

@@5VLogic The description link does not have a .hex file but only an exe.ihex file. I don't flash it your way, so I need the file .hex

Ok, I updated the repo, try it now and let me know if there are any problems.

I don't want you to change the name, I want a .hex file that can be loaded directly with the NEO programmer tool without avdure or similar, I don't use linux, I have ch341 avr and nep SPI programmer.

I don't want you to change the name, I want a .hex file that can be loaded directly with the NEO programmer tool without avdure or similar, I don't use linux, I have ch341 avr and nep SPI programmer.

Totally agree

Seems like you are even lower level programmer than me, I still use Arduino IDE despite writing in almost pure C, while you use vim on linux. Good to see that there are still some channels showing the proper way of doing things, instead of using pre-prepared solutions for everything. Yeah, it takes more time, but you also learn a lot more. I would say that it's the best way to master troubleshooting, logical thinking and pushing yourself to the limits not to give up. Not that long time ago I was crazy enough to write my own audio codec that beats MP3 when it comes to some aspects. Was it easy? Nope. But was it worth it? Definitely yes. Anyways, best wishes for you and your channel!

@_MINT: I suppose it depends on your definition of "garbage" and "shitty." Nothing that actually does what it's suppose to do can rightly be labelled as either. If it takes another half second for a program to run, who cares? If it uses code that theoretically can be optimized but it works anyway, why waste even more valuable time (the programmer's) to fuss with it? Since we _do_ have very-fast micro-controllers, why try to make the code faster than a person will even notice, at least for a test instrument such as this? If I insert an inductor in an instrument and it gives me a reading in 1.5 seconds instead of 15ms, I (the programmer/user) will never experience the delay in any meaningful way. This very long-standing concern with speed of execution--and with memory usage--if from an era when those things were either unavailable or costly. Now they're ubiquitous and _very_ cheap. The only other reason to make the fuss in all but the most critical applications (in which you wouldn't be using an Arduino anyway) is to assume a posture of superiority over "noobs" and to assert that twenty years of experience isn't just one year repeated twenty times.

@@tcarney57 well, I'm a perfectionist, so something totally okay for others might be garbage for me. I'm not gonna define what shitty and garbage means, let's not elaborate too much. I demand from my code to be clear, fast, memory efficient and totally idiotproof. No bugs allowed, even minor. Creating such a code takes time, but I am satisfied with myself afterwards. Only exeption from above rules is writing temporary code for test purposes.

@@tcarney57 I don't know why your reply is gone, but in my case it isn't "I am perfect". I am not perfect and I will never be. What pushes me to create "perfect" code is the need of an absolute control over what is happening and the need of having a feeling that the code is bug-free and stable. That implies using no libraries, unless I trust one, which isn't the case for most of Arduino ones, and also creating the code like it's some kind of fine art. I am something of an artist myself, very competitive one. Maybe my approach will change one day, I'm not even 20.