|
Post by Rowan on Aug 19, 2019 19:36:33 GMT
They should be linear, even with the filtering, but there will be some variation across the range. Best to calibrate them to be accurate in the nominal range you'll be be measuring.
|
|
|
Post by colinm on Aug 19, 2019 20:06:02 GMT
One more question, if I use an echook for batttery testing, can I reduce the frequescy of the readings within the code?
|
|
|
Post by Rowan on Aug 19, 2019 21:29:40 GMT
|
|
|
Post by colinm on Aug 22, 2019 10:51:45 GMT
Hi, I changed the transit interval to 15,000 (15s) for battery testing but this causes the BT not to pair to the phone (keeps trying and failing). I tried 3s, same thing but got it working at 1s. It creates alot of data. Is there any other adjustment in the code to correct the BT issue at 15s?
Good news is all the sensors for the car are working and reading pretty accurate after calibrations so thanks for helping me with that.
|
|
|
Post by Rowan on Aug 22, 2019 11:09:07 GMT
I've never tried such long intervals. I hadn't expected it to affect the Bluetooth - I'll have to have a look! Glad the sensors are all up and running on the car though
|
|
|
Post by colinm on Sept 5, 2019 15:47:35 GMT
Hi We’ve got everything working in the car now which is great however the car speed is showing 27 mph on the app but 12 on the dweet feed. Any suggestions?
|
|
|
Post by Rowan on Sept 5, 2019 15:57:40 GMT
The dweet feed shows speed in meters per second, the app shows in mph by default. 12m/s is 27mph.
In freeboard you can add a multiplier to the speed to give you mph, however in dweet it shows m/s I'm afraid as it just shows the raw data.
|
|
|
Post by colinm on Sept 5, 2019 16:03:44 GMT
Thanks Rowan. We guessed that was the case. We’re on Node red now so no problem with the conversion
|
|
|
Post by Rowan on Sept 7, 2019 17:49:19 GMT
Excellent. I'd love to see what you're doing with node red if you're happy to share it?
M/s probably isn't the most intuitive unit but in the background we were trying to keep everything in Si units.
|
|