Tutorial SMC3 Arduino 3DOF Motor Driver and Windows Utilities

Thank you for your response. @RufusDufus , @Pit New are on their way.

Hi guys,
I'm using the IBT_2 with a arduino mini pro clone and 2 x 350W/24V motors (12v powersource), and its working just fine.
The bridges don't even get warm . i'll also got the motomonster shield but all is working fine so i don't see the need to replace them. (never change a winning team )

And why do then one IBT-2 H-bridge gone? Everything I have been connected according to the diagram. It is also involved in even the kind that works.

Why only 12 V powersource?

1 only have a 12V powersupply, i prefer 24V but aint got the PSU for it, thats why
(and it works perfectly, so why bother )

The 24 motors powered by a 12V PSU will definitely working, but the power output will be greatly reduced. PS: (better explaining) the motor will turn at half the same speed at the same load.

Your completely right! yes they will turn at half speed, butt until i have a 24V PSY i'll have to do with the 12V

Hey guys, I have a problem connecting the motor to the simtools app.

Got SMC3 , moto monster, and the MCPmotor. the SMC3app works great, moves well and everything ok.

When i turn simtools on, and set it as explained on first posts, my motor moves suddently to 5 positions. 0%, 25%, 50%, 75%, 100%, in terms of position. No smoothing, As I move the slider on the axis testing screen, there is no movement until the bar is moved even more.

It should have 1024 steps right? I have 5 hahahaha

SMC3app on manual works great.

Also, I'm having PSU shoting down when moving via simtools. Its 70A at 12v........... no shotdown with the SMC3app, even in motion with load.

Thanks

Hi @CalSim, Have a read of post #393 on page 20 of this thread and see if sounds like your problem.

If it does there is two solutions...

1) Use recently released new version 1.3 of Simtools

2) Set your windows localisations to use English number formats (examples given in previous posts).

Hi Rufus,
If i want the third output to control a tensioned seatbelt, what considerations to follow?
Can it be fast while still maintaining linearity?
I mean that to be fast it needs a high Kp value, but then it may lose linearity, because to minor changes it reacts with full power. Maybe in this function you don't need speed at all.
There is nothing available on motor controlled seatbelts.

Hi @Thread, that shouldn't be a problem. The SMC3 PID loop should have no problem doing that.

The Kp is multiplied by the position error, so if the error is small the output drive is small. You can also use Ki and Kd if you are getting overshoot etc, but would be surprised if you need that precision for a seatbelt tensioner. I haven't tried a seat belt tensioner but would assume you want smooth motion not jerky, so probably want some smoothing applied in the simtools output axis settings.

I gave up on the idea, first i thought that a free-rolling motor would do, one direction only, but because of the gears, it won't loose back easily, so it has to be a feedbacked system, not necessarily limited to 180 degrees though, you can use a spool.
Has anyone seen a working one?
What is the advantage over the simple spring method?
I guess that pitch and surge can be more differentiated, you can maintain a 200kp force on the belt as if braking with several G-s.
Don't know, maybe simtools should provide a separate surge for this, it can be scaled more freely, but i am only guessing.

Thanks @RufusDufus Did it and it seems to work. Rebuilding now to decect the source of another fail.

greets

Well this is my fail right now.

The code, or the arduino, something is missing.

It works as it should, but sometimes the motor "misses" the target line.

Pot works, as you can see in the photo. I was using the manual output mode.

When I just move fastly the blue dot, the direction is missed. Same happens on real fire on a game. To get it back, I have to put the target line OVER the green pot line, then it takes the signal back and follows as spected.

See the graphic and judge yourself.

Whats wrong???




thanks

Hi Guys,
I have a wierd problem, after intensive driving the rig stops.
The problem is the Arduino pro mini (with SMC3 code), the thing just blew up .
Replaced it and its working again, now after a few weeks of driving it happens again (grrrr)
Anybody seen this before??? looks like some sort of spike or something like that.
I'm thinking of filtering the feadback pots and powerlines with some capacitors and maybe shotky diodes for protection.

Check check and recheck your wiring, it solved most of the problems I had . Only reason I can think of that an Ard would blow

It sounds like the same problem I had, it was the motors drawing too many AMPs making my motomonsters shutdown for a second making the motor stop and it restarted once I aligned it again. I just ended up using 1 dual motomonster for 1 motor it solved the problem for me. May be the same issue but I dont know what your setup is ?

ps Have you tried a lower PWMMax say around 150-160 ?

@SilentChill I made again all connections, changed main wires, now AWG14, sanded all pins.

My motor is big, but people drive the same and even bigger ones with mm. It is the motioncontrolproducts ZYT-90, its 23A constant 48 Apeak, with 60:1 gearbox
I really dont think ( i hope it wont) the motor is crashing the mm, beause i'm using 1 mm in dual mode, to drive 1 motor. My PSU is 70A and it shuts down if PWMmax > 180 ( With Kp500 )

I did not know motomonsters have overdraw protection. just thermal protection. When signal is lost, the mm is still on since i can see the red led. If i have reached the max power of the mm, this is definitely not proper to drive the motor.

What kind of test shall i make, to ensure this is my issue?

Maybe @Pit, that works with mm knows this issue, or @RufusDufus can have an idea of whats happening.

Really, Thanks

Could the Arduino pro mini be overheating?

Set KP to very low (saying 80) and raise PWMmax from 150 to 255 for testing with (always same testing procedure if possible). After done please report any issues.