Question Motor quitting for unknown reason

I have been have a very long running issue with a motor I am using for heave quitting on me.
I have this on its own arduino by itself. I have daisy chained 2 IT-2 motor controllers so it has double the power.
I have swapped out for new IBT2. I am activly cooling the IBT2s with a fan.

It's a powerful 600watt motor (this is it: https://www.ebay.ca/itm/394945206008)
I am using a 1000 watt PSU so it should have sufficent power.

I have attached the smc3 utility screen shot to show how it eventually quits. This is after maybe 1 minute of the sin wave pushing me up and down. Any thoughts?
Thanks!

ps: i have set the upper limits to the max because I am using Simtools to handle the limits

ok, well that sounds positive to me @noorbeast! I was worried it was a hardware issue.
I have tried tweeking the settings in various ways but I am not sure what to try. (I am also noticing now that the actual values didn't show up in my screen shot). I will take a photo of that part

@noorbeast I have the limits set in simtools, fyi so I am only using 50% of the axis in there.
Also to note, I have tried messing with a lot of these settings but the motor cutting issue still remains
- I have adjusted the PWMin from 0 upt to maybe 40
- I tried increasing the Kp to 500- i changed the fpids and the khz

If you have any other ideas of adjustments , I will give those a try tomorrow

Thanks!!

Hey @noorbeast I tried with those settings and it seemed to last a lot longer, actually during my sin test it dxidn't quit at all. Do you think the Fpwm has something to do with the problems I was facing?

@noorbeast in a previous thread you helped me with, one of your suggestions was to set the clip and max limits to 0 and let simtools handle axis limiting (this is the other thread https://www.xsimulator.net/community/threads/600-watt-heave-motor-issues.19074/)
So I am actually only using 50% or less of my heave axis when I am in a game, so I dont "think" I was hitting those limits. But maybe I am wrong. And in the first screenshot i posted in this thread it looks like it dies while just traveling the sine wave.

I will test the change to the Fpwn in a game and see if that was the fix. I didn't know about the IBT2 issue you mentioned, i only picked that higher freq becuase it was quieter but I can deal with some motor buzz if it means it will work.

I will report back and let you know if that was the silver bullet,. thanks again!!

oh sorry @noorbeast !

Your sin wave looks to me like its hitting a limit or maybe is too straight up. It for the most part lags (normal) but at the extremes something wierd happens. Maybe move in manual mode to those limits and see if there is an obstruction or some odd mechanical alignment issue.

@Joe Cortexian I do have 3 of these lift supports to help the motor with my weight so you might be seeing when the motor is starting to compress these perhaps

@Joe Cortexian @noorbeast
So I seem to be in pretty good shape now. I think it was a combination of a few things:
1. Setting the Fpwn to a lower freq so it works better with IBT2 controllers as @noorbeast recommended
2. I also added back the max and clip values as you mention noorbeast, becuase i think removing them based on what the write up you shared, means that I am not making use of the reverse braking
3. I also noticed that my daisy chained IBT2 controllers, only one felt warm after use, so even though they are both brand new, it seems one is faulty, so I swapped it out for another spare I had and now both feel warm so they must be shareing the load correctly.

And at this point I havent had issues with shut down. I also am using smoothing, at 20%. If I remove this I do still get shut down, so maybe thats something related to the motor. But its a small price to pay to have it working

Thanks for the help again!

I really need to figure out how to use those other motor controllers people talk about on here, the Monster ones. They sound like they are a lot more reliable then ibt2s

Do you know if your motor have thermal fuses in them? I had a similar problem where I had one motor cutting out after driving for a bit that would then come back after a couple minutes and die again. I was using JRKs at the time for motor control. I was just using wiper motors, but inside there was a thermal switch that would cut the power if it got too hot. I thought I had removed them, but must not have done it on every motor. Probably better I didn't as it likely saved me really burning up stuff.

In the long run I think my issue was in the PID tuning. On the JRKs I just kind of took a stab at values that seemed to work okay. I swapped them for a Sabertooth/Kangaroo combo from Dimension Engineering as I was planning to use those for a new build and they have a nice PID autotune function. Gave that a shot and my motor temps went way down and I never had any issues with a thermal shutdown again, though I admittedly didn't use the rig too much before taking it apart to reuse parts for my current build.