From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
05-09-2017 07:56 AM
Development software: LabVIEW RT 2014
Hardware: PXI RT , Excalibur M4k1553px on Exc-4000cPCI carrier board, PXI NI 6683, A separate monitor connected to PXIRT's DP port to check CPU status and program status on PXI real time.
Mode: Simulating Remote Terminal communication on 1553 , Bus controller external and all A&B cables are connected with Bus coupler with proper 78 Ohm terminators. No mode code or error injections
Issue: Simulation of 1553 works but real time PXI systems locks up, CPU#0 that goes to 100% and ISR (Interrupt service request) to 72% when (ONLY) 1553 communication starts simulating (or by calling ExcM4kP Run RT function).
http://www.mil-1553.com/Excalibur/Templates/showpage.asp?DBID=1&LNGID=1&TMID=108&FID=1535&IID=3221
05-10-2017 10:50 AM
Hi Shahab_S,
Which driver are you using for 1553? How are you implementing it in LabVIEW? What exactly does your code do, and does your PXI controller rail when doing a simple 1553 communication task?
Nick
Applications Engineer
05-10-2017 03:21 PM
Location of driver, you need to have profile to get the LaBVIEW RT driver and then the shipping example was ExcM4kP App RT Get Messages.vi
http://www.mil-1553.com/4000-family
m4k1553pcipx-viRT-win(2.3 Mb) Labview RT drivers
Shipping example in the driver tree: ExcM4kP App RT Get Messages.vi
Thanks
05-11-2017 10:52 AM
Hi Shahab_S,
We need more information about what's actually going on. A few questions:
Nick
Applications Engineer
05-17-2017 05:50 AM
Issue: Simulation of 1553 works but real time PXI systems locks up, CPU#0 that goes to 100% and ISR (Interrupt service request) to 72% when (ONLY) 1553 communication starts simulating (or by calling ExcM4kP Run RT function).
No error on target related to this issue.
Controller never free up and yes killing the power of PXI RT is the only way to get back and try again.
When ExcM4kP Run RT is called which is start of 1553 communication this lock up occurs.
It happens to all other 4 controllers, and Excalibur company also able to replicate the same issue with their shipping LabVIEW example which I posted as link earlier on thread
This has never served us as robust system, we want to make the system that NEVER shows 100% CPU.
{BTW over all program is designed to work under 3% CPU load, No crazy loops without wait function. And also tried timed loop to shift the entire program to CPU 1, still CPU 0 gets upset and zips to 100% and did not help at all}