Data type error

[bpsf]

Hi,

I am writing a transfer function in labview in the attached file. 

However, it yields error: Type not supported in current target.

Could you tell me the solution?

Thanks for your help.

 

[GerdW]

Hi bpsf,

---

@bpsf wrote:

I am writing a transfer function in labview in the attached file. 

However, it yields error: Type not supported in current target.

Could you tell me the solution?

---

Well, if you would tell us the kind of target you are trying to use - but that information detail is missing from your post…

I guess you should not use DBL values in a FPGA VI. (It's an educated guess…)

Is there a specific reason to multiply by "1"? Is there a specific reason to try that operation twice?

[bpsf]

Thank you GerdW, for your reply.

Yes, I would like to use it in FPGA and timing loop.

There is no reason to multiply by 1 twice. These values are for being changed to other values.

Is there any way to avoid using DBL values or to convert it to FXP?

Thanks,

[GerdW]

Hi bpsf,

---

@bpsf wrote:

Is there any way to avoid using DBL values or to convert it to FXP?

---

Yes, there's a way!

Configure the math operations to output FXP values!

---

@bpsf wrote:

I would like to use it in FPGA and timing loop.

---

You want to place the code inside a SCTL?

Then you might need to use the HighThroughput math functions…

[bpsf]

even when I placed a converter, feedback node yields DBL and shows error.

I appreciate it if you could tell me the specific way.

Thanks,

[GerdW]

Hi bpsf,

when you define all math function outputs correctly then no orange DBL wire appears:

(Infact I only needed to define the output datatype of one single math function…)

[bpsf · Accepted solution]

Thank you GerdW, for all your kindness.

The problem was representation of adder and multipliers. 

Anyway, Thank you very much!

 

[GerdW]

Hi bpsf,

---

@bpsf wrote:

The problem was representation of adder and multipliers. 

---

Note: I used the ToFXP node to convert the "input" to the same FXP representation as "f1" and you copied this behaviour. This might not be the best solution as it could be reasonable to use different FXP settings for f1 and input…

Another note: so the marked solution is your copy of my example code?