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

DerelictRobot · January 16, 2021, 3:04am

The issue extends beyond just the battery voltage being displayed incorrectly. It is outright dangerous to run stock fw5.1 on your ESC, because it changes the scaling for the current measurement, which in turn has major implications for the FOC algorithm.

github.com

vedderb/bldc/blob/47c4342808269f3b1b4d3a81925b10e57758e74a/conf_general.h#L274


#define SERVO_OUT_ENABLE			0		// Enable servo output
#endif
#define SERVO_OUT_PULSE_MIN_US		1000	// Minimum pulse length in microseconds
#define SERVO_OUT_PULSE_MAX_US		2000	// Maximum pulse length in microseconds
#define SERVO_OUT_RATE_HZ			50		// Update rate in Hz
// Correction factor for computations that depend on the old resistor division factor
#define VDIV_CORR					((VIN_R2 / (VIN_R2 + VIN_R1)) / (2.2 / (2.2 + 33.0)))
// Current ADC to amperes factor
#define FAC_CURRENT					((V_REG / 4095.0) / (CURRENT_SHUNT_RES * CURRENT_AMP_GAIN))
#define VOLTAGE_TO_ADC_FACTOR	( VIN_R2 / (VIN_R2 + VIN_R1) ) * ( 4096.0 / V_REG )
// Actual voltage on 3.3V net based on internal reference
//#define V_REG						(1.21 / ((float)ADC_Value[ADC_IND_VREFINT] / 4095.0))
//#define V_REG						3.3
// Use the pins for the hardware SPI port instead of the hall/encoder pins for the AS5047
#ifndef AS5047_USE_HW_SPI_PINS
#define AS5047_USE_HW_SPI_PINS		0

I would highly recommend that you make sure it is abundantly clear to your customers that stock firmware is unstable/dangerous on your Spitend Ubox ESC.

The other option would be ensuring that your product is trademark/OS licensure compliant and requesting main branch support through VESC-Project.

hardunclejohn · January 16, 2021, 3:08am

Hi, friends
Too busy to response here in time. now share you what I’m busy with recently.

Due to some key chipsets and MOS are stopped supplying(or supplying with a long long lead time), the local supplying stock parts are crazy cost up, I’m busy with searching and buying reliable parts.
Also keep busy with some known project: the BMS, the single Ubox, the 100V ESC
and meantime, shipping and service support for some customers.
Yes, Too many things, and now I really hard to hire a qualified guy that can help me, I do have two sales girl, they help little on this design jobs.

I may response slower here, but I will not disappear.
Have a good day!

b264 · January 16, 2021, 3:11am

It’s not legal to sell or resell products containing GPL licensed software unless you comply with the license requirements.

Sounds like a lot of cool new stuff!

hardunclejohn · January 16, 2021, 3:11am

Thank you for your reminds. I 'm checking on it NOW! thanks again!

hardunclejohn · January 16, 2021, 8:03am

@BillGordon The source code is published in my website. after spring festival, I will add in vesc-project .

BillGordon · January 16, 2021, 8:10am

Appreciate everyone’s help in getting Spintend to be fully compliant with expected standards.

hardunclejohn · January 16, 2021, 8:15am

I rechecked it today, can’t find any abnormal there. From actual test and feedback in market: The change of 3.44V to 3.3V in the VESC source code solved two problems: 1. battery display discrepancy 2. it well improved overheating .
Surely we welcome market feedback if you’re using my customed firmware, and also the source code is published in my website. when I’m free after Spring festival , it will be submitted to vesc-project.
The most important remind: wear protection well no matter whose products you’re using now.

DerelictRobot · January 16, 2021, 8:45am

What I am stating, is that due to this requirement, if a user is unaware & loada stock fw5.1 on your ESC can cause it to become unstable.

The impact of this being incorrectly set is beyond incorrect battery voltage, and can cause unstable/unpredictable behavior in the control algorithm (linked in my previous post).

Does that make sense?

I think it should be made explicitly clear that running stock firmware on these is potentially dangerous.

hardunclejohn · January 17, 2021, 7:01am

Oh, I see. Yes, a notice is necessary for it. Will make one in our product page. Thanks!

Andy87 · January 17, 2021, 8:07am

For me it solved as well high current cut outs.
With stock FW I got ABS overcurrent faults with motor max setting at 130-150A and suddenly hard acceleration from stand still.
With the custom FW (300A Version) I do not have this problem anymore. Running now 140A motor max setting without ABS overcurrent faults.

Sandels · January 17, 2021, 9:30am

Just curious…What’s your battery?

Andy87 · January 17, 2021, 11:04am

I have no build in battery. All my packs are removable and interchangeable depending on which ride I want to go. Usually 12s2p-4p 5Ah 60c lipos or 12s10p vtc6 on this setup.

Sandels · January 17, 2021, 11:08am

images (4)

Sandels · January 18, 2021, 12:32pm

@hardunclejohn any update on the bms?

Halbj613 · January 18, 2021, 12:32pm

@hardunclejohn how can i wire the switch to two vescs in canbus?
what pins to i connect to both?

luastoned · January 18, 2021, 2:25pm

@hardunclejohn hey, for future remotes could you swap the speedmodes from (H, M, L aka 3, 2, 1) to L, M, H (1, 2, 3) ?

Can you explain how the speedmodes work, or how to change them?

Fosterqc · January 18, 2021, 2:32pm

powering into the top speed mode is to make calibration easier I’m pretty sure.

hardunclejohn · January 19, 2021, 2:52am

Quick click reverse button to swtich H/M/L speed mode.

hardunclejohn · January 19, 2021, 2:55am

It’s in process, hard to say an exact time now. Really sorry for the delay

hardunclejohn · January 19, 2021, 3:02am

Use canbus cable connect two UBOX by canbus connector.
make the two switch button in parallel. (The power-on signal wire can be welded in parallel on a power-on button, but the LED on the power-on button cannot be welded to two LED signal wires at the same time.)