Announcement

Collapse
No announcement yet.

Arduino Nano PI Main Discussion

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

  • Originally posted by Qiaozhi View Post
    Nice.

    I downloaded the code and compiled it. It takes 47% of the program space, so would probably fit on an Arduino Nano with the PI code. However, the overhead of the display might affect the audio response of the detector as you suspected. In this case, having a separate display driver is a good solution.

    You might also want to look at the Arduino Voodoo code where I used a very similar OLED (an SH1106 as opposed to an SSD1306). In that example I used the U8x8lib instead of the Adafruit_SSD1306 library. -> https://www.geotech1.com/forums/show...883#post287883
    Thanks for the input. I will try the U8x8lib and see if it will work faster. It would be nice to be able to put it on the Nano that is onboard that way you can add the additional info (batt, threshold, delay) that you added for the voodoo.

    Comment


    • Originally posted by MartinB View Post
      Looks really good. Are you using a display with a yellow portion at the top or are using a RGB display?
      the top is yellow... Its a happy accident that it kinda works out for this.

      Comment


      • Originally posted by Agme View Post
        Thanks for the input. I will try the U8x8lib and see if it will work faster. It would be nice to be able to put it on the Nano that is onboard that way you can add the additional info (batt, threshold, delay) that you added for the voodoo.
        Actually, thinking about it some more, the audio won't be affected on the ANPI because it's controlled by the analog circuitry, unlike Voodoo.

        Comment


        • Originally posted by Agme View Post
          the top is yellow... Its a happy accident that it kinda works out for this.
          I hadn't noticed that. The OLED that I was using is monochrome.

          Comment


          • Originally posted by Qiaozhi View Post
            Actually, thinking about it some more, the audio won't be affected on the ANPI because it's controlled by the analog circuitry, unlike Voodoo.
            I attempted to make the display work with the onboard nano. It worked but it was not behaving normal there was jitter in the pulses. And i think some of the analog readings where dropping out. I think i will see if i can use a Attiny chip or something that requires less power to read and display the readings from the board.

            I was unable to get the U8x8lib to work with my display. It would only show a 3/4 of the screen.
            I found a very small code that might work, but i did not try on the onboard nano yet.
            http://www.technoblogy.com/show?23OS

            Comment


            • Originally posted by Agme View Post
              I attempted to make the display work with the onboard nano. It worked but it was not behaving normal there was jitter in the pulses. And i think some of the analog readings where dropping out. I think i will see if i can use a Attiny chip or something that requires less power to read and display the readings from the board.

              I was unable to get the U8x8lib to work with my display. It would only show a 3/4 of the screen.
              I found a very small code that might work, but i did not try on the onboard nano yet.
              http://www.technoblogy.com/show?23OS
              Hi Agme
              The issue you are having with 3/4 display is that the starting point is not at the left hand side of the display
              Have you got a line in your code that looks something like this?
              U8G2_SSD1306_128X64_NONAME_1_HW_I2C u8g2(U8G2_R0, /* reset=*/ U8X8_PIN_NONE); which is used to initialise the display.
              To select the right statement for your display, go into the U8glib folder, select the .scr file and open with Notepad++ which is downloadable from https://notepad.software/download
              Find the right statement for your display and then copy and paste into your code. Just be aware that there are hundreds of line entries in the .scr file so this might take a bit of time

              Comment


              • Originally posted by MartinB View Post
                Hi Agme
                The issue you are having with 3/4 display is that the starting point is not at the left hand side of the display
                Have you got a line in your code that looks something like this?
                U8G2_SSD1306_128X64_NONAME_1_HW_I2C u8g2(U8G2_R0, /* reset=*/ U8X8_PIN_NONE); which is used to initialise the display.
                To select the right statement for your display, go into the U8glib folder, select the .scr file and open with Notepad++ which is downloadable from https://notepad.software/download
                Find the right statement for your display and then copy and paste into your code. Just be aware that there are hundreds of line entries in the .scr file so this might take a bit of time
                Thanks, I will try it. I spent so much time reading peoples code and datasheet for this display I think I understand the commands to directly control it without the libraries. I have been trying to get it to be as fast and small as possible and it seems difficult to do with the libraries.

                Comment


                • Originally posted by Agme View Post
                  Thanks, I will try it. I spent so much time reading peoples code and datasheet for this display I think I understand the commands to directly control it without the libraries. I have been trying to get it to be as fast and small as possible and it seems difficult to do with the libraries.
                  U8G2_SSD1306_128X64_NONAME_1_HW_I2C u8g2(U8G2_R0, /* reset=*/ U8X8_PIN_NONE); works very well with my yellow and blue OLED which is in another project.

                  Try the following;


                  #include <U8g2lib.h>
                  #ifdef U8X8_HAVE_HW_SPI
                  #include <SPI.h>
                  #endif
                  #ifdef U8X8_HAVE_HW_I2C
                  #include <Wire.h>

                  U8G2_SSD1306_128X64_NONAME_1_HW_I2C u8g2(U8G2_R0, /* reset=*/ U8X8_PIN_NONE);

                  void setup() {

                  u8g2.begin();
                  Last edited by MartinB; 07-28-2021, 10:09 PM. Reason: Additional Information

                  Comment


                  • I have moved this thread to a dedicated Arduino Nano forum. I encourage people to open new threads for particular discussions so it becomes easier for others to find relevant information. If you have posts in this thread you would like extracted to a separate thread let me know.

                    Comment


                    • Hi all.
                      I'm at the beach, and every night I'm with the nano. I notice a phenomenon: at the start of detection, there are very few false signals, then after 2 hours of use, false signals appear(earth fields) . the battery voltage is always at 12v, from start to finish. I specify that I am on the wet sand of course. the phenomenon is attenuated if I switch to boost mode. George, do you have an explanation?
                      thermal drift of a component? or maybe just sand stuck under the coil ..? to validate the stuck sand, this evening I will pass the coil in sea water as soon as the phenomenon appears.

                      Comment


                      • Originally posted by lamoiz View Post
                        Hi all.
                        I'm at the beach, and every night I'm with the nano. I notice a phenomenon: at the start of detection, there are very few false signals, then after 2 hours of use, false signals appear(earth fields) . the battery voltage is always at 12v, from start to finish. I specify that I am on the wet sand of course. the phenomenon is attenuated if I switch to boost mode. George, do you have an explanation?
                        thermal drift of a component? or maybe just sand stuck under the coil ..? to validate the stuck sand, this evening I will pass the coil in sea water as soon as the phenomenon appears.
                        All the timing is done by the Arduino Nano, so it's not really possible for the timing to drift due to temperature. I would suspect that it's something to do with the coil.
                        If it sounds like an Earth field problem, you can prove / disprove that by waving the coil in the air from side to side away from the ground.
                        What happens if you turn off the detector for a few minutes and then turn it back on? Does the problem go away?

                        Comment


                        • Originally posted by Qiaozhi View Post
                          All the timing is done by the Arduino Nano, so it's not really possible for the timing to drift due to temperature. I would suspect that it's something to do with the coil.
                          If it sounds like an Earth field problem, you can prove / disprove that by waving the coil in the air from side to side away from the ground.
                          What happens if you turn off the detector for a few minutes and then turn it back on? Does the problem go away?
                          the problem appears after a certain time of detection. 1h30 or 2 hr the problem occurs. If I switch off and turn on the detector, the problem remains the same.
                          for the voltage regulation of the power supply module, I use 2x 18650 li ion and an xl6009 module to maintain a permanent 12v
                          tomorrow I will test the coil on an analog surfPI to see the problem comes from it or not.

                          Comment


                          • Originally posted by Qiaozhi View Post
                            All the timing is done by the Arduino Nano, so it's not really possible for the timing to drift due to temperature. I would suspect that it's something to do with the coil.
                            If it sounds like an Earth field problem, you can prove / disprove that by waving the coil in the air from side to side away from the ground.
                            What happens if you turn off the detector for a few minutes and then turn it back on? Does the problem go away?
                            If it sounds like an Earth field problem, you can prove / disprove that by waving the coil in the air from side to side away from the ground.
                            I'm wondering if there is an Earth field signal if the coil is waved side to side away from ground. Holding a coil on the East and West edges while rocking the coil so the North and South edges go up and down causes a Earth field signal for me. I'm not seeing one when I wave the coil side to side or rock the coil with the East West sides going up and down.

                            Comment


                            • Originally posted by green View Post
                              If it sounds like an Earth field problem, you can prove / disprove that by waving the coil in the air from side to side away from the ground.
                              I'm wondering if there is an Earth field signal if the coil is waved side to side away from ground. Holding a coil on the East and West edges while rocking the coil so the North and South edges go up and down causes a Earth field signal for me. I'm not seeing one when I wave the coil side to side or rock the coil with the East West sides going up and down.
                              I would say, that what you see, is your body field, not the earth field.

                              Comment


                              • last night, I detected 3 hours non-stop with nano. I confirm that I hear the salt in the wet sand .. yet great care has been taken to shield this one ..

                                Comment

                                Working...