I did, which is why I said everyone is welcome to value things as they see fit.
I’m pointing out that citing hardware component cost here is a false equivalence in a product that is 95% software development in regards to labor spent. BOM cost is largely irrelevant.
Whilst I completely agree with this coming from an EE background, I just don’t think the hardware cost is justifiable at all. I would much rather pay for a subscription or a one time license per module to support the development than to pay this much for a small piece of hardware. Even though I love my original metr and the app works great.
I will definitely document it when I actually start building it. I am currently gathering parts. I’ll move from the US to Finland in the end of May, and I’ll build the board when I arrive there. The main reason for this is the battery logistics…
Yes. Both Metr Pro and Metr Pro CAN. The difference is that first is using UART connection to VESC and then CAN to FlexiBMS. Second is using CAN to both of them.
Already been answered but yes they can. It actually saved my butt a few months ago as i was stuck in a forest at 8pm, 15km or so from home. Got abs_overcurrent faults as soon as i moved the trigger just 1%. Vesc wouldn’t allow any changes but switching between both metr back and forth somehow let me change something so i was able to ride home. Later that day both neoboxes used in that trip died, one forever.
External GPS is a tiny bit more accurate (at least compared to my phone) and has a higher refresh rate (phones OS try to save battery, for example iOS has 1 second resolution). But I don’t think any of it is noticeable in esk8 applications really. Just a small detail.
When you are connected over UART, it is possible to “shoot yourself in the foot” and disable UART through the app. And be locked out. You can not disable CAN the same way, it is always enabled. Maybe that’s what happened.