[Tesseract]

Originally Posted by Stiive

DTC requires only the knowledge of stator resistance - unless your doing some advanced sensorless speed estimation

I don't know about DTC only needing to know the stator resistance - there are many variations on the original scheme, you know, including marrying it with SVM - but either way the stator resistance changes with temperature and that was what I was getting at when I wrote that it's performance depended heavily on modeling/estimation.

Parameter shift causes all sorts of headaches for both DTC and FOC schemes, so I'm not singling out DTC here.

[Stiive]

Originally Posted by bjfreeman

Yes C. You get a free library you can read on how to use the board.
It comes with header pins to you can put it on a proto board an wire to it. I use header sockets, so I can unplug the board for my different projects.
I use Eclipse as my IDE and tool chain.
here is the forum

Well, so far looks like this is my new choice Do i need a new crystal to get the 168Mhz?
I hadn't done much research on what board/processor to get yet, but this is looking pretty much bang on what i originally wanted. I had been overlooking ARM so far because the last time i used one i had to program in ASM, and it made a job that should have taken a few hours take a few days!

I use Eclipse for Android software development.. maybe i should control my motor using the accelerometer in my phone :P

Thanks for the info though, very much appreciated

[Stiive]

Originally Posted by Tesseract

I don't know about DTC only needing to know the stator resistance - there are many variations on the original scheme, you know, including marrying it with SVM - but either way the stator resistance changes with temperature and that was what I was getting at when I wrote that it's performance depended heavily on modeling/estimation.

Parameter shift causes all sorts of headaches for both DTC and FOC schemes, so I'm not singling out DTC here.

I think you'll find that the original DTC scheme and infact the majority of variants (including SVM) can be implemented with only the stator resistance and its actually surprisingly un-sensitive. I don't see this as becoming an issue. SVM can also be used to help keep the switching frequency constant

FOC is another ball game due to its feed-forward control loop and requirement of nearly all parameters of the motor.

Your absolutely right about the phase-voltage though, and this is still stumping me as i want the HV and LV to be completely isolated. I believe i can rid of this requirement by either using an encoder, or some fancy maths.

[bjfreeman]

Originally Posted by Stiive

Well, so far looks like this is my new choice Do i need a new crystal to get the 168Mhz?
I hadn't done much research on what board/processor to get yet, but this is looking pretty much bang on what i originally wanted. I had been overlooking ARM so far because the last time i used one i had to program in ASM, and it made a job that should have taken a few hours take a few days!

I use Eclipse for Android software development.. maybe i should control my motor using the accelerometer in my phone :P

Thanks for the info though, very much appreciated

No read system_stm32f4xx.c
The reason I chose it is my 56F103 is 16bit 80mhz DSP. The is a 32 bit at twice the speed.

I also build gaming perhiperals so using the accelerometer on a glove with strain guagues on fingers for control, to replace my joystick.
also take adantange of the Dual Can to run the class B an C msgs. Added a wifi on the SPI to allow any computer to hook up an interact through a browser.
I use the SDIO for storage of files on a 16Gig SD.

[Stiive]

Originally Posted by bjfreeman

No read system_stm32f4xx.c
The reason I chose it is my 56F103 is 16bit 80mhz DSP. The is a 32 bit at twice the speed.

I also build gaming perhiperals so using the accelerometer on a glove with strain guagues on fingers for control, to replace my joystick.
also take adantange of the Dual Can to run the class B an C msgs. Added a wifi on the SPI to allow any computer to hook up an interact through a browser.
I use the SDIO for storage of files on a 16Gig SD.

Wow that sounds awesome. I feel like I should buy one (or two) right now to have a play. Even if i don't use it for this project (though i can't think why not), I'm sure I'll find some use for it!

Are you using this to control a motor? Do you have a link to a thread/details?

[bjfreeman]

My current 3 phase AC 250KW controller uses the 56f103.
I just got the STM32 Discovery. Busy prototyping the PCB with Eagle.
I am in the processes of porting over the code, module by module and testing on my new mock-up. I expect it will be tested about this time next year.
this is my overall design. I am HEV not EV. This is more how the commercial guys do things.

[bjfreeman]

you mentioned monitoring voltage. you might find this useful.
http://roadwarrior.free-man.com/can/...anBusway.shtml

[Arlo]

Cool I would like to see the code and some scematics if possible. I can link my BLDC controller thread if you like. I am planning to spend next winter writing code to make it better. I have only just got the code good enough to run it sensored with no feed back (open loop).

[Stiive]

Originally Posted by bjfreeman

you mentioned monitoring voltage. you might find this useful.
http://roadwarrior.free-man.com/can/...anBusway.shtml

I don't quite understand whats going on here.. Both the CSLW6B40M and ACS712 are current sensing modules.

[Stiive]

Originally Posted by bjfreeman

My current 3 phase AC 250KW controller uses the 56f103.
I just got the STM32 Discovery. Busy prototyping the PCB with Eagle.
I am in the processes of porting over the code, module by module and testing on my new mock-up. I expect it will be tested about this time next year.
this is my overall design. I am HEV not EV. This is more how the commercial guys do things.

What control method are you using on your current controller? Whats going to be different in the version? Faster sample rate with the new chip?