TMC389+603 basic design

[Yachaan]

Thanks!
1] About the active current control - can you please direct me to some info?

[TRINAMIC_BD]

Processor control will allow you for example a nice stand-still power down, e.g. going down stepwise from run current to hold current if no additional step pulses come within timeout time.
Also, you can use the µC to evaluate coolStep and stallGuard to the best extent (if motor model is known).

[Yachaan]

Thanks!

[Yachaan]

ON THE ERROR LOGIC

With CLR_ERR constant active, you disable the short circuit protection feature, as an error condition will be cleared right upon its detection. But if you cannot add a timerfunction to your controller, this would be a possibility.

I cannot see how the above can be true if "The internal error condition generator has a higher priority than the CLR_ERR input,
i.e. the error condition on ERR_OUT cannot be cleared, as long as the error is persistent."

IT CANNOT BE CLEARED! Please explain

THANKS for the answer below!:

"For the detection of a short circuit to GND, the error can be only detected while the high-side MOSFET tries to switch on. This condition is detected after a programmable time. The MOSFET will not survive it for more than a few microseconds at a time. This is the reason, why the bridge must be switched off for a reasonable time after error detection. If you would clear the error at once, it will switch right away again into the short circuit condition. "

HAVE YOU SEEN THE TCM332 EVAL: the CLR-ERR on the TCM603 is contantly/directly driven by 5V?

Correct, the TMC332-EVAL does not use the error latching within the TMC603. It is handled within the TMC332 chip. But this would not be a safe realization in conjunction with a processor, as it might not react quick enough.

[TRINAMIC_BD]

I'm sorry if you feel my explanations are too cryptic - of course we want to support you to be successful. But, as a first design I would propose in order to make your design simpler for a start, to just work with the TMC389 and a suitable set of MOSFETs which can be directly controlled. This will be very efficient from a design aspect and from board complexity as long as you are in the range of a few Ampere or say up to 8A. If you need to go beyond 10A, your solution with the TMC603 as a gate driver is better.

You will find the sample software for the evaluation board on our server.

GNDP and GND must be tied together - just use the same GND plane on the PCB. The ICs provide multiple pins for some signals, in order to reduce resistance and parasitic inductivity. So, always provide connection to all signals.
For the detection of a short circuit to GND, the error can be only detected while the high-side MOSFET tries to switch on. This condition is detected after a programmable time. The MOSFET will not survive it for more than a few microseconds at a time. This is the reason, why the bridge must be switched off for a reasonable time after error detection. If you would clear the error at once, it will switch right away again into the short circuit condition. Of course you can realize the timeout with a monoflop and you can build the monoflop any way you like (e.g. with Schmitt-trigger gates).

[Yachaan]

ADDING A CONTROLLER:

There are several reasons for me going the route: "solution with the TMC603 as a gate driver is better" - Ill edit this later.
But one big thing for me personaly is - I have lots of time - stranded at home with a boy that needs special care that only I can give.
i AM GOING TO DO BOTH CONTROLLERS FROM THE EVAL BOARDS OF 389 & 603

I have started with the Library file, and updated it with the EVAL 603 Controller STM32F103RBT6 & AT91SAM7X256/518
Also the Schematic - ill update it along the way.

Please scrutinize it carefully, because ill have to throw out a lot of stuff this project do not need.



Q&A's:

MOSFET related QUESTIONS:

1]I changed items around the the mosfets - this is the first area to evaluate.
[The TCM389 datasheet has less items than I have now-I imported stuff from the EVAL's]

I would rathe have ALL possibilities here, because you allways have an option not to populate something you want to leave out later.

TMC-389+602 mosfet.png (207.11 KiB) Viewed 517 times

2] USB ISOLATION & IMPROVEMENT:

I have decided to ISOLATE the USB input to protect my PC - I think it is the WISE thing to do.
I chose the ADuM4160 as it is the best I could find.

THE USB FUNCTIONS ON BOTH BOARDS ARE NOT EXPLAINED - SO HAVE TROUBLE connecting the ADuM4160 CORRECTLY on both boards.
NOTE: I have asked Analog Devices to verify my design on the ADuM4160:


VERIFY AT THIS REF: http://ez.analog.com/thread/14973

USB iso SCH.png (37.59 KiB) Viewed 478 times

[color=#0000FF]USB related QUESTIONS:

SO:
3] What does USB-DISC do on 603 EVAL?
A] Disconect? STILL DONT KNOW-WHERE DO I FIND THE ANSWER? [is it disconnect or discover or connect?] I use it as a pull-up of the ADuM.
B] When if so? Why would I need it? SOMETIMES ITS NEEDED on MCU's
C] Can I leave it unconnected? DONT KNOW YET.
4] & USB-PRESENT? So long I put 3.3V from my USB isolator ADuM4160 on this line... Is this correct? CORRECT YES
5] & on the 389 USB-MONITOR, & USB-PRESENT.
- The USB-MONITOR - I presume - is looking for 3.3V signal from the 5V comming in. CORRECT
- But this is now isolated, I can give it 3.3V from the internal regulator, made from the 5V suply of the board side of the ADuM4160.
- USB-PRESENT: if it gives 3.3V power to activate - like VUSB on normal pheriphiral cards, the PIN connector is the right choice. CORRECT
- The ADuM4130 uses very little power on idle - so it actually do not need that - and I would like to discard what I can.
- IF I KNOW WHAT THE FUNCTION OF EACH IS - IT IS EASY. BUT I STILL CANNOT FIND ANY MENTION & EXPLANATION of SOME........


SERIAL related QUESTIONS:

6] On the eval board, do I need the serial interfase? Or can programming be done through USB too?
I just put in a serial debug port - but can I leave it out too? - NOT NEEDED


OTHER QUESTIONS - relating to things to leave out if not needed:

7] K14 and the pull-up resistors, do I need them? - NOT NEEDED
8] The TMC603 EVAL: - BH1-3 & BL1-3 how do they connect on THIS config on the STM32F103RBT6- if they do? [PA8-10] - NOT NEEDED
9] What is the "ENCODER" and its usage? Can I leave it out? - NOT NEEDED
10] VCC-IO I am guessing it is used to program 389 to use 3.3V or 5V to communicate with the other IC's.
Here is 2 voltages in use - so what is the option to do here, tie it to 5V or 3.3V? HERE IT SEEMS THAT THE MCU IS 5V TOLERANT...
11] On the STM32F103RBT6: Inputs EN-A,B,N is used for what? - NOT NEEDED
12] And the JTAG ? - NOT NEEDED
13] Encoder - This has to do with BLDC - and not with Steppers? If so - I can leave it out? - NOT NEEDED
14] I also do not know if it need to handle the 389 special functions like stallGuard2™........... I PRESUME SO


16] STM32F - Talking to TCM 389
This is the most problematic question for me.
When Using the STM32 controller - how would I connect it to the 389 if I want to run step dir through the USB?
again - see the schematic for my try at it.

My QUESTIONS relating to the STM32 controller IS MARKED ON THE FIRST SCHEMATIC ON THE FIRST POST:

[Yachaan]

The above Q's is very important to get answered

[Yachaan]

Is my ERROR LOGIC CORRECT now?

UPDATED ERROR LOGIC
Thanks to the added controller STM32F103RBT6 - the new ERROR LOGIC is as follows:

a] The BOB controller gives a EN-LOW sinal and it is inverted to High & it enables all and olso this 603 mosfet action.
b] 603 later detects one of the 3 types of errors and sinks EN-to-LOW via ERR_OUT.
c] BOB controller gets notified because it gets an iverted HIGH signal back via TRIPPLE SCHMITT-TRIGGER-INVERTER.
d] It in turn disables all action by HIGH logic.
e] It stoppings all action on ALL DRIVER BOARDS: only the TMC603 mosfets is disabled by an inverted HIGH on the AND gate. EN goes disabled on 603 on all driver boards.
f] Some time lapses.
g] The error condition stops.
The error condition on ERR_OUT can now be cleared.
Then the new Q is: How to clear error automaticly?
603 needs a signal FROM some intelligence or ITSELF that tells that error is cleared to open drain.
h] The STM32F103RBT6 does that via CLR-ERR. - The ERROR-OUT goes HIGH as the Drain closes.
i] In turn one leg of the AND gate goes HIGH.
j] The BOB gets the all clear to send an inverted High to the other leg of the AND gate.
a] back to [a]: The BOB controller does that & gives a EN-LOW signal, to all EN's... It goes high on the 603 and the cycle starts again.

Yes, is OK

21 August THANKS SOOO MUCH!

[Yachaan]

REMINDER: The first post have all the updtated files.[/color]
I marked all or most of my questions there.

[Yachaan]

If I just can get my pending questions answered - I can move to a new level with this.

[TRINAMIC_SALES]

Dear Yachaan,

thank you for your interest in our products. For this advanced level of support request, please send a quote request to sales@trinamic.com. Please let us know your needs and accordingly we will provide a quote on one of the following:
a. Package 1: Hardware review based on given data, closing report (comments and recommendations on hardware)
b. Package 2: Hardware and software review, closing report (comments and recommendations on hardware and software)
c. Customized board level product: according to your requirements (based on STM32 & TMC603 & TMC389, TMCL standard Firmware)

With your mail please include the project data (timeline and estimated volume on prototypes, pre-series and series, expected life time) as well as technical requirements (e.g. motor current, supply voltage, interfaces, inputs/outputs, …).

Thank you and best regards
Trinamic Sales

[Yachaan]

ABOVE RESPONSE BY dear Guido Gandolfo IS TOTALLY INAPROPRIATE to my situation.


Question summery:
My main questions consisted of:
1] How can I communicate with the TMC389 from the controller of the TMC603. And is it at all possible without altering the program.
If this cannot be done with the existing program, I can understand the above. But I stil dont know it can be done.

2] The other questions consists mainly of - what can be left out. Just that!

[Yachaan]

If only I can know if I could control the TMC386 via the TMC603's controller - the STM32Fxx. And how.

At least I can use it as is:
At this stage I can use my Step-Dir input to the TMC389 from my BOB.
The STM32Fxx controller is to control the TMC603 as per Bernhard suggestion.
Then it should work.
I want absolutely nothing remaining from the eval board schematic that is not needed.

[TRINAMIC_BD]

Dear Yacchan, for straightforward questions we can answer always, but you are responsible for your design -
You should be able to do the software for your hardware and learn to change it, otherwise you will not succeed in doing any adaptations. The EVAL software is more a sample than a final application kept as simple as possible for your reference.

[Yachaan]

A reminder:
All I have to work with is this from the datasheet:

TCM389+TCM603.png (103.24 KiB) Viewed 550 times

The controller is not here, and no suggestion is made as to use one or wich one.
THAT IS WHY I HAVE QUESTIONS!
IF ONLY YOU CAN DIRECT ME TO STUFF TO READ - ILL GET FAR, very far.

THEREFORE:
I feel that since this combination is suggested in the TMC389 datasheet - TRINAMIC should supply all the needed info and resources to get this design done right.