while I’m riding sometimes happens that my motors stop working, like they get only 1 amp, it seems to me that the Focboxes lose the settings. In fact, usually just reflashing the mode from metr.at solves the issue.
The thing, however, is, that if I keep closed the metr.at app I don’t see this issue.
Can be that metr try to do something without … consent lol? @rpasichnyk thoughts?
Here my logs:
Do you have other UART devices? Like UART remote? Or display?
Alright, this is actually something I noticed a few times. Basically when the commands are coming to VESC from different sources (CAN and UART) at the same time, weird stuff can happen. No issues with PPM though.
@Pimousse @Deodand @janpom @Wajdi @Ackmaniac @twan @emmaanuel
I think this is a very nasty problem and it would be awesome if we can figure out why it’s happening.
Just a wild guess. I noticed that when requests to VESC are too frequent, I get rubbish in the response. It’s not that just some requests don’t get the proper response. Literary all requests get rubbish responses unless enough time is allowed between them.
So maybe in case one request comes in over CAN and another over UART at the same time, it’s the same kind of situation. Then potentially the remote could get a rubbish response and get confused and things go wrong from there.
This point is critical for me.
Currently, there is no priority given to a specific protocol over another one.
Say you set the VESC up this way : PPM + UART and “Send status over CAN” and you can drive the motor through 3 differents protocols (PPM, UART and CAN) without any hierarchy.
IIRC, this point has been mentioned, but can’t tell BV’s answer.
EDIT : Vedder promised a new FW with a lot of features (apparently) in the next days/weeks.
This may have been managed hopefully.
Mmm, but happens even when I use the ppm remote and turn off the photon. Do you think the receiver is still sending something even when the remote is off?
There is just as much a Vesc can handle at a time before things go wrong. As @janpom mentioned, once a command is sent, a wait time is needed before getting a correct response. If requests are sent faster than what the Vesc can process, then corrupted data will be an issue.
I thing the vesc needs a better protocol management, especially when communicating through different protocol channels.
However I personally didn’t experience the issue @DAddYE is describing, I’m running the Photon receiver on UART and dual setup on CAN bus with no issues.
Mmm, this is interesting
@rpasichnyk thoughts on my issue?
You already tested with Metr App off. Can you unplug Photon receiver and test with another PPM remote? This way we can make sure that it is neither an issue with Metr Pro nor the issue with Photon remote, but the problem when you have them both.