2021-01-04, 12:04 AM
(2021-01-03, 05:18 PM)topodom Wrote: So, now i think it's clear that it's not coming from the vnh5019, but from motor.ino code.
Yeah, I think it's a software problem.
(2021-01-03, 05:18 PM)topodom Wrote: @ CapnKernel : wichh code version are you using ?
The release done in Dec-19. I'll upgrade when I have some new hardware to play with, although I'm a bit concerned about ironman's report of the PWM duty cycle being too small in newer versions:
https://forum.openmarine.net/showthread....8#pid17558
(2021-01-03, 05:18 PM)topodom Wrote: @ ironman : Tks for the idea, the issue it's clerarer now. But i am not able to undestant the code differences.
@ Sean : i agrre with CapnKernel, an update with replacement of VNH2SP30 in the code with VNH5019. But maybe it's not relevant if the code is not compatible anymore or have to be updated.
I was just suggesting that Sean runs a search and replace in the code from VNH2SP30 to VNH5019 because the VNH2SP30 is obsolete and most of the parts out there are faulty. Keeping it as VNH2SP30 just leads people to failure.