I hope you are all well and in good health. I would like to thank every one of you for the valuable contribution and support you have always provided to each other in this wonderful community.
Today, I'm here to ask a question or raise a concern regarding [Arduino Nano]. I programmed a code to make the built-in light on the Arduino Nano board illuminate every second, but after uploading the code, the result was that the light turned on for four seconds and then turned off for four seconds.
Then, I changed the code and created a new one to count from zero upwards and display the count on the serial monitor. After uploading the code, strange symbols started appearing every four seconds. When I changed the speed of the serial monitor in the Arduino IDE program to 2400, although the speed in the code was not changed and remained at 9600, the numbers started to appear, but there was a four-second delay between each number.
Now, my question is: where is the problem? I think the issue might be with the speed of the crystal, which should be 16 MHZ . I searched for it but couldn't find it!! I will attach pictures of the Arduino Nano, and I kindly ask you to guide me to the crystal to ensure that it is indeed 16 MHZ.
If the problem lies with the crystal, please help me find a solution.
I look forward to sharing your ideas and experiences in finding the solution and learning more from you. Thank you again for being a part of this kind of community.
It is not an "Arduino" board, not a "Nano" and it does not have a "ATmega328P" microcontroller.
It uses a LGT8F328P, that is a clone chip. It can run at 16MHz without external crystal.
The crystal is not your problem.
I have my doubts about the soldering, and it is not fully compatible with a normal Arduino Nano.
What to do ? I don't know. If you have a plastic Christmas tree, then you can hang your fake board in your fake tree
I've heard about those, mostly bad things. But how do you know that's what this is? Is there some "tell-tale"? I can't see many markings on the chip in the photo, but it's often difficult to capture them with a camera, on real or clone chips.
I guess one tell-tale is that there seems to be no crystal, as @bazkhf has discovered. (The 12MHz crystal on the underside is for the CH340 USB-serial chip).
Thank you for moving the topic to the appropriate section, and I apologize for posting it in "Uncategorized." I will check the package you mentioned and give it a try to solve my issue. Thanks for the guidance!
Thank you for your insights into the board's specifications. I appreciate your clarification regarding the microcontroller used, as well as your suggestion that the soldering may be causing the issue. Your input is valuable, and I will definitely look into the soldering connections to ensure they are properly done.
As for the compatibility with a standard Arduino Nano, I will investigate further to understand any potential differences and how they might affect performance.
Your humorous suggestion brought a smile to my face! While the situation is challenging, maintaining a sense of humor certainly helps lighten the mood.
Once again, thank you for your assistance and suggestions. I'll keep you updated on my progress.
Thank you for your participation and engagement in the discussion. As you and our friend Koepel pointed out, the Arduino Nano board I acquired is a non-genuine version (not manufactured by myself), lacking an external crystal and instead utilizing the internal oscillator, with an internal clock division ratio of 4, meaning the oscillation speed is 4 MHz. Consequently, the LED light activation is delayed for 4 seconds instead of one, and similarly, the serial monitor does not respond at 9600 baud but does at 2400 baud. By calculating it mathematically, the internal clock division ratio can be determined, which is 9600/2400=4.
As for the jumper wire on the Arduino Nano board, I was surprised by its presence, just as you were.
I believe through exchanging these insights, we have gained valuable information to understand the reasons behind the LED light delay and issues related to the serial monitor. We look forward to more collaboration in the future.
Thank you once again for your contribution and the contribution of our friends in solving this issue.
