myRIO 1900 error 63038

[daniel.srubar.st@vsb.cz]

Hello,

I apologize for yesterday's "hijacking" of another topic. Please help me with my problem regarding LabVIEW and myRIO device.

I am using LV version 2018 32bit (32bit because of myRIO Toolkit). I am working on a program with FPGA VI and for some reason the FPGA stopped working. LV throws me error 63038 when starting the FPGA VI. Also when I turn on myRIO, the myRIO USB Monitor program starts. I enter Launch the Getting Started Wizard and the device gives me the same error.

I don't know what happened, maybe there was a background update or something. I tried updating the FPGA module, myRIO Toolkit even Xiling tools and the result is still the same. I put photos from NI MAX and NI MANAGER here, the programs should be compatible.

I will be very grateful for any help to solve this problem and get the FPGA up and running.

Thanks 🙂

Daniel

[Bob_Schor]

Thank you for attaching three pictures (I generally, and in this case, too, hate pictures when discussing problems with LabVIEW code).  The first one was a black rectangle (I could see no image), the second a (partial?) list of the LabVIEW files found by NIPM (not very useful, as we don't know much else about your system, such as what version of LabVIEW you are running, and whether it is 32- or 64-bit, and whether you are running the Real-Time Module (oops -- I just went back to look, and saw that the first, "MAX", image now opens and answers (some of) my questions).

OK, you seem to be running LabVIEW 2018 SP1 (a.k.a. 18.5).  Still no information on the system running on the Host PC, presumably also LabVIEW 2018 SP1, and presumably 32-bit.  [Correct me if this is incorrect]. 

So now find the LabVIEW Project, which (I hope) is contained, along with all the LabVIEW code you have developed, in a Project Folder (along with the .lvproj file).  Go Compress this Folder (right-click folder, choose "Send To", choose "Compressed (zipped) Folder", and attach the resulting .zip file when you reply.  I'll be happy to try out the code with LabVIEW 2019, and if I also get an error (which I should), I'll try to find out why it is occurring, and do a little "teaching".  My Forum colleagues will also have something to look at, and many are significantly more experienced than I ...

Bob Schor