Spintend 75V/200A Ubox (Based on 75V/300A VESC)and Uni1 Introduction !

None of my lingyi boards had that feature… the main one I spent time on was an ecomobl ET. Just felt like there was so much input lag, it drove me insane

2 Likes

@No, we don’t provide firmware for BKB’s lingyi remote. their ESC is not based on vesc, they can’t use our remote firmware for it.

2 Likes

for the Uni-1 remote you had to replace the main PCB of the remote correct?

at beginning, we don’t have our own case, so we replaced lingyi remote with our own pcb, now our un1 v2 is our own case, which has light/horn button.

3 Likes

Guys, Happy New Year! :heart: :heart: :heart: :heart:

5 Likes

And about Voyager remote issue is : we received BKB remote sample for analysis to find BKB added a case for receiver, and fill the case with hot glue . The hot glue may influnence the receiver touch pin connection, since the cable and pins are not soldered, the hot glue( or potting) may fill in it. While the voyager sold in our website has no receiver connection problem, we don’t do any potting or hot glue for the receiver, it’s naked with heatshrink. cable connection is no risk.

And we added csutom firmware that support “TANK MODE”, it means you can run wheel at any angle you want , but please leave a note if you want tank mode, if you don’t leave a note, we will ship with standard firmare that don’t have tank mode.

3 Likes

And if you rightly had a BKB voyager remote, you can take our uni1 remote receiver only, they’re compatible, and no connection risk . is it a way to save your voyager remote ? :innocent:

1 Like

Ah, you mean for tank mode for Onewheels using vesc… Correct?

1 Like

onewheel only have one motor, it doens’t need tank mode. you can turn left and turn right you want. I will show you video what tank mode is: two motors , run at any angle you want

6 Likes

Question hive mind pls.
Not used it for a couple of years so firstly . Are these still deemed safe or best avoided?
Also, my antenna wire has snapped . Can I just solder it or is it somehow special? Many thx

1 Like

How do I know which software version I need? ubox v2 is probably still a 100 volt version.

That is a very small coax cable, you need to buy a replacement. There isn’t any good way to repair it. I have been using a V2 ubox for a bit and it seems fine to me. I think the specs on it might be a little optimistic and as long as you keep a 15 to 20% headroom on your voltage and amperage, you should be able to get some good life out of it. It’s not as high of a performance as it initially made out and people had some bad QC issues I think.

Also firmware is not software - don’t update it until you have to. I have mine on 5.2 and it works great. 5.3 gave me headaches and 6.2 was an absolute disaster. Keep it as is unless you have no other choice.

1 Like

Wathe is the problem withe 6.2 ?

Biobaurds vesc i think she all install new vesc the 6.2 !!!

1 Like

That’s the magic, i had problems but others didn’t. Getting vesc to act right is a magic trick so don’t mess with the alchemy if you don’t need to. I had issues with settings reverting to default randomly and losing my motor settings and detection halfway through a hard turn and all kinds of weirdness. 5.2 was just boring and worked so i haven’t touched it in a year and that’s the way i like it - id rather ride than mess around on a laptop :grin:

1 Like

I shortened it and crimped the connector back on. Seems ok … for now

That’s the antenna and balancing and tuning them is way beyond me, i just know never to turn on a transmitter without one or it could fry it… don’t ask me how i learned that lol.

Hopefully it works out for you, i have trust issues :grin:

1 Like

With the vesc tool I can now directly flash the latest 6.2 or 6.3, correct?

Supposedly, but I wouldnt tempt fate… Just get it from spintends website.

3 Likes

I went to jump on my flux today and it gave a stutter without input from the remote. Not a fan of weird so propped up the board to run input calibration. No wheels turn. Fuck. put it down to vesc life and do it all over. One wheel turns but stutters. Shit. Ok… gunna be like that is it… Detect motors, both run. No issue. Rerun input. One side but cleanly.

Rage quit, go and play population one for an hour till the kids get back. Kids, dinner, bed … right.

Laptop out, connects first time via external usb jumper, pats self on back and praises all the gods that smiled apon me for allowing it to work… repeat the cycle… WTF…

Now i have to wonder how much fucking about its going to be and if I shouldnt just shortcut the whole thing, jam a DV6s in there and move forward. Its old, its now being funny… i have a spare one somewhere I think… :laughing: is retiring them before they go puff puff a thing? Maybe i can keep it as a spare and put it in an external case.

did you perform visual inspection of motors and esc ?