Last post by darrob - Today at 06:09 am
Should be okay.
You will have to ensure that your hardware reflects the changes you make to the code (and vice versa)
Last post by jean81 - Today at 06:09 am
Avant les remerciements qu'il se doit, tu vas te taper mon anecdote ! lol
Moi c'est l'inverse température trop haute et ma crème glacé à la vanille en état liquide !
A déguster avec une paille ! lol
Je te remercie pour ton aide, car là moi plouf !!
does the web editor support pcDuino3B?
Thanks for the tip Leo. Well, It's a RF remote control.
Last post by J-M-L - Today at 05:56 am
May be it's google or Samsung stealing your data for advertising purpose... who knows - as we can't see the code...
--> Don't post snippets... we have no clue what is modifying the variable possition for example... (which would probably be better spelled as position by the way)
Last post by DKWatson - Today at 05:56 am
Polling is generally faster than using interrupts, especially when you know when to expect the event. External/pin change interrupts are best suited for asynchronous event trapping. You could investigate setting up a timer interrupt to poll the appropriate pins, this is how non-blocking serial comm is implemented.
Another thought to not forget (I mentioned it earlier) is the use of __NAKED__ ISRs. Normally when you enter an ISR you go through an exercise called context switching. All relevant registers are placed on the stack so they can be recovered in order to restore the processor to the same state it was in when the interrupt was fired. IF YOU ARE CERTAIN that your interrupt does not disrupt any registers, your can declare the ISR as __NAKED__ in which case no context switching is perform. This will shave about 1us off the time. If maybe certain but not sure, save the SREG when you enter your ISR and restore it just before you exit, still saves time.
Last post by Wawa - Today at 05:55 am
I don't see what difference there could be between a Lego servo and an other servo.
Servo supplies and servo signals are standarised, at least for common/small servos.
However, the array remains full of zeros and does not update any of its values.
In my case, the array's elements are updated correctly with the values of thousand, hundred,..., and etc. However, you have to take care for the consistent data types of the variables.
Last post by npresto - Today at 05:51 am
Many thanks for a great library. I recently purchased a 3.5in display via ebay, connected it to an Arduino Pro Mini (3.3V 8MHz - using UNO pinout connections) loaded up the graphictest_kbv example and ran it without any problems. ID displayed on the monitor is 6814.
I really appreciate your hard work in creating this great library.