Possibly - but I;m not sure I see what extra information you'd get by doing so?

I would either modify the above code to record the time for every (say) 100 pulses OR record the number of pulses over a given interval?

Martin

It might be missing the interrupt - you have a 300ms delay in the first macro shown (which i assume is the ISR) - this would likely cause your program to fail. It is very hard to tell from screen shots (no macro names etc) - so please upload your code - however, as version 4 is now no longer support...

Flowcode v4 is now no longer supported - can I suggest you try v11 - you will find a lot has changed for the better...

If you need a non blocking delay you will need to get rid of the delays in your code... A timer interrupt could handle things (and must not contain delays)

Martin

Looking at the micro-ROS docs at https://micro.ros.org/docs/tutorials/co ... tion_rtos/ it looks like it might use FreeRTOS as an underlying OS. There are quite a few examples on the forums using this on esp32 - which may give you a bit of a start point.

Martin

Just looking at the AirMar P66 transducer data - and looks like the speed reading is given by pulse frequency (~5.6Hz at 1knot for example). So rather than measuring the pulse length - measuring the number of pulses over a given period might be an easier option? So count rising edges over 10s (or mo...

Thanks - I did mention the memory was getting less reliable with age!!!

Will be interesting to hear how it goes!

Another new year's resolution - organise my Flowcode (and other) projects/life generally better. I was looking for a particular project - and memory not being what it used to be - struggled to find the version I was looking for.... Many of my projects just get thrown in the same directory - and if I...

Thanks Ben,

Yes it would be good if the 'hidden' pins either defaulted to something - I think it's been suggested to have a 'unconnected' pin allowed - that doesn't compile / cause errors?

Thanks Jorgen,

I'll have a play with the LED too - be good to turn the thing off if nothing else!

Martin

Hi Viktor, A simple example - I've assumed that you want to measure the time the pulse is HIGH - but the same can be applied to a LOW signal. The very simple test signal generator - gives equal time HIGH and LOW (here 2s) - though this isn't necessarily the case (and the measurement 'ignores' the ti...