Recent Posts

Pages: 1 2 [3] 4 5 ... 10
General Electronics / Re: ACS712T Max current
Last post by KeithRB - Today at 11:45 pm
This is all spelled out in the data sheet, but TJmax is 165 C.

so the 40 C ambient + the 25 C rise puts you at 65 C, well below the max. At 20 A, you will run cooler. Just make sure you have the same heatsinking as spelled out in the reference design.
Displays / Re: Problem with custom chars ...
Last post by Alex_Tr - Today at 11:45 pm
I fixed it..
It was the library (liquid crystal),
I reinstall arduino.exe and now works great.
Français / Re: Audio shield vellman KA02
Last post by zoroastre - Today at 11:44 pm

Tu as essayé le code exemple donné à la page de téléchargement ?


Español / Re: es viable cables largos pa...
Last post by gepd - Today at 11:44 pm
Quizás sea mejor usar dos arduinos y transmitir los datos por RC, dependiendo de lo que necesites, puedes usar un arduino nano para procesar los datos y enviarlos, los gastos no son tan elevados, módulos rc hay de todos los precios.
What would be the best arduino for this?  Looking to the best one with lots of inputs/outputs.  I know nothing about this but I'm jumping in anyway.
Deutsch / Re: Encoder macht zuviele Schr...
Last post by SDL-Amiga - Today at 11:44 pm
Das Problem hatte ich auch.

Abhilfe haben, zusätzlich zu den Widerständen, 100nF Kondensatoren geschaffen (3Stück gegen Masse- A/B/Taste).

Ich habe gänzlich auf libs verzichtet und das mit Hilfe von millis() gelöst. Das Ergebnis ist brauchbar, egal welche Qualität der Decoder hatte.

Code: [Select]

void loop()

if (menue == false) {TIMER_MENUE(pin1_1,1,5);} //Aufruf der Taste


/* Timer_Menue *******************************************/
void TIMER_MENUE (int pin, int menue_z, int laenge)
time_menue = millis();

if(time_menue >= (loop_time + laenge))
      // alle 5ms Teste den encoder --> 200Hz
      taste1 = digitalRead(pin); // Read Taste 1 Encoder 1/2
      if((!taste1) && (taste1_1))
      // Menue einschalten   
        if (menue_z == 1)
        menue = true;
        MENUE_START(); //Menuebild aufbauen
        // *****************
        if (menue_z == 2) { menue_2 = true;}

      taste1_1 = taste1;
      loop_time = time_menue;  // Updates loopTime


Damit ist die Taste bei mir sauber entprellt. (Ich benutze diese Taste mehrfach im Menue)

Und hier die A/B Decoderauswertung.
Code: [Select]

void loop()
if (menue == true)

TIME_MENUE_D (pin1_2, pin1_3, 5);

                                TIMER_MENUE (pin1_1,2,5); // Änderung von menue_2

while(menue_2 == false); // Taste gedrückt


/* Timer_Decoder1 ****************************************/
void TIME_MENUE_D (int pin_A, int pin_B, int laenge)
  time_menue_d = millis();
  if(time_menue_d >= (loop_time_d + laenge))
    // alle 5ms --> 200Hz 

    encoder_A = digitalRead(pin_A);    // lese encoder pins
    encoder_B = digitalRead(pin_B);   
    if((!encoder_A) && (encoder_A_prev))
        // A Übergang high to low
          // B ist high --> Uhrzeigersinn
          // increase the counter
          goingUp = true;               
          // B ist low --> entgegen Uhrzeigersinn     
          // decrease the counter
          goingDown = true;

    encoder_A_prev = encoder_A;     // Zustand von A für die nächste Schleife   
    loop_time_d = time_menue_d;  // Updates loopTime

Jeder zweite Rasterpunkt am Decoder bringt ein sauberes Ergebnis.
Und ich verzichte auf Interrups.
Ich habe es so gemacht, dass das Menu per Tastendruck geöffnet und dann erst der Decoder A/B abgefragt wird.
Zeitlich ist es auch in Ordnung und ich kann so nebenbei ein Pegel optisch darstellen.
When I click the arduino.exe file in windows I get a splash screen and then it vanishes.  
Right-click and select "Run as Administrator"

If it continues to do same OR you do not have the Run as Administrator option, your ID may be restricted by a "policy".  Contact the owner or seller of the unit.

Displays / Re: LCD 1602A not displaying c...
Last post by MAS3 - Today at 11:43 pm
My question then - in your language, are the two adequately distinguished?  I'll bet they are.
Got to answer that of course.

Soldering translates to Dutch as "solderen"
Welding translates as "lassen".

But that last word, lassen, can be different things too.
They all have to do with bonding or connecting however.
First thing that comes to mind, is twisting installation wires together using a plastic cover, like these:

Is called lassen in Dutch, but it isn't welding.

I understand you were trying to convey and explain the difference.
The "no idea" part was what triggered me to reply to it.
I don't believe that this is about someone not knowing what he was talking about, just someone who has no idea about the differences in other languages.

Back on topic:
Today i can see the picture.
The wires are the well known jumper wires, they are also well known to have bad connections now and then.
Those wires are not meant to be soldered, and i'd not be surprised if that would be the cause of your problems.
Also crossing wires is more likely to happen if you are using the same colors and it seems to me that you did do that.
I'd use as much different colors as possible, but keep red for power supply and black for GND.
so wouldn't the line ... the same as saying
No. In the compiled code, arrays have addressed. They do NOT have names. You need to purge your mind of languages like PHP that are interpreted. C and C++ are compiled languages. No names!
Pages: 1 2 [3] 4 5 ... 10