Hi there!
Advice welcome
…
Setting up a fungineers Thor 301 with their 20S2P P30B, with a GT-S hypercore w mte 5” N52 hub in a XR WTF chassis and avs laser beams w converter.
Resolved: a modified stator to rail connector (due to the longer motor axle of the GT-S motor vs. XR) and the exchange of the motor connector in the controller box to an Avaspark GT Thor connector adapter.
Despite following advisory videos of Jay, Surfdado and Onedadonewheel… Unfortunately the setup of the Thor301 with the new Vesc-Tool (Aug. 2025) went nuts…
First day the laptop (win11x64) properly allowed to connect via USB-C and updated the FW in the Thor to 6.06, the motor setup went nice and the IMU setup failed due to a timeout issue. Shutting down the laptop it automatically received some Windows update and the next day the laptop failed to get the Vesc tool started. Several Windows workaround and re installations w/o success. The vesc tool now runs but somehow can no longer access the BLE interface of the laptop.
Then starting the VESC-tool on iPad, it connected via BLE (USB-C no connection): two BLE devices were found (but no “Thor301”). Once one of them connected, one BLE device appears as “VESC Express T” and the other as VBMS32micro …the BMS. CAN scan finds no others. Subsequently the motor setup finally fails to detect the motor. Disconnected the Thor from the battery.
Once switched on the power button, the Thor301 after some seconds beeps once and shows its onboard status leds on. Depending on the duration of hitting the power button, the different LEDs (front, rear and status bar) sometimes start to light and sometimes they all stay off…
Next day tried the vesc-tool on iPhone …same result. Running the Vesc tool on Samsung android mobile: no device found at all.
Never give up ![]()