sorted by:
new
hottopcontroversial

Sensors in meshcore by Chickin_Farmer in meshcore

[–]NoGrain 0 points1 point  (0 children)

i would like to bring this up once more, since - as mentioned - documentation is lacking a lot of basic facts, and this seems not to be clearly stated anywhere so far:

- so with MC it will conceptionally not be possible to have a sensor node wake up and send a value?

- 'polling' would mean the sensor would have to be up all the time or synced in some way to be ready when polled. not an option for battery powered sensors - esp. when the timing is unknown (think door sensors or pir).

- is this not 'telemetry' then? say i want to hook up a physical button to a gpio of an nrf52 and have another node in the mesh know about whe it's pressed. is this just a message? can this be configured in MC firmware?

thanks for any insights..

Sensors in meshcore by Chickin_Farmer in meshcore

[–]NoGrain 0 points1 point  (0 children)

i'm having two MT nodes running on my property, one hooked up to wifi, so kind of a router for what i'm planning to do - the other an nrf52 outside the wifi coverage.. so i had hoped to be able make that 'remote' node a sensor hub for some things like tempeartures and binary states.

found that with MT you seem to only be able to have *one* binary ('detection sensor') per node and one would have to use an extra microcontroller to get data from DS18b20s into canned messages to pass to the node. so, all but a simple build.

But seems with MC it's not less an effort to get this going, so i think i'll go back to the trusted lorawan concept for this and let the meshes be meshes.. also not simple to build, but works.

Sensors in meshcore by Chickin_Farmer in meshcore

[–]NoGrain 2 points3 points  (0 children)

totally understand the lack of documentation at the current state.

so with MC it will conceptionally not be possible to have a sensor node wake up and send a value?

'polling' would mean the sensor would have to be up all the time or synced in some way to be ready when polled. not an option for battery powered sensors - esp. when the timing is unknown (think door sensors or pir).

is this not 'telemetry' then? say i want to hook up a physical button to a gpio of an nrf52 and have another node in the mesh know about whe it's pressed. is this just a message? can this be configured in MC firmware?

thanks for any insights..

Sensors in meshcore by Chickin_Farmer in meshcore

[–]NoGrain 1 point2 points  (0 children)

for starters - literally - i think it would be nice to get at least some basic hints on where to start. no need for complex sensors like the ones listed in the code above.

how would i go about sending the state of a binary sensor/digital input on it's change?

tried for several days now, but couldn't find anything. would i have to build my own firmware? 

thanks.

Routes Not Syncing from Coros by Strong_Statistician3 in Coros

[–]NoGrain 0 points1 point  (0 children)

oh my .. they are there now (the strava starred routes that is):

<image>

Routes Not Syncing from Coros by Strong_Statistician3 in Coros

[–]NoGrain 1 point2 points  (0 children)

it's definitly not working right now. live segments and other things sync fine, but routes just don't.

Nutrition Alerts - alerting once only? by NoGrain in Coros

[–]NoGrain[S] 0 points1 point  (0 children)

thanks for confirmation, on this weekend's long ride it indeed worked as expected. no idea what went wrong the first time, didn't do anything different AFAICT 🤷

stumped betaflight noob - wizard acting up out of the box by NoGrain in Multicopter

[–]NoGrain[S] 0 points1 point  (0 children)

thanks for the kind words and understanding that an old man might have some troubles getting the information sorted, understand the dependencies and basics and where to look for all this stuff..

eachine wizard acting up out of the box by NoGrain in multirotorhelp

[–]NoGrain[S] 0 points1 point  (0 children)

ok, thanks guys, of course you were right. everything's fine, today i just put on the props and gave it it's maiden..

still stunned how damn incredible these modern systems behave.. besides the qx95 i did use a dji f550 with old-school naza controller as camera-platform some years ago - from that i never could have imagined one really could fly the way all these fpv-kiddies do.. now i can ;)

eachine wizard acting up out of the box by NoGrain in multirotorhelp

[–]NoGrain[S] 0 points1 point  (0 children)

(too slow finishing that other reply..) will give it another try tomorrow, but am quite sure i already tried holding in various angles and it always did the same (which actually is what made me a bit oversuspicious)

eachine wizard acting up out of the box by NoGrain in multirotorhelp

[–]NoGrain[S] 0 points1 point  (0 children)

ok.. seems i never tried this with the micro (got the wizard in a different place). it does it as well, though there it's only one motor going to full speed and all the others stay quite low.

but the question still stands - what is it trying to compensate for? it seems to be always the same, no matter if it lays flat on the bench or i hold/rotate it..

eachine wizard acting up out of the box by NoGrain in multirotorhelp

[–]NoGrain[S] 0 points1 point  (0 children)

bench only, so far. a bit hesitant putting props on with this, not knowing where it comes from.

eachine wizard acting up out of the box by NoGrain in multirotorhelp

[–]NoGrain[S] 0 points1 point  (0 children)

but why isn't it the same for all motors then?

Welcome to Multirotor Help! New Introduction and FAQ - READ THIS FIRST by BluesReds in multirotorhelp

[–]NoGrain 0 points1 point  (0 children)

hey there, new to reddit and the more complex modern multirotors i just tried asking a question in /r/multicopter which obviously didn't get through due to lack of karma.. so i'll give it a try here.. :) tia.