NI PXI-1042 controller.ini file

Hi,
My PXI-1042 system just came in and now I am configuring the controller. A NI PXI-8361.
But in my MAX I can not find the controller.ini files. Where should I look when browsing for it ?
Same goes for the chassis but my guess is that the chassis three will become available when I found the controller.
Thanks in advance.
Stieve
Solved!
Go to Solution.

Hi Stieve
Just in the case you didn't yet found out, as your post is already quite old.
The PXI-8361 is a MXI controller using an external PC. Therefore in MAX, you have to identify is as 'External PC' and not an actual controller. Once this is selected, you should also get access to the proper chassis setup.
Best Regards
Michiel
Applications Engineer
NI Belgium
http://www.ni.com/ask

Similar Messages

Pxi 1042 configuration for Real-Time

I have purchased
PXI-1042
controller 8187
one module for data capturing.
I want to configure the said pxi for Real-Time purposes,
so what steps should I follow?
thanks
Abbas
Solved!
Go to Solution.

The Real-Time Deployment License is different from the LabVIEW RT module.
When you purchase a PXI controller, part of what you are buying is the operating system that is installed on it. If you purchased the controller with Windows on it then you purchased the copy of Windows that came with it. Now that you want to put the real-time operating system on it, you need to purchase the license for it.
But that's all legal stuff.
And you are correct that there is a copy of the RTOS on the controller. But if your controller has its disk formatted as NTFS you will not be able to use it. The RTOS requires that the hard drive be FAT32.
If your controller is FAT32 then you can boot into BIOS (hit delete while booting), and select Real-Time in the Boot Configuration to make your controller boot into Real-Time.
If you controller is not FAT32 then you will need to format the controller first, using the disks I have previously mentioned.
Please let me know if you have any questions.
Justin Parker
National Instruments
Product Support Engineer

I have a CD-ROM with file chassis.sys for my PXI-1042 chassis. What do I do with it?

I have a CD-ROM with file chassis.sys that came with the PXI-1042. How is that file used/installed?

Hi,
The "chassis.ini" file contains information which is used to generate a "pxisys.ini" file, which describes a unique combination of PXI chassis and controller. If you are using a National Instruments PXI controller, you will not need to use this "chassis.ini" file, because our Measurement and Automation Explorer (MAX) configuration software already contains the necessary information embedded. Instead, you simply need to setup your configuration in MAX.
KnowledgeBase 1EGB71UI: What Are PXISYS.INI and CHASSIS.INI?
K
nowledgeBase 32TDRRWD: Configuring the PXI System Entry in MAX 3.x
Josh Hernstrom
PXI/VXI Support
National Instruments

PXI-MXI-4 with NI PXI-1044: No PXISYS.INI or CHASSIS.INI Files

I am unable to locate PXISYS.INI or CHASSIS.INI files for use with the PXI-MXI-4 bridge with a NI PXI-1044 chassis. I have reviewed the knowledge base article regarding these files (http://digital.ni.com/public.nsf/websearch/862567530005F09C862566A0005EAB87?OpenDocument) but am still stuck.
According to the article, the chassis manufacturer (NI in my case) should provide these files. However, they are nowhere to be found!
Any help would be appreciated.

Hi Luke,
You can generate the required configuration files using MAX. Please refer to
"Configuring the PXI System Entry in MAX 3.x" at
http://digital.ni.com/public.nsf/allkb/5902345227DFCA1286256EDA0063F50C
for more information on how to do this.

Image a Windows 2003 Server on a PXI - 1042 with a 8108 controller

Hi,
I have installed Windows 2003 Server on a PXI - 1042 with a 8108 controller. When I try to take an image of this it fails and I have to remove the hard drive. Then I have to hook it up to a SATA interface and use Ghost 11.5 to image the hard drive.
Is there a easier way to do this with the Acronis software?
Thanks,
John P

Hello John,
When you fail taking an image, are you using Ghost or Acronis?
If it is Acronis you are using, are you using the version that comes on the controller, or are you using the upgraded version, Acronis True Image Home 2009? If you would like to replace the image that is present on the NI PXI controller you will need to use Acronis® True Image Home 2009 which is available from Acronis.
Note: If you would like to create a locked factory controlled partition on your PXI controller as National Instruments provides, the Acronis® True Image Home 2009 will allow you to do this. This additional functionality would then be supported by Acronis and not National Instruments.
This version should allow you to successfully take an image of Windows 2003.
Thanks,
Ryan F.

ADLINK PXIe-3985 Controller - NI PXIe-1062Q Chassis Compatibility

Hello forum members!
we recently purchased a PXIe-3985 ADLINK PXIe Embedded controller to be installed in a NI PXIe-1062Q PXIe chassis. In our system is also present a NI PXIe-6672 Timing Module, installed in the chassis timing slot (4). Windows 7 installation, NI MAX toolsuite and NI PXIe-6672 Timing Module driver installation worked fine, but we discovered that the CPU is not able to recognize the TIMING SLOT. We cannot generate any PXI STAR signal with our NI PXIe-6672 Timing Module because it appears that the TIMING SLOT is recognized as normal peripheral slot. The PXI trigger lines and clocks are working well and usable, but not the PXI STAR signals.
I also tried to install the PXIe Chassis in the NIMAX toolsuite as explained in the PXIPLATFORM _50-17049-100_200.pdf document from ADLINK.
basically in the NIMAX device and interface tab I right click and try to add the pxie chassis.
First it is not understandable how can I find the bus identifier root of the chassis. There is a PXI bus tree, but no evidence of the PXI bus related to the chassis.
Furthermore even if I select one PXI bus, the NI PXIe-1062Q PXIe chassis is not listed and trying to load the corresponding .ini file from C://programs/nationl instruments/PXI/PXIe Chassis/ returns the error “Could not import Chassis information. Error Code 0xFFFB380E”
is the ini file working at all for my PXIe chassis? is there another procedure that I must follow to have my timing controller working or the chassis installed?
We definitely need this capability to test our equipment and I would like to know if there are known incompatibility issues between these three devices:
PXIe-3985 ADLINK PXIe Embedded controller
NI PXIe-1062Q PXIe chassis
NI PXIe-6672 Timing Module
And in case if there is an update or workaround which solves the issue.
The system has Win7 32bit installed.
Many thanks to every answering user

Hi emanuele83,
which version of PXI Platform Service do you use?
Can you please upgrade to a current version?
Here is a download link:
PXI Platform Services 14.1 - National Instruments
http://www.ni.com/download/pxi-platform-services-14.1/5230/en/
This may solve the issue.
Best regards,
Andi

How to use TRG pine in PXI-8176 controller

Dear All,
        I have Thermocouple data acquisition system. In which there are 2 chassis, (1) PXI 1002 with
PXI8176 controller with RT, PXI 6071E DAQ card (2) SCXI 1001 with SCXI 1125 card and SCXI1327 block.
PXI 6071E connected to SCXI 1125 with SH1006868 cable and adapter SCXI1349.
I am using Labview 8.6 , DAQmx9.0
I have develop program for continuous thermocouple acquisition. Now i want to make program on trigger based data acquisition. When trigger pulse comes system starts to acquire data ( and log in file) for userdefine time and stop acquisition. Again when trigger pulse comes   system again starts to acquire and stop at define time.
There is one TRG pin on PXI-8176 controller, Can i use that one and how i can use it? Or i have to use separate DIO line for trigger?
Can you guide me how i can develop such system.
Thank you.
--Vishnu
Solved!
Go to Solution.

Thanks Shreyas,
Once again you help me to solve my problem.
   As i have already mention you i have develop temperature measurement system with-out trigger. Here i am attaching my project. Now, how i can make it trigger based, means when trigger pulse comes acquisition start and target send data after some time for example 5minutes stop acquisition and restart acquisition again when next trigger pulse comes and so on.
Thanks
--Vishnu
Attachments:
host_target.zip ‏81 KB

Pxi-8176 controller to read data from an instrument controlled by another controller

can i use pxi-8176 controller to read instrument data on the gpib bus from an instrument controlled by another pc gpib controller?

Thanks.
I understand what you're saying, but I'm also trying to understand why the following is not possible or is not more readily available:... Just as NI IO Trace (NI Spy) listens/eavesdrops to the GPIB real time, one would think that Labview would be able to do it also. One would think that just as NI IO Trace (NI Spy) publishes to a window/file/memory it shouldn't be impossible to publish to a string so that it can be processed real-time by some VI algorithm. If I think about NI IO Trace as a VI, I would think that it is already in a string format before it is published to the NI IO Trace window... why isn't that string available to Labview VIs block diagram?

Configurate a PXI-1042 RT Chassis in a network thru MAX

Hello,
Iam having two NI PXI-chassis.
The first one is a PXI-1031 4Slot chassis, runs under Windows XP and has the NI-5670 RF Vector Signal Generator (RFSG) installed.
The second Chassis is a PXI-1042 8 Slot Chassis that runs under LabView 7.1 RealTime and has a PXI-6602 Timing IO installed.
Both system has been deliverd by NI with the factory intallation services, so there shouldn´t be any problem with the installation and when powering each system up they seams to work fine.
And now to my problem:
Starting the Mesurement & Automation Explorer(MAX) under Windows (on the first Chassis) I can the see the installed RFSG, I connect both chassis thru a twisted pair cable -- I can see the secound chassis as well. So far so good, I was giving the second chassis (RT-enviroment) the IP address 000.000.000.001. But when clicking into it and the doubleclicking on devices and interfaces I can´t see the istalled PXI-6602 Timing IO card, how can I change that?
I tried to create a new object under devices and intefaces, but I can´t find a predefined PXI-6602. Wherer is the misstake.
in the hope of help
bye

Hello,
normally you should do the following. Connect both chassis. Controller with RT should be reset (at first time), then it will get IP Adress 0.0.0.0. You should change IP Adress, restart system and then install software on RT-System by rightclick in MAX to Software and choose install Software. After it your 6602 should be found.
Hope this helps,
Rebecca Fox
Applications Engineer
National Instruments
Rebecca Fox
Applications Engineer
National Instruments

I tried to upload the Pxisys.ini file and MAX is showing the slot ID ...but i need a function to return those slot numbers..such that i can use in my DLL

hi hamilton,
thanks for your reply .
I already tried the option or pxisys.ini file
The MAX is showing the slot number ..but My requiremet is to use the slot ID in a DLL
so I need a function type of statemen to return or get the slot number of the NI devices on the PXI.
I think I clearly explained.
I would like to get the slot numbers through a software fucntion such that i can use the slot numbers values for some other purpose ,,like configuration ,,

jayamurugan,
This functionality currently is not built into National Instruments software. You can get the device number, but not the slot numbers programmatically.
Trey Hamilton
Applications Engineer
National Instruments
http://www.ni.com/support

Convert PXIe-8135 controller to dual-boot Windows 7 and LabVIEW RT

Hello. I have a PXIe-8135 controller that originally was just running Windows 7. We are trying to convert it to a dual boot system to also run LabView Real Time. (There is host computer that will run LabVIEW 2014 with the RT module, and the controller will become a target).
I have created a FAT32 partition on the hard drive of the controller. Now, I’m trying to install the real-time OS with a USB flash drive made using the MAX utility, but I cannot boot using the USB drive for some reason. I keep getting the message “waiting for USB device to initialize”.
In BIOS, legacy USB support is [ENABLED] and boot configuration is set to [Windows/other OS]. I’ve tried removing the drive, waiting, and reinserting. I’ve tried two different USB drives (both 8 GB, different brands).
I’m not sure what to do next. Apart from the USB boot issue, is converting the PXIe-8135 even possible? I read about SATA/PATA hard drive issues with older controllers, but I don't know about this one.
Thanks, in advance, for your help!
-Jeff
Solved!
Go to Solution.

Per Siana's licensing comment, more information on purchasing a deployment license if you do not have one for this target can be found here.
The RT Utility USB key is used to set up non-NI hardware with LabVIEW Real-Time, but you should not need it in this situation to convert to dual-boot (*). Try this:
1. Since you already have a FAT32 partion created, go into BIOS setup and change to booting 'LabVIEW RT'.
2. The system will attempt to boot LabVIEW RT, see that the partition is empty, and switch over into LabVIEW RT Safe Mode. (this safemode is built into the firmware, which is why you don't really need the USB key).
3. The system should come up correctly and be detectable from MAX, and you can proceed with installing software.
4. To switch back to Windows, go back to BIOS setup and choose 'Windows/Other OS'
(*) One area where the USB key is helpful on a dual boot system is with formatting the disk. If you want to convert from FAT32 to Reliance on the partition designated for LabVIEW RT, the USB key lets you attempt to format a single parition and leave the rest of the disk untouched. If you format from MAX, the standard behavior is to format only one RT partition if found, but if not found, it will format the entire disk. Formatting from MAX on a dual boot system is consequently riskier and you could lose your Windows partition.

Memory upgrade on PXI-8105 and PXI-8106 controllers

Hi,
I've recently upgraded the memory of three PXIs; one with a PXI-8105 controller and two with PXI-8106 controllers. Both the 8105 and 8105 can take a maximum of 4GB (2x2GB) of DDR2-677 (PC2-5300) memory (see links below). However, on all three systems, both the BIOS and the O/S only see 3.3GB. Any idea why this might be the case?
I've tried flashing the BIOS (v1.4 on both PXIs), but with no success.
We're using COTS memory (i.e. not bought from NI) but I'd be hard pushed to believe that that is the cause of the problem.
Thanks.
Links;
Max memory capacity of PXI-8105 http://sine.ni.com/nips/cds/view/p/lang/en/nid/202630
Max memory capacity of PXI-8106 http://sine.ni.com/nips/cds/view/p/lang/en/nid/203442
BIOS upgrade page: http://digital.ni.com/public.nsf/allkb/9C9362590B05CD6E86256B270082164A
Solved!
Go to Solution.

Are these controllers running Windows? If so, this is normal expected behavior. I think it might have something to do with the fact that Windows reserves the rest of the memory for driver addressing (could be totally wrong there). The same thing happens on my Dell desktop PC with 4GB of memory in it.
Jarrod S.
National Instruments

How to create and edit a .ini file using java

Hi All...
Pls help me in creating and editing an .ini file using java...
thanks in advance
Regards,
sathya

Let's assume the ini file is a mapping type storage (key=value) so lets use Properties object. (works with java 1.4 & up)
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.IOException;
import java.util.Properties;
public class Test {
     private static Properties props;
     public static void main(String[] args) throws IOException {
          File file = new File("test.ini");//This is out ini file
          props = new Properties();//Create the properties object
          read(file);//Read the ini file
          //Once we've populated the Properties object. set/add a property using the setProperty() method.
          props.setProperty("testing", "value");
          write(file);//Write to ini file
     public static void read(File file) throws IOException {
          FileInputStream fis = new FileInputStream(file);//Create a FileInputStream
          props.load(fis);//load the ini to the Properties file
          fis.close();//close
     public static void write(File file) throws IOException {
          FileOutputStream fos = new FileOutputStream(file);//Create a FileOutputStream
          props.store(fos, "");//write the Properties object values to our ini file
          fos.close();//close
}

Memory leakage when using Ini-file VIs

I'm using the Configuration File Vis to read and write data to different .ini files. The files contain both standard keys and clusters written as a segment using the Open G toolkit. Instead of opening the files and keeping them in the memory of the Config VIs I'm just using them to read and write, decode and encode...the references are all closed using the Close Config Data.vi. The problem is that even though immediately close the config data the application keeps grabbing more and more data...every time a configuration file is open, read or written to and the closed everything from 4K to 50K of additional memory has been allocated by the application (this is a stripped down application that only deals with the config files, so
there are no other sources for the memory leak).
Has anyone else experienced this? How can you repeatedly open and close config file slike this without it continoulsy allocating more memory?
Attached is a copy of the VIs, the directory structure must be kept intact if the ini file is to be read correctly.
I've been stearing so hard on this the whole day that I might just be overlooking something obvious...
In the full application the VI init and write operations are only done when the user reconfigures the system, which may be a couple of times per month...so the memory leak would not cause a problem right away, but it would not be healthy to leave it there...
MTO
Attachments:
Memory_Leak_Demo.zip ‏1391 KB

Could you post a 6.1 version?
LV7 is still about two weeks away for me.
Does the problem show up in 6.1?
I ran across an error while writting to a FP output that was not configured that would cause a "drop of memory" to leak every time the VI performed the write. The leak did not show up in the profiler but windows would show te memory foot print growing continually as long as the writes continued. The work around was "don't do that!".
I bring this up because I found and reported this just prior to LV7 release and the featur may still be present in LV7. I also believe that Jean-Pierre used a "write and check" metod to detail with the unknown data types of of complex data structures.
If you just read does it leak?
If you just use simple data types do
es it leak?
Is the ini file growing?
I really appreciate the effort you have been putting into the Dev-Exchange Mads! I wish i could do to more to help.
Keep us posted.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

How do I hide Windows .ini files in a dock folder?

Background: On my MacBook Pro, I divided my hard drive into 3 partitions - one for Mac OS X, one for Windows 7, and one for common storage that I use to transfer my files between OS's.
With this setup, I set my Dropbox folder on the "common storage" partition, and created a Dropbox dock folder for easy access. This isn't really a major problem, but it simply annoys me. Since Windows also has access to the Dropbox folder, it creates a desktop.ini file that shows up whenever I use the Dropbox dock shortcut. I tried editing it through Finder, but it's already hidden. It only shows up in the dock folder.
Is there a way to hide this .ini file?

What do you mean deleted from the user's list? Do you mean removed permissions? If so, right click the folder and select get info. Scroll down to sharing and permissions. Click the lock and put in your password. Then click the + and add the user back.
Otherwise, more details...

NI PXI-1042 controller.ini file

Similar Messages

Maybe you are looking for