as you’re looking at the pin-out check the JST listings for the sensor plugs…
sorry… not sorry,
My guess is that this is for larger industrial applications and not really for us. If your using VESC for robotics applications or things like cable cams then some regulations require emergency stop in order to be operated around people.
6 Likes
Why motors should spin faster?
HV + low kV comes out at the same rpm as low voltage + high kV
I mean yes you can go HV+ high kV motors, but I thought we do not do this anyway.
Edit:
For everybody interested in that voltage topic I can recommend this video
He pretty much just speak about 1-12s but it explains some valid points.
Also explains why the motor kV ratings from the factory not always correct if you think a bit about his words.
We wonder why our motors fail, but we do not mind about correct specs from the supplier.
I mean check maytech motors, they have the same weight, same resistance etc. for different kV motors. How can that be?
Motors should run within a specific rpm limit. Something more which should be written in the specs but I hardly can find that anywhere.
6 Likes
Can you elaborate on what you mean by “crash”? You say you quit the app manually so it didn’t really crash, just stopped recording? Also out of curiosity, can you post the space the app is taking up? Can be found in settings -> general -> iPhone storage -> Stormcore. I’d really appreciate if you post your observations in this thread. Thanks Stormcore for iOS App Bug Reports & Feedback (SERIOUS)
1 Like
Unsure if I understand this question. The voltage reading is… correct? A number? Very voltagy?
2 Likes
I think he means voltage rating.
But what’s the Voltron rating while you’re here?
3 Likes
@sofu no I literally meant voltage reading. Its tolerance and accuracy.
I’m using flipshit and davega is all over the place with it
1 Like
I dunno how davega is treating voltage reading internally but for me it’s a lot less noisy than that definitely.
Is your davega updated to work with FW5? FW5 shifted the ordering of the data structs around so certain things may not be correct
2 Likes
Hopefully. And no nothing has been updated since last year.
As a wise man once said:
2 Likes
The app crashed crashed during a ride but the instance was still there when i double tapped my home button thats when i swiped up to quit it and then reopen it. I sent crash info when it happened through the app.
Thanks, that’s very helpful. I’ll look into this. This is an almost new install right?
Yes, Happened on the latest update. The previous version was working fine and didn’t crash on me not once.
Curious, your crash is happening due to a fix I did to try and correct somebody else’s crash that was happening in the same place. I’ll take a more in depth look at this later today, thanks
Edit: I think I figured out what’s going on. I’m mmap()ing too fast and for some reason mmap() ends up trying to allocate a ridiculous large memory size and the system is saying lol no. I’ll have a fix for this later tonight probs
2 Likes
this is how OSes written by hipsters talk. 
4 Likes
Mine crashed mid ride yesterday. Not sure what happened but sent you a crash report. Worked fine this morning.
Yeah, same issue. I’ll fix it tonight. Sorry about that
1 Like
…when they don’t want to try or need to explain the intricacies of memory management to grunts. 
Us grunts know one thing about memory management. That is how crackers break the code of experts over and over. Fool me once…
2 Likes
It’s like the experts don’t look into what’s the failover response of the hardware or something. 
1 Like