From what I see the Hoyt Remote fits that criteria but I still would want a deadman switch since:
It’s a nice thing to have when you’re in the middle of traffic and you don’t want accidentally throttle or need to stop and your mind gets away form you. It’s a little lazy to not turn off the remote in the latter situations maybe. But it’s still a nice safety feature that ensure’s the user is truly wants to move and it’s not an accidental input.
For our purposes it can be used for other things if I no longer need it
If I had to take a remote with or without a deadman switch I would take the deadman switch asap. I think some fears come from the deadman switch preventing input when needed but that’s never happened as far as I’m concerned. And if Boosted can do it, we should be able to emulate the same success.
Yes - we are planning support for that. You could help out if you could point us to some popular ones that people already use. We will have our own lights at some point too but we want to future-proof our receiver so it supports those in the future.
Well said. That’s exactly what we want to provide - options. We want to provide the deadmans switch even if only 20% of users use it. Obviously there is some limit to what we can squeeze in the budget but most features that don’t require expensive hardware changes - we’ll do our best to support.
the only feature I could think of that I’d use the dead man switch for is “a balance board” pull the dead man switch, angle the board and bingo… balance mode… throttle the wheel for zoom-zoom… no balance
The usb-c is definetly a nice touch, added with the possibilities of the receiver it could make for a solid remote.
I hope i can connect to the receiver with vesc tool at least (so i can skip a second receiver just for this).
Now what is really important for me and probably others:
How do you implement cruise control?
Is it like vx1, where it keeps the set throttle position and doesn’t care about speed, or,
Trampa/hoyt puck style, where it actually keeps the set speed, let’s say 30km/hr both uphill and downhill/straights?
Other minor ones:
Any plans for a metal throttle wheel with center setpoint? (That cold metal feeling and weight/inertia feels nice)
Sillicone/rubber coated case? Don’t get me wrong but a 3d printed remote is going to look like a 3d printed remote.
Moar battery? (People are putting 1Ah lipos in vx1’s)
Different throttle spring strength alternatives?
Can speed modes change vesc parameters on the fly? (Like max erpm/top speed, max motor amps) if so hopefully custom profiles available in the app?
Just a few off my heart. 150€ is steep for a remote that shows off on the software side
Yes, we already have a working support for it but we are still ironing out the implementation, which is why I didn’t show it off in the video.
Currently there is none. This is quite high on the priority list and we will implement whichever method community thinks is the best. I personally think that setting fixed km/h is the better option and that’s what we have in mind currently.
Easy. Consider it done. It’s gonna probably be an extra / add-on at cost.
Yes, we have plans for the final remote to be painted with soft-touch coating. We will be injection molding for the production version and printing SLS versions for the BETA units - no hobby grade 3D printing for the consumers.
Yes. The one in the pictures is just the one we had laying around. We will try to fill all the empty space with battery for sure.
This is probably one thing which we won’t be able to do. You might be able to add extra resistance to the current joystick but making this a customizable feature is probably not viable for the production version. We’ll look into it - maybe we can have some sort of a hack.
Yes, that’s what the bottom row of profile icons are. These will be customizable on app and possibly directly in the remote too. These will have same config options as in the mobile VESC Tool profiles.
(to be fair, that’s what probably @eriknorth already had in the mind to use, as he’s the one doing the firmware development and me being the guy “hey, I think we need this feature, but I am not sure how to do it in practice, so I don’t know how much it will take to develop”)
Sick! Just got my Focbox yesterday, so we’ll definitely check it out and see when can we implement that. It’s basically a must have feature now considering our logo…
