Go Down

Topic: Digital implementation of a transferfunction, loop/sample-time? (Read 949 times) previous topic - next topic


I am currently working on reading ADC's, performing calculations on these values, and outputting the result from that calculation through a DAC.

However, if I design a continuous time transferfunction/calculation and want to implement that in the arduino code, I need a fixed sample/run-time. If my loop-time is faster or slower than the sampletime specified in the translation from continuous time to discrete time, I have a mismatch between my designed transferfunction and the actual digital implementation of it.

Is there an option of forcing a wait until a timer reaches the set sample time (of say 100us) before the loop is run again?


Have a look at the BlinkWithoutDelay example in the IDE
Please do not send me PMs asking for help.  Post in the forum then everyone will benefit from seeing the questions and answers.


Feb 24, 2013, 10:06 am Last Edit: Feb 24, 2013, 10:18 am by SuperR Reason: 1
Ahh ok, so if the loop is completed, I check if I may rerun it or I need to wait. I presume that this "timer" is run in the background which doesn't influence my computational power/time?!

If that's true, my next question would be;
What way is best/fastest to implement a discrete-time transferfunction/controller?
Do I store the required values from the past or can I use some sort of discrete time variable which remembers the last say 10 values?

In a different topic someone mentioned;

such a formula can be calculated quite well with an Arduino.

float x1 = ((((((7.716 * z - 37.57) * z + 73.23) * z  - 71.39) * z + 34.81) * z - 6.785) * z - 0.001332) * z - 1.96e-008  

This trick brings it down to 14 "simple" float operations instead of using power

Main problem might be that the Arduino only supports 32bit IEEE754 floats with ~7 significant digits.

I really feel like a noob, but since speed/performance is key in my current project, I need to start of well instead of fiddling around in crappy code I would initially write.


It does not run in the background but it does not block other code such as reading sensors or buttons, unlike the delay() function.  So, in your case start the timer, read values from the ADC, which can be quite slow, then, when the timer reaches its limit process the input.  You mention a period of 100uS in your original post. 

You will need to consider the use of micros() in your timer rather than millis() or even using one of the Arduino hardware timers.  There are other members here better placed than me to give you advice in that area.

The check to see whether the 'delay' time has passed is carried out each time loop() or another user defined control structure, such as while(), is executed.

I cannot help you explicitly with your other questions but it seems to me that an array would be a good way to hold a series of values for later access within the program.

I think that you do need to write some code to get you started, however "crappy" it is to start with.  Speed of operation, structure of code etc can often be improved but if there is no initial code then there is nothing to improve.
Please do not send me PMs asking for help.  Post in the forum then everyone will benefit from seeing the questions and answers.


Thank you for your reply. I was aware of the micros() command after reading the example.

Concerning the code, this couple days are to get the info I need to start building the code. Some of the hardware is not available yet so this research is to get a head-start when I finish the hardware.

But, you are right, as soon as I get the HW done, I shall write my, to be expected crappy, code. Maybe the speed of the due is such high that I don't even need speed-enhancement.

Updates WILL come :), once..

Go Up