FPGA Module I/O node ghosted or faded

[Lokis]

Hi There.

I am writing a Sine Waveform from a NI 9263 module by writing the output from the "Sine Generator" to a FPGA I/O Node to Mod2/AO0.  I am then using a 9239 to read in that Sine Waveform using a FPGA I/O node to Mod3/AI0.  I was originally running things on a 9012/9102 combination (8 slot).  I then switched over to a 9012/9101 combination (4 slot).  I updated the software and am using 8.5.1 on the 4 slot.  For some reason my FPGA I/O Nodes have now become faded or faint.  I am using two other modules in the 4 slot and have no problems with them (9403 and a 9870).  The program compiles, but when I run it I get no data coming in on the 9239.  All zero.  I test the signal coming out of the 9263 and there is a sine wave being generated, but I have lost host control over the amplitude of it (Normally I can control amplitude and freq from the host).  I suspect when I switch the vi's from the 9102 to the 9101 I broke something.  I have literally started from scratch with a new project and still end up getting faded FPGA I/O nodes.  Have used different modules as well as different chasis so I don't think it is a hardware issue.  Anyone have any idea what the problem might be. 

Thanks.

[Bassett_Hound]

Hi Lokis,

Any chance you can post some images of the Faded IO or zip up the project files?  Have you been able to run any examples shipped with you latest update?  Did you also upgrade your LabVIEW FPGA and NI RIO versions when you upgraded LabVIEW?

Basset Hound

[Lokis]

Thanks for the Reply. 

Yes FPGA and NI RIO were upgraded when Labview was upgraded.  After spending a day troubleshooting with no results, we have decided to go back to an existing 8.2 program and update it to 8.5.1.  Turns out it works fine and we don't have any faded I/O Nodes.  So now we are going to rebuild from this software which will probably be quicker than trying to determine what went wrong with the other code.  I was hoping it might be a relatively common problem.
Hopefully I have attached a png of the FPGA code.  I had disabled the Mag component above.  Mod2 and Mod3 are the faded I/O's. 

If I do determine what caused the problem or it's cure I will post it. 

Thanks again.
Lokis

[Bassett_Hound]

Lokis,

I believe your seeing the new feature of NI RIO 2.4.0 with LabVIEW FPGA 8.5.x where the IO nodes return calibrated fixed point data.  In earlier versions of NI-RIO software, C Series I/O nodes returned raw, uncalibrated binary integer data. In NI-RIO 2.4, C Series I/O nodes return calibrated fixed-point data scaled to engineering units. For more information about how this change may affect your applications, refer to the KnowledgeBase at ni.com.  If you have existing applications, you can configure the modules to return uncalibrated Integer data as was previously returned.  Just right click on the module in the project and select Raw or Calibrated and you'll see the IO node change between Fixed Point (gray) and Integer (blue) data.  If your using calibrated you no longer need to use the Binary to Nominal VI to calibrate the data.

Check out the KB linked above as it provides some decent info to get you started.  Please post back any feedback you have as I really think you'll like the new feature.

Hope that helps,

Basset Houn

[Lokis]

Thanks you very much. 

That was the problem.  Saved me alot of time rewriting the whole project.  Much appreciated.


Thanks
Lokis.

[Bassett_Hound]

Your origninal project should have migrated the modules in the project to retain the Raw mode for IO nodes.  Did you re-add modules to an already existing project?

[Lokis]

Hi again.

I had added a new target and new modules to an already existing project.  The detect of the new modules resulted in the switch from raw to calibrated data.  Sadly I thought I had double checked the old module properties with newly detected ones and determined they were the same. Obviously they weren't. 

Lokis

[Bassett_Hound]

Ah.  Sounds good then.  If you migrate existing projects they will keep the Raw Ingeter mode intact.  For any new modules added they will default to Calibrated Fixed Point Data.  Feel free to proivide feed back on the change or the new data type.

Regards,

Basset Hound