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.

NI Linux Real-Time Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Configuring desktop pc as RealTime Linux Target

Hello All,

             I was working on NI PXIe-1071 Controller with Pharlap ETS OS, recently we did started a pilot project to migrate from PharLap to Real Time Linux,to analyse the performance and responsiveness of the System. I did realized that RealTime Linux is only supported for the cRIO platforms, which is either ARM or Atom based  Configuration. The ATOM configuration of cRIO caught my attention, as my intention of performance testing does not necessary need a FPGA Part of (cRIO) ( Please see the attachment FPGAExcluded.png), so i had continued to building a RealTime Linux image with Desktop PC as target

As Instructed within the NI Site and Read Me Files, following are the steps i had performed.

Package Setup:

1) Set-up a Host PC with Scientific Linux:

Linux localhost.localdomain 3.10.0-327.13.1.el7.x86_64 #1 SMP Thu Mar 31 11:10:31 CDT 2016 x86_64 x86_64 x86_64 GNU/Linux

2) Create the Environement Setup with the following command ( Please find the corresponding env-nirt-i386)

     MACHINE=i386 ./nibb.sh config

3) I did following the READ me to build the SquashFS and the RootFileSystem ( Please find the RFS-SquashFS.pdf)

     bitbake ni-console-image

Bootable USB

1) Created two partiton with parted utility  within the host

2) Installed the Grub over the USB

    sudo grub2-install --boot-directory=/media/usb/boot /dev/sdb

3) Extracted the Root File System over to the other partition.

    sudo tar xjf niconsole-image-i386.tar.bz2 -C /media/rfs/

After all this steps, i had realized that, the RFS (Extracted over to the USB) does not contain any of the NI  envrionment, applications like NI-LVRT and other startup scripts.

Over my study i did realized that .RTEXE can be deployed as a standalone application in linux only after the BootStraping the file with the bootable content, for which NILVRT is responsible.

It was my idea to pay the cost for the deploying licence,similar to one existing to convet PC to LabView Target

http://www.ni.com/tutorial/2733/en/

Really stuck up here for some ideas, and instructions to deploy

0 Kudos
Message 1 of 4
(5,624 Views)

Hello pratapnaidu,

Unfortunately we have not yet converted our LabVIEW RT Deployment License for Desktop PCs to NI Linux Real-Time. Our goal is to first complete standardizing our own hardware on NI Linux Real-Time and then address this use case. Unlike the Phar Lap use case, where we combined the RTOS and LabVIEW Real-Time Run-Time Engine into one item for purchase, now that NI Linux Real-Time is open source on Github, we still need to separately price and package the RTE and select supported chipsets. Let me send you a private message to discuss loaning an NI Linux Real-Time CompactDAQ controller.

Deborah Burke
NI Hardware and Drivers Product Manager
Certified LabVIEW Architect
0 Kudos
Message 2 of 4
(4,955 Views)

Hi pratapnaidu,

While this doesn't answer your question regarding deploying NI Linux RT to a desktop system, if you don't need the expansion I/O provided by cRIO, you could also look at several other NI RT systems that also now run Linux RT (besides cRIO).

IC-3173 Industrial Controller

http://sine.ni.com/nips/cds/view/p/lang/en/nid/213465

NI CVS-1459

http://sine.ni.com/nips/cds/view/p/lang/en/nid/212667

0 Kudos
Message 3 of 4
(4,955 Views)

Hi Deborah_B <https://decibel.ni.com/content/people/Deborah_B>,

Iam located around Chicago, I would like to

know what would be the cost of leasing the unit?

Thanks,

pratap

0 Kudos
Message 4 of 4
(4,955 Views)