Pages: 1 [2] 3 4 ... 10
 11 
 on: Today at 02:10:38 pm 
Started by JacobJT - Last post by JacobJT
Quote
There's a very simple way of finding out. . .

I misunderstood, sorry.  I thought you were telling me that the statement should always be false, which didn't make sense because it obviously evaluates to true.  I did misuse the logic, but it does have the same effect that I want.  I could leave the logic at 421 > delayLeft to get my intended result, since that is going to be true until delayLeft rolls over.  At that point, 421 !> delayLeft, and 0 !> 0 so the statement is false.  I'm just going to get rid of the > 0.  Sorry for the misunderstanding, and thanks for the info.

 12 
 on: Today at 02:10:14 pm 
Started by marcovaldor - Last post by marcovaldor
Then you mean that the arduino is dead?
and what solutions do you think would work ? Could you plz use more simple words , I'm new in arduino .

 13 
 on: Today at 02:07:05 pm 
Started by doctjh - Last post by polymorph
No. Most MOSFETs are rated for a maximum gate to source voltage of 20V.

In addition, you said it was a 60V MOSFET, yet you are supplying 112Vdc.

The 10k resistor is going to mean a very long turn on time, resulting in a lot of heating in the MOSFET.

Is this just a typo and you meant 12Vdc?

 14 
 on: Today at 02:06:51 pm 
Started by georcon - Last post by olikraus
I have seen a lot of timing problems with the ST7920, but they usually look differently.
Is there some flicker, or is it constantly looking like this?

Can you modify the HelloWorld example, where you enter an infinit loop after the first picture loop:

Code:
void loop(void) {
  // picture loop
  u8g.firstPage(); 
  do {
    draw();
  } while( u8g.nextPage() );
 
  for(;;)
    ;
}

How  will it look like?

Oliver

 15 
 on: Today at 02:06:39 pm 
Started by hyalite - Last post by hyalite
Surfer -- I am pretty sure I did upgrade the firmware per the arduino wifi shield websites specs ... I did that about 2 months ago or so. I also did see the post you referred to, but those guys are getting 90 bytes out ... I'll go and try to update the firmware again, as my memory has failed me on more than one occasion.  I can probably live with 90 bytes of data. Thanks for your suggestion, and I'll post back as to whether it worked.

 16 
 on: Today at 02:04:44 pm 
Started by calvingloster - Last post by calvingloster
Just slow down abit please, I don't even understand pointers. And believe me I have been reading my balls off and I just don't get it.


Also what is the difference between a normal array and a uint8_t array?

Char normal_array[] = "programming is difficult"

Now what is a uint8_t array? What does that even mean?

 17 
 on: Today at 02:04:41 pm 
Started by EugeneDumboinc - Last post by EugeneDumboinc
Hello everyone!

Let me introduce myself first. My name is Eugene, I work in a startup incubator located in NYC. My goal is to make the incubator better, acquiring some interesting and useful devices and stuff.
 
Recently, I have found this project on the Kickstarter https://www.kickstarter.com/projects/botfactory/squink-the-personal-electronic-circuit-factory?ref=card

So I would like to hear your opinion on this printer, since you guys are experts in this field. Is it worth the money? What do you think about this printer?

Many thanks,
Eugene

 18 
 on: Today at 02:02:33 pm 
Started by renaudbedard - Last post by renaudbedard
Hey! Glad it piqued your curiosity. smiley

To answer your questions :
- Yes, coroutines have read/write access to global variables. Since they run "on the main thread" (there's no multithreading), the usual warnings of race conditions and atomic read/writes or what have you do not apply, it's all safe.
- You can do conditionals and any kind of inner loop you want inside of the coroutine as well.

However, the sketch as you wrote it would not work, because you use delay().
Coroutines will only run in as a result of calling .update() on the Coroutines<N> object, so if you use delay() in your loop method, they won't get called in the idle time, unfortunately. One could override delay() to make it do that, but it makes it hard to read and understand. What I'd suggest instead is to move your loop() body to another coroutine, which would be able to interrupt itself with COROUTINE_YIELD at various points in time.
Same goes for delay() calls inside a coroutine. You should use coroutine.wait() followed by a COROUTINE_YIELD which effectively does the same thing, but makes sure the rest of the program can execute while your coroutine waits.

I'm not sure I understand the function of the delays in your loop function, so I don't know how to suggest a functioning way of doing what you want to do. In pseudocode or comments, can you describe the flow of what you're trying to achieve?

Cheers,
Renaud

 19 
 on: Today at 02:02:26 pm 
Started by Kannan - Last post by raschemmel
Did you research quadrature encoder code ?

  https://www.google.com/webhp?sourceid=chrome-instant&rlz=1C1GPCK_enUS504US504&ion=1&espv=2&ie=UTF-8#q=arduino%20quadrature%20encoder

 20 
 on: Today at 02:01:28 pm 
Started by doors666 - Last post by doors666
the println i had just put for debugging. Is there a way to get this to work with some inerrupt enabling disabling or setting interrupt priorities etc. i dont want to set a variable in the interrupt handler and check it in the loop as the main loop is a few microseconds  and this periodic interrupt is once every few seconds. I will be unnecessarily checking the flag way too often in my loop.

Pages: 1 [2] 3 4 ... 10