This is to follow up on this post. If you have experienced any restarts, freezing, or white screen, please share your experience here. Video recordings and photos are much appreciated. Thanks guys.
Also, to have some idea about how frequently people are affected by the problem, if you have a DAVEGA X and have done more than 100 km on it, please add a vote on this poll.
Thanks for the update! That doesn’t make any sense though. The 5V on the communication port and 5V on PPM are the same rail. At least on my focbox, there’s continuity. Either the problem is intermittent and you were just lucky on this ride, or it has to do with the connectors on your VESC.
For me, changing the cable did the trick. I still get sometimes the white screen once accelerating or braking, but not anymore on bumps.
Did yesterday a 35km ride, no issue until 200 meters from home, with 15% battery left.
PS: Got to send you back the package, it came back to Prague, guess I messed up the address.
Yea. I’m not convinced about this fix yet. I’m using vesc6.
Not sure if it matters but I have the 5v and gnd plugged in to the master while its tx and rx are connected to usplit then to slave. I could try moving it to the same Vesc?
Interesting. Could you try returning to the original setup and see if the issue has maybe mysteriously disappeared? It might have been just a bad connection. Cable not plugged all the way in or something like that.
At any rate, I’m glad it’s working for you now.
These results are making me think that you have found a flaw in the uSplit layout. Switching the power to the slave ESC’s PPM connector like you suggested is a good test before returning to the uSplit. If both of the tests using 5v from the PPM connectors show good results but the issue returns when on the uSplit, it will be pretty safe to say that’s the issue
I never had any issues in the first 100km. I probably did close to 400km before I noticed any issue.
I first noticed I would get the white screen occasionally after putting my board motors mounts down onto an escalator. But never while riding.
Then a month or two later I would very occasionally get white screen on a ride. Then it became more often, then almost every ride, then 3 or 4 times per ride. I would need to stop and reboot my board to make it go away.
I have also noticed that changing battery capacity from like 90% to 100%, it freezes. Same results w changing the mAh. This is on version 1.3. I thought somehow when we downloaded the update, it got corrupted. I deleted v1.3 after we got back from our ride, redownloaded it and same results. Power cycled in between.
Factory reset and reset settings didn’t help. I’ll post more findings when I get a chance.
Yeah, unfortunately, I don’t think that connecting to PPMs 5V should make any difference (unless there’s something wrong with the connector). It must have been a lucky coincidence that you didn’t get the freezing before. If you could try powering it from something else than VESC (e.g. 1S LiPo or directly from the battery pack using a buck converter) that will likely resolve the problem. Anything that outputs between 3V and 5V should work.
BTW, when you say “freeze”, what exactly does that mean? Is that a white screen or the picture remains on the screen but it stops updating?
I know of memory problems and I’m working on it. In fact, I already have a bootloader 2.0 implemented where the problems have been addressed. I want to do more testing on it before I make it public but if you (or your buddy) didn’t mind being a guinea pig for it please let me know. (You can always easily downgrade without loosing the data if something is not working as expected.)
BTW, did that memory error happen while riding? I haven’t seen that happen while riding. Only when doing things in menu.
Freezing or does it throw an error? If the latter, please send the error details. I have had this reported before. I thought I have fixed it. Maybe not.
Nah, that shouldn’t happen. It’s more like the 1.3.0 is more demanding on memory so the memory errors are more likely to happen than in the previous versions.
Thanks for the report and apologies for the problems. The software issues (memory errors, bugs in changing battery capacity) will definitely be fixed. The hardware issues (freezing), I unfortunately can’t do much about. I still think this is actually a problem in the power supply, i.e. a VESC problem.
The next generation of DAVEGA will have a built-in buck converter so it will be possible to power it directly from the battery pack which should resolve these issues. No ETA for it yet though.
Yes, picture remains on the screen. Numbers are stick. Red blinking light.
Sure. I’m more than happy to try it.
Yes, it happened a few times while riding. In fact, we got annoyed power cycling it every single time so we just left it like that until we were done w our ride.
It gave me an error of “I apologize for the inconvenience. Take pic and send.” Somewhere along those lines.
Oh, that’s actually not freezing then. It merely looses the UART connection with the VESC. You should still be able to access menu and/or switch screens at that point.
Are you saying that if you power cycle, that fixes this?
What kind of VESC is that?
Perfect. I’ll send you the files and instructions later.
Right, makes sense. If you can reproduce the problem, would you please send me the pic. Thanks!
That loss of UART connection is interesting. I wonder if it’s the DAVEGA power cycle or the VESC power cycle that fixes it.
Here’s what I can do. I can add a “RESTART” menu option that will allow you to power cycle DAVEGA without power cycling your VESC. If that doesn’t re-establish the UART connection it would indicate a VESC side problem, in which case you’d need to talk to Trampa about it.
It’s a simple update. I should be able to release it as v1.3.1 tonight.