Hi Steve,
The problem with Node-RED is that I need to have assurance that it turns on consistently as it severly hampers testing if it doesn’t automatically activate the script when turned on. Is there an easy way to turn the Node-RED script into a shell script, or a way to generate a shell script that can listen to the LoRa ports for incoming information and log it that way?
With range, the advertised ranges I am talking about are the ones listed in the mDot data sheet, where it states a 1-3mile (or 2km) in Building Penetration and 16km maximum range. We weren’t expecting to get the perfect results due to signal attenuation, however we were attempting to get at least 5km (ideally 10km) in our rural test from one of the highest points easily available to us, which is about 85m above sea level going off Google Maps. As previously stated, the best result that was obtained was ~3.56km during our testing. This was on a signal that was alternating through DR1 to DR4 and sending GPS Data to the Conduit. Thank you for the information of previous tests, however, it at least gives us an idea of the limits.
As for the mDot Box, I have found that it appears to have a shorter range than the standard mDots and I am not convinced that the survey mode works correctly on the Box that we currently own. As such we created a simple mDot GPS device to send the distance data to the Conduit as this appears to be more effective than the Box.
Regards,