I have a CR6 running at a 1-second scan interval with 4 CS215 SDI-12 temperature/RH sensors and 4 two-dimensional sonic anemometers. Any scan interval below 10 seconds creates skipped scans in my output table. After consulting with tech support, I have tried the M! and C! commands to change the way the SDI-12 sensors are scanned compared to the other sensors with no change. I have isolated the problem to the SDI-12 sensors by removing the other sensors from the program and vice versa. Only the program with the SDI-12 sensors creates skipped scans. The odd part is that the measurment and processing time are well below the 1-second interval.
I would normally increase the scan interval to 10 seconds and call this issue fixed. However, in order to meet the requirements of my analyses, I need the 1-second resolution in the data from the anemometers.
Can anyone shed some light on how to increase the scan interval without creating these skipped scans?
Could you read the SDI-12 sensors from a slow sequence at a slower rate?
That is exactly what I needed! Thanks for the suggestion. I looked into this and all I needed was a second scan codeblock in the main program. I edited my code to include the SlowSequence and now I am in business again.
Hi
The anemometers what output have?
You could decrease the response time of the SDI-12 sensors (notoriously slow, even a few seconds each) with the R command instead of M. With a multiparameter Vaisala probe I solved this, greatly reducing the times but consuming a little more energy .
Also you could read one at a time, every 4 scans, ex. on the second 1 you read the sensor 1 on the second 2 read the sensor 2 on the second 3 the sensor 3 and on the second 4 the sensor 4 and then start again, on the second 5 the sensor 1 and so on. I fear, however, that even with just one sdi12 and the anemometers, you won't stay in the second. Maybe you should use analog sensors.
regards
Smile
Hi Smile,
I have resolved the issue with a secondary scan with a 10-second interval after the main scan with a 1-second interval. I only needed the anemometers to log at 1-second while the temp/RH sensors need 10 seconds. However, I think your approach is smart. The only thing I cannot understand is how the processing time for each scan in my previous program was taking far less than a second, but the logger was still skipping scans.
Weak signal strength or poor cabling can affect data transmission basket random and result in skipped scans.
Run 3 is a popular endless running game that offers a unique twist to the traditional endless runner genre. In this game, players control a character who is constantly running and must navigate through a series of challenging and futuristic platforms suspended in space.
This post is under review.