@Trampa Is there any way to adjust the the min and max range of the WAND trigger? I max out at 31 mph on full charge. Although i only push the trigger upto 60% of its full movement, I max out on speed. This wouldn’t be so bad but there is a significant push back when my board maxes out which sketches me out and has almost made me eat shit. Like i’ll accelerate till 31 and then just stop. If the max happened when I push my trigger all the way up, I could at least be ready for the push back . Right now its so unpredictable i always have to slowly speed up , i cannot just get low and go. I need to be extra careful.
Is there any way to fix the min and max like we used to get for the ppm remotes?
Aww shit man. I’m in Florida. Sorry can’t really help with hills. I can tell you it’ll accelerate until it reaches the speed you set it at. It’ll also brake going downhill
Usually lifetime trip monitors are stored on the ESC and then when the remote connects to it, it syncs the data. That’s how it works on the Revel anyway.
In the case of the applications for the Wand, we use VESC, which does not retain any data except for the settings that we program it with initially. You’d need something like the @WavRX infinity logger to have a lifetime tracker like that. Even then, I doubt trampa would let you get into their code
Anyway, that’s one possible explanation, and who knows, maybe in the future, it will
While not lifetime the VESC can log data. I’m not sure if it can do it without a NRF module but the way it’s set up in the VESC Tool leads me to believe it can. From what I last recall searching, the VESC logs until the Ram Buffer it’s stored in is full.
Interesting, I’ll have to take that back then. I assumed the wand was independent and closed source
I have never seen a DIYer get that ram buffer data before, it would be cool though. If the infinity logger turns out as awesome as it seems then I’d rather just have that though
Yeah I don’t think anything VESC related (software wise at least) is closed if Benjamin is involved. I could be wrong but I haven’t seen ti when it comes to Benjamin.
I got a ride file earlier thanks to kook. It’s not as nice as METR or what I’m seeing from iLogger but it’s nice to have. I’m going to use all 3 for data redundancy and checking. Hoping this project I’m working on makes people utilize the features the the VESC tool has more.
Proper log files are pretty huge, so storing them on the RAM is no option. Also RAM in the chip should not be used to be permanently changed. The RAM suffers from that. A separate logging device is better. Benjamin and I work on a proper solution.