Umm, I go with the default settings and only increase stuff if it feels underpowered. Not trying to bust anyoneâs balls. If the main maintained vesc-tool has issues it should get called out and fixed.
@mmaner, what crazy values are you talking about? I have always found them to be conservative. Can you link me? I curious what might have happened.
So I ordered a second receiver from Hoyt St. and it arrived today. Same problem. If I shut off the remote with power still on to the board the wheels spin up to full speed after a 1 second delay (the lost signal timeout). I have also ordered a complete second remote and receiver from Torqueboards (same place my motors and VESCs are from). That doesnât arrive until Saturday.
I did a little more experimentation with the real time data mode in the application PPM mapping settings. I noticed that the input does not jump to full input after a 1 second delay. The input jumps to 30% after a 1 second delay. So I set the input deadband to 35% and sure enough the wheels didnât turn when I shut the remote off. After a 1 second delay the input jumps to 30% and stays there. When I turn the remote back on the input falls back down to 0 +/-2%. Bizarre.
The remote has 3 modes. The input only goes to roughly half scale in mode 1 but full scale in mode 3. Doesnât matter which mode the remote is in when I shut it off. The input always goes to 30%.
Some day you will wish they would stop dropping.
You may have done this already. Try thisâŚMake sure your trim is at center. Then rebind it again?
Iâm using the Hoyt. I donât have any of the issues youâre having. I wonder whatâs different on yours vs mine. Too bad I get off around 1230am. Otherwise, Iâd let you use my spare remotes.
I have been through the setup so many times I can do it blindfolded. I have done it with two different receivers and the same result.
I did that. Itâs all in the other 2 threads, but Iâll link you dinner data when u get home.
Bummer to hear I made my RX/TX so serial debugging was a bit easier but being the only tester had down sides (destroyed a board because of throttle runaway) but for an off the shelf or out of the box product it shouldnât be so difficult. Whatâs your idle value sorry know we saw this but I forgot is it 1.75ms it might be that the receivers are sending the correct idle (1.75) but the transmitters range makes idle too low.
Nope. Spring trucks generally have the same pattern but urethane trucks like MBS matrix 2s use standard 4 bolt pattern.
These are the auto detected values assigned by teh VESC-Tool Wizard on my FlipSky FSESC 4.20 plusâŚ
Hereâs my log attempting to use VESC-Tool 1.13âŚ
9:12 AM 6/21/2019 attempt to update firmware on all devices using can bus, result is buffer erase timeout
9:16 AM 6/21/2019 attempt to update firmware on master, result is successfull
9:17 AM 6/21/2019 attempt to update firmware on slave, result is successfull
9:18 AM 6/21/2019 autoconnect > setup motors FOC
mini outrunner (~75g), Liion 10s 12ah, 18/36 100
run detection
9:22 AM 6/21/2019 it appears to have completed, checking values
9:24 AM 6/21/2019 Motor > General > General - BLDC, not FOC
Motor > General > Current - WTF! I dont even think this thing will ride with these valuesâŚ
9:27 AM 6/21/2019 Motor > BLDC > General - Sensor Mode is reported as Sensorless, incorrect
Motor > FOC > Hall Sensors - sensors values are correct, why no sensors detected?
9:30 AM 6/21/2019 this is unpredictable, not safe, going back to Ack firmware
I get equally crazy wizard results with x2 FlipSky FSESC 4.20 plus, x2 FocBox, x2 TB 4.12 VESCC and x2 VESC-X. There are others getting unusable results as well, quite a few. I wouldnât ride a board with those values, hell I wouldnât put Frank on a board with those values 
.
Has anyone seen this?
Seems like a dual 6 vesc variant for 200 bucks. I only see 2 capacitors though which is probably not good.
I like the specs, itâs a value for the price. I donât like the lack of can control or the built in receiver.
The detection is not the sole determiner of those values. It canât be because it doesnât know how big of a battery you have and how big of a motor you have. So can you tell me what motor size did you choose before starting your detection. Also the battery specification. If you entered the mass of motor to be less that itâs true mass class then it will restrict motor current to prevent overheating of the motors.
Otherwise I can do a complete detection from scratch and post my results here. Letâs see if I find anything crazy.
Locked to one remote
Integrated switch 
will that one last?
I like the cute phase wires, but iâm not sure if itâs good that the phase wire is hanging over that resistor or what ever it is
Also, does anybody know what they mean with:
â Solve the problem of easily burning MOSFETS when instantly braking electric skateâ
It could as soon as you need to select your battery type and size. To set the bat min and max values automatically to a crazy high value is not good at all. Yes you can change it manually, but thatâs not what the new wizard makes you to do. The new wizard makes new people to think your settings are all on point automatically after running through the setup routine.
Not sure where to read idle value. I see 1.75 ms for pulselength end. I see 0% on the input around 1.45 ms on real time app data.
Since the problems all start after the lost signal timeout, I am guessing they are in the setup or VESCs rather than the remote or receiver. Since it always jumps to 30% I am thinking firmware or setup problem rather than VESC hardware problem.
I tried doing uploading the firmware again and doing the setup without having it start with the standard settings. No difference. I went through every screen looking for anything set to 30%. The only thing I found was Motor Settings/FOC/Advanced/Observer Gain at Minimum Duty. Changing that to 15% on both VESCs did not change the input after shutting off the remote. It still jumped to 30% after the timeout.
If your values arenât close to 1.00 - 1.50 - 2.00 thatâs indicative if the issue. If your to value is 1.75 I would assume you have the review in a lower mode than full.
Under App Settings/PPM/Mapping/ I am looking at:
Pulselength Start 1.238 ms
Pulselength End 1.756 ms
Pulselength Center 1.449 ms
It doesnât ask or the motor kv, but in this instance they are maytech 6374 190kv motors. In other instances where I also got crazy detection results I used 6374 190kv and 6365 200kv motors The rest of the values are specified in the message above.
mini outrunner (~75g), Liion 10s 12ah, 18/36 100
Frank advised that almost all of the motors we use are mini outrunners around 75g, so thatâs what I used.
The real issue is that battery and motor amp values need to take gear ratio into account. All of these values are rarely going to be âgoodâ without using that ingo in the formula.
Hit the mode button in your remote until it vibrates 3 times, then rerun ppm detection.
