Search results

Time is supposedly relative, what is a few weeks in a 1Ghz core ��

Ok I do have a question for you Have you, or someone else paired the T4.0/T4.1, used for BLDC commutation, with a motionsensor eg. 9 axis? Somehow I have this inclination towards doing a ebike motor controller coupled with a fast motionsensor and a external ADC. Since the new 1176 MCU will...

Are you saying the T4.0 does have this option and that the product page showing the FlexPMW pins does not tell the whole truth!? Awesome ! Edit: I think I must have mistaken something in the deadtime concept. Thought we had to use all 6 pins within the same FlexPWM. From your post, im guessing...

Voting for 6 complimentary pins on a eFlexPWM as to use deadtime insertion for BLDC commutation purposes. The dual core nature of the RT1170 makes it very cool for having the 1Ghz core work on the motor and the M4 do the communication/ HMI Definitely room for future progress in ebike/eMTB...

The T4 has some very nice deadtime insertion functionality on the eFlexPWM, but the pins are not broken out in pairs. Bummer, I will have to solder wires to the buttom side SD card footprint to use that function. At least I think so. One will need 6 pins on the same FlexPWM in pairs of A and B...

Holy crap she’s fast! “Yes, the FlexIO peripheral runs happily with the 480 MHz clock source, but as far as FlexIO is concerned this translates to 480 million timer edges per second so the fastest data rate is 240 MHz since the data is shifted on either rising or falling timer edges.” Source...

Looking at your FlexIOSPI.cpp, it does look pretty configurable. Since the output of the AD7387 device is in sync on the two MISO lines, I suppose one would set up two DMA channels using the same trigger. Is that possible? The second MISO line would in a sense just be a clone of the first doing...

Ah, I see it uses DMA and has some sophisticated timer, triggers, sync, so on and so forth. Would be worth a try. https://github.com/KurtE/FlexIO_t4 I see a use case for SimpleFoc FET pins on the same timer. Usually a challenge to find 6 pins on the same timer, if doing 6 pin PWM switching...

I wouldn't know, have no experience using flexio yet. I would think hardware SPI lines has some additional functionality. It would be a plus for Teensy 4.0 use, not having to use two SPI ports, even though it is broken out, the second port is on the bottom side SMD footprint.

I concur, in theory it should be possible to use the AD7387 on all three SPI ports. The CS pin triggers the sample and conversion and depending on settings the data is send on a single line or dual. So it will work like a normal SPI device, but has the option to go dual, when configured...

Hi KurtE Just found this other thread where you mention the regular SPI ports might have DUAL capabilities. Did you find out, if the pins are broken out on the T4.0 or T4.1 for that? "Then there are the different normal SPI ports on the boards which we use for SPI, SPI1, SPI2, which are made...

@hat Can you confirm the above method? Did you get the dual MISO SPI to work. Im looking at the AD7387 ADC, with 4MSPS and up to 16bit resolution (when oversampling) for sampling a 1Mhz current sense amplifier. It has the same two MISO lines for faster throughput.

Can someone point me to the optimal cutoff freq. when designing a anti-aliasing filter for the Teensy 4? The way I see it, and from what I have found on the forum, either I implement a anti-alias filter or use a external ADC (which could give higher resolution). Would it be reasonable to use...

Mkay, so im looking @ the datasheet page 56 (https://www.nxp.com/docs/en/nxp/data-sheets/IMXRT1060CEC.pdf) If ADHSC=1 then the sample freq will be 20Mhz, which means a bit higher current consumption then if set to 0. Then I set the sample cycles to say ADLSMP=0, ADSTS=11, which takes 8 cycles...

I have been experimenting some with the SimpleFoc repo. and are ready to take the great leap onto the modular approach of using Teensy 4 for a custom BLDC controller design in the making. Mainly the project is for ebike/eMTB motor control. Here is a thread on SimpleFOC community regarding this...

What is FOC (Field oriented control) https://www.youtube.com/watch?v=Nhy6g9wGHow&feature=youtu.be hmmm.... that´s another way of FOCíng I made a repo here : https://github.com/Juanduino/Beefy-BLDC-3phase-Powerstage-T4 See this...

Hey Since the SimpeFOC lib is under heavy Development i would like to revive this thread. (https://simplefoc.com/) I have been doing work on a 10kw (300amp) EVnode w. CAN FD. The SimpleFOC lib. does not support 6pin pwm w. dead timeinsertion. This is also often hardware specific like stated...

I think i got the answer i was looking for. https://github.com/greiman/ChRt/issues/12

Just some additional info: There is a ongoing effort to make VESC universally available for all MCU´s running ChibiOS. Which is really awesome. (https://github.com/vedderb/bldc/issues/181). From this thread i see, there is some low levels ST libraries, which need to be replaced or ported...

Hi Im working on a BLDC motor controller board for the Teensy 4.0. The most straight forward approach would, in my opinion, be to port the VESC firmware to T4. Looking at the VESC firmware, it is running ChibiOS and there has been some development on ChibiOS for the T4...