The dudes German from what I understand, they’re alll a little snappy.
3 Likes
You are completely correct in your analysis of this situation. Every single criticism has been met with user error and at the very least should be backed up with a pm and some help. Its brand spanking new and no one is that good at getting a product out of the door first time without issues and the way they fix those issues is customer feedback. Trusted customers with experience in all aspects of how the thing is going to be used.
6 Likes
That’s no excuse. This is an international community, get along it get out. That’s for everyone.
I offered to test it, for some reason no one ever responded 
1 Like
And that my brother is absolutely the worst decision they could have made because if you liked it then so would everyone else given the history. Things need testing in a wide array of environments. To say a remote can be blocked by your body if you ride a certain way is a certain no no for anyone who has any kind of experience. I run all my boards with the receiver as close to my remote hand as is possible so in the event of a signal interference issue it has the best chance of not being affected but I use cheap remotes not something this expensive. You should be able to leave the receiver out on a trailer 50m behind you for the cost. I am not bashing here but slightly annoyed that feedback is not being taken seriously and remarked upon enertion like as user error instead of taking those criticisms on board and working through them. Its pretty @Trampa but get it working properly and use these guys to do that.
6 Likes
Ive used just about every remote in the market. I’m pretty liberal in my praise too. I don’t key my personal preferences cloud the quality of the gear.
An example is the VX1. It’s a solid remote, inexpensive, no major flaws, feels good in the hand. I personally do not like it, that doesn’t make it a bad remotes, just means I don’t like it, that is all.
The biggest hurdle webl as a community have to get over is thinking criticism is bad. Nothing great ever came from a bunch of yes men.
5 Likes
The throttle input signal shown with RT data enabled should be the raw signal coming in from a PPM or UART receiver. I say this, because you can literally see the jitter or lack thereof from this input depending on remote quality.
I think what he means to say here is that the vesc takes this input and it’s filtered into a throttle output control response, consisting of duty cycle/amps in proportion to the input signal.
I don’t have a Wand (yet), but just wanted to add some data here as I have this deck as well and have tested just about every other remote on the market in it.
From what I can tell, the enclosure is a carbon composite, and overall I haven’t run into any connection issues or signal interference from it. My Kaly XL deck also has two thick layers of carbon fiber, and still doesn’t cause any issue. I’ve done pretty extensive testing on these two decks specifically during OSRR development.
5 Likes
Video here illustrating RF blocking by woven CF, apparently CF filled PLA is even worse.
1 Like
I have no doubts CF blocks RF well, however that link is also in context to wireless video transmission, which requires significantly more bandwidth. I have personally experienced this with drone fpv.
In my personal experience testing 2.4ghz radios, the LaCroix Prototipo & Kaly XL deck/enclosures, despite both having CF construction in the deck, don’t have a noticeable impact.
I’ll do some more testing, curious!
1 Like
My interest in this is selfish, as my printed Tx case is made from CF filled PLA.
FWIW what’s the most effective material for blocking RF in the 2.4GHz range?
1 Like
Copper?
Sorry if you felt my reply was defensive, I didnt mean it to be mate! I have no reason to defend anything. The only thing for me is I have tested my one and can say how it is for me and my testing shows me at least that there isnt a problem with connection.
2 Likes
I got a code freeze too. I had stopped to chat to a neighbour. After another 7 minutes I got on the board and started rolling down the hill, only to realise that the Wand had frozen. Had to remove the battery to get it going again.
Benjamin is digging into this issue already.
We hurry up to see what could be the cause of this.
7 Likes
No worries, the FW will get uploaded soon.
We have tested the Wand for a very long time and freezing was never a problem.
We will carefully check the Wand that was reported to freeze and will find out what happens.
Could be as simple as a corrupted FW (bad upload).
Benjamin Vedder is currently coding a feature that allows to download the FW from the Wand and compare it to the actual FW version. This way we can spot such issues.
Today he coded a new FW for the Wand, allowing joystick input signal redundancy. The new FW will take multiple samples of the input signal and can weed out bad signals (e.g. from a bad joystick).
1 Like
I just received the wand, first impression is really nice! I can imagine Frank you are proud with the result.
However please take the feedback seriously. Your product can’t be perfect from the start, everybody understands that. It can in the end, if you better listen, instead of jumping to conclusions.
4 Likes
Could it be rescued by some watchdogs ?
We always do. Benjamin already coded a new Firmware with redundant throttle input reading.
We analyse any potential issue and straighten it out ASAP. There is already tons of feedback incorporated in the Wand product and it continues to improve over time.
6 Likes
That is how you should have dealt with these things right at the first issue. I have no problem with you or your products Frank but sometimes defence is not the best option.
The wife loves the orrsom btw. fml
5 Likes