Hi Colin,
colin-aerospace wrote:
The problem I was having with mxbaseconfig was that for the default tasks "ai finite buffered", etc. I was unable to choose a Device from the dropdown menu. None were listed. I was however, able to see the devices when I would click "Create New Task". Unfortunately, when I would select my device "NI 6289", I was unable to choose any of the possible acquisition types, because the "OK" button would be disabled for all types. My guess is this is a bug in mxbaseconfig, or possibly some definition of the 6289 features. I really don't know, but at this point, not sure I care too much either.
I'm not surprised you didn't see your M Series device. The mxbaseconfig utility is meant to be used with the CF-6004 on WindowsCE, where the driver's architecture is better suited for preconfigured tasks.
colin-aerospace wrote:
One more issue I'm having though, and this could very well be a hardware problem on my side, but frequently since installing the PXI-8360 PCIe card which talks to the PXI-1042Q, when shutting down or restarting the computer, I get the "grey screen of death", or the kernel panic screen from OS X[1]. I'm really hoping the 3.5 update fixes this, but I also think it might be a bad connection to the pci bus from the card, which I have encountered before from other devices. Have you ever encountered this? Additionally, when I left a program reading from the PXI-1042Q for a day and came back, the device was no longer responsive. This is when mxbaseconfig was crashing. I restarted, got the kernel panic screen, manually shut down, restarted, and everything worked as before. So that's where I'm at today, will it crash? will it not crash?
I doubt the NI DAQmx Base 3.5 update will address this panic. I'm confident that this is a connectivity problem -- one or more connections are intermittant. When a whole PCI bus disappears momentarily, the Mach and Linux kernels panic; when part of a PCI bus flickers, the bus controller typically sends a non-maskable interrupt (NMI) to the CPU, which causes Windows to blue-screen, Linux to oops and ignore the bus, and Mac to log the error and ignore the bus. You may see important kernel messages in Utilities » Console.
Joe Friedchicken| NI Configuration Based Software |
|---|
Get with your fellow OS users
[ Linux ] [ macOS ] | Principal Software Engineer :: Configuration Based Software
Senior Software Engineer :: Multifunction Instruments Applications Group (until May 2018)
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008) |
