Is that a patch? So whats actually broken here? The antispark? Cause I’m guessing the red wire bypasses it entirely?
Check all voltages, VBAT->5V->3.3V that they’re fine.
Check resistance in each half bridge of mosfets.
Clean that gnarly looking PCB. Defluxer or isopropanol should do the trick
I have no idea what broke actually but i guess not the antispark, that one still works.
Ill clean the pcb too 
i had to get it off my heatsink which was a pain in the ass.
These are the results with the 5045 200kv racerstars, as you can see, again 50 mili-ohms too much resistance.
Again, same problem. (Excuse me for the jank setup)
@MartinSp could it be you wired it to the wrong resistor?
i had one like this. it was the first one i got from the raptor clearance shop.
i was told there is an known production issue that sometimes causes this.
and used to be caught when supposedly they actually had QA…
i don;t think you are going to be able to run 2 motors on this…
i still have mine laying around and plan on running a single motors off one side… not entirely sure i can do that.
here is the link on my previous discussion
Thanks for the info @rafaelinmissouri very interesting informatiom you have provided!
Btw i am no guru whatsoever so i have no idea what values to check etc.
Sorry but that is beyond me.
and regarding the values. what i used as a reference was the recommended motor amps. and expected them to be within 5 amps or so.
so mine were way different regardless of which motors i tried.
This jumper wire just connects V+ to V+… it really shouldn’t do anything and can likely be removed. No idea why that would be there, there is a big V+ power plane of copper connecting these.
How weird, do you think the 3 repaired half bridged need to be redone?
Thanks for your help to mister!
Half bride is one leg of the Mosfets that controls a phase. Not sure what you’re refering to. I asked you the check the mosfets just to see if they’re whole, resistance should be in the ballpark similiar to the other side of the unity f.e
Ok will check, sorry, like i said im pretty bad with this stuff.
No problem, if we’re speaking greek just point out what is unclear to you
Would you mind pointing me to the fets and what points to measure? All the components are unmarked as in there are no serial numbers etc on them.
I think it wasnt always this bad actually, i just uploaded this video and noticrd that it worked better, not good at all still but i think it was better?
Im having this exact same issue with two Trampa VESC6 MK3’s that are known-good. I just updated them from fw4.2, where they were working perfectly, to fw5.2, where I am now getting issues detecting the proper motor values and sensors.
I have also now heard from a previous customer that his Xenith is having the same issue.
I think it’s a problem with FW5. I will be doing more testing on my setup to try to figure it out.
This could very well be true,because that film was them running on unity firmware i think
I can confirm that the customer of mine had his issues resolved entirely by switching to using the Unity app and firmware.
@Trampa, I think we found a bug.
