02-10-2016 08:04 AM
Dear Community,
I have this error message saying that "LV Comms has encountered a problem and must exit" popped up when opening certain projects. However I still can use the software as normal, just not touch the error message. Is there anyway I can get rid of this error message? Many thanks!
Regards
Yi Chu
02-10-2016 12:22 PM
Follow up the first post, I have found the reason for the error message. In the attached project I have removed all code on the PC side and only kept code on the FPGA. In the top-lv VI FPGAPNC.gvi I put a MRD named PNC Relay fft outside the clock driven loop. Once I connect a clock constant to this node the error message pops up immediately. I have tried this on two PCs and they both got error message. Is this a bug or there is anything wrong within the code? Many thanks!
Regards
Yi Chu
02-11-2016 05:28 PM
Hello Yi,
Thank you for posting your project. This does appear to be a bug with calling MRDs inside of other MRDs.
Can you try to insert the MRD Code instead of the subMRD?
Sorry for this inconvenience.
Regards,
02-12-2016 05:17 AM
Hello Thomas,
Originally the code inside the branch MRDs are directly in the main MRD and there were no compilation errors given. However the compilation to run the code on FPGA has cost three days and failed at the placing stage. I have to switch to different approaches but met other problems...
Regards
Yi
02-15-2016 02:51 PM
Hi Yi,
If you have other issues with the MRD, please feel free to post them here! Or, if you run into other issues in LabVIEW Communications, please create additional forum posts so we can help you.
BeenCoughin
02-16-2016 11:58 AM
Hello Yi,
I am sorry that your compile failed after 3 days. The Compilation Times for FPGAs are usually very long and dependent on the size and intricacy of the design.
Can you please post the other problems that you are facing in another thread. I would love to look through them and is if I can help resolve them.
Regards,
02-21-2016 09:16 AM
Hello Thomas,
I have contacted through service requests and they have solved this bug, thanks very much for the help anyway!
Regards
Yi
02-22-2016 08:47 AM
Hello Yi,
I am glad you were able to resolve your issue.
Regards,