No output DAC0 or 1 using CW10.5 using PE DAC_LDD component on K70 tower board

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

No output DAC0 or 1 using CW10.5 using PE DAC_LDD component on K70 tower board

Jump to solution
1,696 Views
jdjenzano
Contributor I

No output DAC0

Tried several different program methods finally went back to the Help example code for SetValue. Method in Component DAC_LDD - bare board simple project with one component, tried two different TRW-K70F120M boards

 

The Voltage reference source was default – internal Vrefo in the DAC component Properties – Seemed like good choice – Changed it to external Vdda – schematic shows this connected to 3.3Vdc Generate PE code/Build/Debug/Start - Got voltage out

 

Not sure why internal Vrefo (default) did not work but I’ve had just too much fun with this component to spend more time looking –We can live with Vdda just fine – Anyone know  why internal Vrefo did not supply an output?

 

 

Original Attachment has been moved to: TestDAC.txt.zip

Labels (1)
Tags (3)
0 Kudos
Reply
1 Solution
1,101 Views
Lukas_Heczko
NXP Employee
NXP Employee

Hello,

internal reference in this case means that it is produced by internal peripheral. Vrefo is generated by VREF peripheral so prior using DAC you have to configure it. After reset, VREF is disabled which caused missing DAC output. You can use Init_VREF component to configure VREF.

Best Regards,

Lukas

View solution in original post

0 Kudos
Reply
5 Replies
1,102 Views
Lukas_Heczko
NXP Employee
NXP Employee

Hello,

internal reference in this case means that it is produced by internal peripheral. Vrefo is generated by VREF peripheral so prior using DAC you have to configure it. After reset, VREF is disabled which caused missing DAC output. You can use Init_VREF component to configure VREF.

Best Regards,

Lukas

0 Kudos
Reply
1,101 Views
jdjenzano
Contributor I

 

Lukas – Thank you for your great response – We will not have time to test it now but your answer makes sense – We are now having more fun than we should be allowed to have with setting up FTM1 as a Quad encoder input – Seems to be working, we need to test some more (We were trying to use FTM0 but the FTM init component has no Quad properties for FTM0!)

0 Kudos
Reply
1,101 Views
Lukas_Heczko
NXP Employee
NXP Employee

Hi,

as for quadrature decoder: K70 FTM0 peripheral does not have this functionality so it can't be configured in init component. Quad decoder is available only for FTM1 and FTM2 as described in reference manual:

3.8.2.1 Instantiation Information

This device contains four FlexTimer modules.

The following table shows how these modules are configured.

 

Table 3-63. FTM Instantiations

FTM instance     Number of channels     Features/usage

FTM0                8                                 3-phase motor + 2 general purpose or stepper motor

FTM1                2                                 Quadrature decoder or general purpose

FTM2                2                                 Quadrature decoder or general purpose

FTM3                8                                 3-phase motor + 2 general purpose or stepper motor

 

Compared with the FTM0 and FTM3 configuration, the FTM1 and FTM2 configuration adds the Quadrature decoder feature and reduces the number of channels.

Best Regards,

Lukas

0 Kudos
Reply
1,101 Views
jdjenzano
Contributor I

Lukas
Thank you for you helpful and proactive answer to the FTM that was not part of this DAC question thread. We missed this in the manual but we realized it after a while when we could not find the Quadrature property setting in FTM0 - We moved to FTM1 and there they were! Works great - We input the Quadrature signals from a 4 inch linear encoder and output them to DAC1 (setup same as DAC0) and we can see it works as expected. We use the linear encoder to measure "Nugget expansion" or "Set down" in resistance welding in relation to Hall effect current input (ADC0) Attached are the DAC and FTM1 properties we are using

0 Kudos
Reply
1,101 Views
Lukas_Heczko
NXP Employee
NXP Employee

Thank you for sharing! Happy to hear that your project successfully progresses!

Lukas

0 Kudos
Reply