As an aside - I've done a little work in the ISR - and in general ISRs should be as short and fast as possible. I've set it to as slow as possible interrupt rate (1:256) (I used timer 0) - but if it runs at 75Hz (maybe using a different timer?) - then the small amount of code here would be fine. Als...

I've done a simple example - with a single LED and button to activate the timer - this will allow you to run in simulation (in v9) and hopefully follow the logic. When the button is pressed - a countdown for the LED is set (I've used arbitary values) - and the ISR counts down - and either lights the...

I was thinking along similar lines as Steve....

Sorry - I don't have Flowcode 4
Martin

Glad you are making headway again.

Let us know how the project goes!

Martin

and https://www.furunousa.com/-/media/sites/furuno/document_library/documents/brochures/brochures/s650_st650.pdf - which shows the 4.8/5.6Hz values - though this might be a different part - it looks to be the same as the Airmar replacement? And the rate is per knot so if your boat is going at 20kts ...

Struggled to find them again......

This gives the 26000, 7.25Hz http://www.ohmex.com/p66.pdf

There seems to be a 'fuller' datasheet - but only on scribd (and I didn't want a trial subscription)

Martin

Got PicoMQTT to run AOK (on an esp32s3) this morning. Compiled the basic_server example (using the Arduino IDE - setting up the esp32 toolset failed multiple times!) - and then connected using the MQTT Client app on Android. Yesterday connecting failed but today it went smoothly - esp32 connected to...

For interest - there is a MQTT server that will run on the esp32 - PicoMQTT. It is quite limited (5-10 connections) and so far I haven't managed to get it to run - but for 'remote' or low-power scenarios it might be a suitable alternative to the power of a RPi.... Having said which - a Pico is proba...

Possibly - but I couldn't get the timed interval component to compile. I got: from D:\Projects\Flowcode\t1.c:20: D:\Projects\Flowcode\t1.c:2433:3: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' Error returned from [avr-gcc.exe] So in theory - you could run a 'check' every 4s (...

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