Its phobia suport vesc mks 75100!?? With lowside shunt

[artayasa]

Good day mate. Is phobia suport vesc 75100??
Because i see your ptoject is used 2 shunt resistor. But vesc 75100 using 3shunt low side, with ina181 20xgain R 0.005.
Also vesc 75100 not using drv again.
Tha k u for your great projec. I hope u answer if posoble tomorrow i will tested. Just recived my vesc.
After longtime imported, stuck on my country coustem😩

Also if posible i request to add braking resistor mode sir, so when we used PSU we canot gen fault under/over voltage like vesc, or burn the psu😁. Thank u.

I think i will make new board ( big board, i dont like smd pard i dont know to assemblyit, lol🤣🤣.
What do u think if chang ad8418 curent shunt to acs712 30A ( basic this hall curent sense)???
Also for the phasa and input voltage i change the op amp to lm358 or semilar is posible?? Because very hard to buy in my country, if import it will stuck again😩😩😩

[rombrew]

Look into doc/HardwareVESC.md for supported hardware table. You can use FSESC_75100_v2 hwconfig and modify HW_ADC_SHUNT_RESISTANCE if you need. Also you can modify hal.ADC_shunt_resistance variable at runtime.

[artayasa]

Look into doc/HardwareVESC.md for supported hardware table. You can use FSESC_75100_v2 hwconfig and modify HW_ADC_SHUNT_RESISTANCE if you need. Also you can modify hal.ADC_shunt_resistance variable at runtime.

Thank you so much mate, thank u for great projec,
Also add braking resistor mate if posible.

It is no way to build/make the pgui?? I just see the build of firmware.

If i coustem the your board V5, use acs712 as shunt resistor, and lm358 as a voltage sense opamp is posible mate?

[artayasa]

Look into doc/HardwareVESC.md for supported hardware table. You can use FSESC_75100_v2 hwconfig and modify HW_ADC_SHUNT_RESISTANCE if you need. Also you can modify hal.ADC_shunt_resistance variable at runtime.

I was bulild, but alwys show pm error dc link overvoltage mate. I was set on pgui wattage dc link voltage high 150v. But still like that. Whats wrong, i used adc r1 56k and r2 2.2k mate. Same like your default seting vesc 75100 flipsky

[rombrew]

The PM_ERROR_DC_LINK_OVERVOLTAGE error is caused by measured DC link voltage being higher than pm.fault_voltage_halt. By default pm.fault_voltage_halt is initialized as 95% from full scale.

Please collect more info.

1. Run self-test and self-adjust procedures from Test menu button on Diagnose page in PGUI;
2. Grab telemetry on Telemetry page (Menu -> Telemetry grabbing -> Flush GP);
3. Attach tlmgrab.csv and phobia.log files from storage /tmp directory.

[artayasa]

1. Run self-test and self-adjust procedures from Test menu button on Diagnose page in PGUI;

When i click integrity selft test, PM_OK. But when board selft adjustment , Ror Dc link overvoltage mate.

2. Grab telemetry on Telemetry page (Menu -> Telemetry grabbing -> Flush GP);

This intruction just give me like this.

3. Attach tlmgrab.csv and phobia.log files from storage /tmp directory.

I need to attach hire mate??

[artayasa]

3. Attach tlmgrab.csv and phobia.log files from storage /tmp directory.

phobia.log
tlmgrab.csv

[rombrew]

You have broken power stages or voltage measurement distortion (more likely). Try to increase Watch frequency on Telemetry page to 30000 Hz, after that do above steps again and attach files here. I guess there are voltage short spikes in analog path when power stage switches. Also you could check operation at low supply voltage (about 12V).

[artayasa]

Try to increase Watch frequency on Telemetry page to 30000 Hz, after that do above steps again and attach files here.

this file from 50v psu. when i increase watch freq, self test become error overvoltage, not like before only on board adjudtment.
phobia50v.log
tlmgrab50v.csv

Also you could check operation at low supply voltage (about 12V).

also used 12v, nomore over voltage, but now coming over current mate.
phobia.log
tlmgrab.csv

oh yeah my motor is acservo pmsm motor 220v 3A 750w with ABI encoder 2500ppr (10.000cpr)
i try runing with vesc are no problem. i thing i still not familiar in your foc. it because i not setup the encoder??? i need to put ppr or cpr of encoder??

[artayasa]

Also you could check operation at low supply voltage (about 12V).

Also i try with 12v and change the Amper like this fote, its work but now is low acuracy, mybe because less suplay voltage??.

[rombrew]

tlmgrab50v.csv

Looks like ADC reference/supply voltage drops down when power stage switches. All of voltage measurements reached the top. This is a significant hardware malfunction. I could filter out these spikes as a workaround, but not anytime soon.

also used 12v, nomore over voltage, but now coming over current mate.

Too large probe current for your motor.

it because i not setup the encoder??? i need to put ppr or cpr of encoder??

No, it is not related.

its work but now is low acuracy, mybe because less suplay voltage??.

I need appropriate log and telemetry files to answer that.

[artayasa]

Looks like ADC reference/supply voltage drops down when power stage switches. All of voltage measurements reached the top. This is a significant hardware malfunction. I could filter out these spikes as a workaround, but not anytime soon.

Oke mate, today i will test it by battery 36v.
Yess mate i think also, that way i request to put braking resistor mate😁 if in vesc i put lisp code for braking resistor.

I need appropriate log and telemetry files to answer that.

Oke iwill give u now mate.

[artayasa]

I need appropriate log and telemetry files to answer that.

this mate the file.
phobialow.log
tlmgrablow.csv

[artayasa]

Looks like ADC reference/supply voltage drops down when power stage switches.

Still same mate if i used 36v batrery mate. Over voltage

[rombrew]

If we want to do it well the hardware investigation is required. Check voltage spikes and current measurement accuracy.

As workaround:

1. try to enlarge skip after ADC sample in variable pm.dc_skip on page Config, try 4 or 5 us.
2. try to enlarge accuracy fault tolerance in variable pm.fault_accuracy_tol on page Config, try about 30%.