Communicating with modules in PXI-1042 via MXI-3 interface, all I get is PXI0::MEMACC appearing in MAX. I have OEM modules in the chassis, should these be displayed?

I have a PXI-1042 with PXI-MXI-3 interface kit. In the chassis I have inserted an OEM PXI module. When I run MAX, all I see is PXI System->PXI Bus 0->PXI0::MEMACC. Is this correct? How do I see the other modules?

Darren,
The only PXI modules that show up under the PXI System option in MAX are those cards that are registered with NI-PAL or NI-VISA. For 3rd party cards, it depends on how their particular driver functions. If the vendor creates their drivers based on NI-VISA, then the device will show up in MAX.
If the vendor created a Windows-specific driver, then there is no way that NI-VISA can find any information on the device, nor can it communicate with it. An example of this is a CompactPCI SCSI or Ethernet card, which is supported by a driver that is native to Windows. NI-VISA does not detect such devices.
It is important that you contact the manufacturer of your 3rd party modules and find out if they are NI-VISA complient devices.
Regards,
Andrew Mier
au
Applications Engineer
National Instruments

Similar Messages

I have just downloaded ML. I can get my email via iCloud, but I can't get it on MAIL 6.0. I have done the JAVA thing--seems to be OK. MAIL 6.0 on my desktop won't sync with Mobile Me and won't download emails. Any suggestions?

I have just downloaded ML. I can get my email via iCloud, but I can't get it on MAIL 6.0. I have done the JAVA thing--seems to be OK. MAIL 6.0 on my desktop won't sync with Mobile Me and won't download emails. Any suggestions?

Just did something--am not sure what, probably in the "iCloud"--but seems to be working at last!

HT2998 Hi, I try to conect Mac Mini from 2009 with my HD Tv Samsung F 6400 . With Mini Dvi conection and adapter to HDMI input in TV I got picture but not sound! I have analog cable from the phones out from mac but imposible to conect to TV? Can you HLP

Hi, I try to conect Mac Mini from 2009 with my HD Tv Samsung F 6400 . With Mini Dvi conection and adapter to HDMI input in TV I got picture but not sound! I have analog cable from the phones out from mac but imposible to conect to TV? Can you HLP?

You really need a newer Mac Mini with a true HDMI output, because that Mac Mini's DVI output does not support Audio.
You might try a 3.5mm to RCA adapter
from the Mac Mini's headphone jack to the TV's audio input,
but that would require being able to select the Audio input in the TVs menu while using it's HDMI input.
Optionally you could also use an external 2.1 Speaker System or patch the audio from the Mac Mini to your home stereo system to enhance that older Mac Mini's audio.

I have my catalog "Back Up Each Time Lightroom Exits" checked, and always have. That means the catalog should have been backed-up and saved everyday, if not more than once on some dates. So with a a major problem now and needing to use the Catalog backup

I have my catalog "Back Up Each Time Lightroom Exits" checked, and always have. That means the catalog should have been backed-up and saved everyday, if not more than once on some dates. So with a a major problem now and needing to use the Catalog backup from last Friday, I go to my Lightroom Backups folder - and the most recent one showing not only isn't yesterday, it's OCTOBER 28 !?? Where the hell are the daily backups between October 28 and November 14?

Oh wow - JET LAG strikes agin - my apologies; I have located the missing weeks of back-ups. After getting home from a 30-day trip to Europe, I had changed the location of my LR catalog back-ups to an external drive, and forgot that I did that. I have found them, and all is good. Never operate Heavy Machinery without enough rest. Cheers

How to receive intransit shipments for inter-organization transfer with in-transit receipt routing via Receiving Open Interface

Somebody have samples about how to fill the ROI tables only to have the receipt from inter-organization transfer with in-transit routing.
Thanks in advance.

Pl. visit following links.
Oracle Apps: 11.5.10 / R12 ROI How to Receive Intransit Shipment (Inter-org transfer) for Lot / Serial Controlled Items …
11.5.10 ROI를 통해 INTRANSIT SHIPMENT(INTER-ORG TRANSFER)를 처리하는 방법

What is the matter with you people. I ask a question and all I get is around and around the same page.

All I tried to do was upgrade my system and now I'm discovering I may need a new computer to use Firefox. Im on a Mac G4 osx 10.5.8 Firefox 3.6.10. I tried to update the FF, but now it's telling me I'm running FF 1.6 and my system isn't supported. What's up?

As you have a PPC or Power Mac the last release to work on PPC is Firefox 3.6.*
Firefox 3.6.22 can be found at http://www.mozilla.com/en-US/firefox/all-older.html
Since you have a PPC Mac there is this third-party option for Firefox 7.0.1 http://www.floodgap.com/software/tenfourfox/
As of Firefox 4.0, a '''Intel''' Mac with OSX 10.5+ is required for Firefox builds from Mozilla. http://www.mozilla.org/en-US/firefox/7.0.1/system-requirements/

Why do multiple PXI modules in a chassis cause my PC to continually reset?

I have a PXI-1000 connected to my desktop PC via a MXI-3 interface. When I plug more than a couple of PXI modules into the chassis and switch on, my PC continually resets itself. Any idea what is wrong?

Dear Darren,
This sounds like there is a problem with your chassis supplying the power required for all of your PXI modules. This could indicate either a problem with the power supply on the chassis itself, a problem with the PXI backplane being shorted, or a problem with one or more of your modules. If possible, I recommend testing this system with a different PXI chassis.
If a second chassis works, then we know the problem is with the first chassis. In this case, I recommend checking for bent pins on the backplane. You can also send it in for repair.
If the second chassis does not work, then we know the problem probably is not with the chassis. I recommend testing each card. One of your modules could be shorting the backplane. I recommend testing the s
ystem with each module one at a time. Place each module in each slot in the chassis to see if any combination of modules and slots makes a difference. Once you verify that each module works, you can then test to see if a certain combination of modules causes the problem. The goal here is to determine which module or modules is causing the problem. We need to find out which module is either shorting out the backplane or is drawing too much power.
This could also be a problem with the MXI-3 connection or the PC. I recommend testing this system with a different PC. You may also consider upgrading your PC's BIOS.
If you want to send in your chassis or PXI modules for repair, you will need to call in. In this case, go to http://www.ni.com/support and generate a phone support request.
Regards,
David Shatila
Applications Engineer
National Instruments

Help DSCC agent not communicating with AppServer or Tomcat?!

Installing Directory Server Enterprise Edition 6.3 From Zip Distribution on system running Solaris10 11/08.
Cannot get DSCC to work with either AppServer or Tomcat.
Both AppServer & Tomcat deploy DSEE WAR file and I can look at things that I have manually registered via command line. Cacao agent is running it is just not communicating with AppServer or Tomcat so it cannot commit any actions such as starting and stopping directory instances or creating new directories instances within the web app.
Is this a bug that occurs only when doing a new install using the Zip Distribution?
The Error message I get regardless if Appserver or Tomcat is:
"Could not contact the DSCC agent on <server>. Use the command cacaoadm to check that the DSCC agent is installed and running on port 11169."
I changed to port 11169 because it had a conflict on default port 11162.
Output from cacaoadm & dsccsetup commands is follows:
root@dsee:/ $ /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm status
default instance is DISABLED at system startup.
Smf monitoring process:
8423
8424
Uptime: 0 day(s), 0:47
root@dsee:/ $ /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm list-params
snmp-adaptor-port=11161
snmp-adaptor-trap-port=11162
jmxmp-connector-port=11169
commandstream-adaptor-port=11163
rmi-registry-port=11164
secure-webserver-port=11165
java-flags=-Xms4M -Xmx128M -Dcom.sun.management.jmxremote -Dfile.encoding=utf-8
java-home=/local/jre
jdmk-home=/local/dsee6/private
nss-lib-home=/local/dsee6/private/lib
nss-tools-home=/local/dsee6/bin
retries=4
enable-instrumentation=false
network-bind-address=0.0.0.0
root@dsee:/ $ /local/dscc6/bin/dsccsetup status -v
## /local/webconsole/usr/sbin/smreg/smreg is MISSING
## /local/webconsole/usr/sbin/smcwebserver/smcwebserver is MISSING
## /local/dscc6/dccapp is present
Sun Java (TM) Web Console is not installed
## /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm is present
## /local/dsee6/cacao_2/.configured is present
## /local/dscc6/lib/jar/nquickmodule.jar is present
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm list-modules -r
DSCC Agent is registered in Cacao
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm status
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm list-modules
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm get-param network-bind-address
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm get-param jmxmp-connector-port
Cacao uses a custom port number (11169)
## /local/ds6/bin/dsadm is present
DSCC Registry has been created
Path of DSCC registry is /local/var/dscc6/dcc/ads
Port of DSCC registry is 3998
Any work around or ideas on how to get DSCC working?
Thanks!

I started over and installed Glassfish and everything just worked. After the fact I think the real problem was related to the server.policy file. I think this was the problem because using the default appserver 8.2 that comes with Solaris has a different path and I got this same error when tried using tomcat also. When installing glassfish it uses this default path as in the server.policy example as follows so it just worked.
Add the following lines in the {install-dir}/domains/domain1/config/server.policy file
// Permissions for Directory Service Control Center
grant codeBase "file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/DSCC/-"
permission java.security.AllPermission;
Hope this helps some as I was really stuck and confused at the time and just started playing with the stuff. Growing pains. Thanks to those that replied.
Thanks!
Wences

Teststand best practices architecture for communicating with TCP instruments

Hi,
I am using Teststand 2014 and LabVIEW 2013 SP1 as the module adapter.
My Teststand sequence file includes communication with 3-5 different instruments via TCP/IP.
Such as Spectrum analyzer, generator and other RF measurement devices.
There are many steps located in subsequences that implement code to communicated with these devices whether to fetch , query or write.
What is the best architecture to implement this program ?
As I can see it there are many possibilities, such as :
1. Launching a subsequence as a new thread in the Sequence Setup. This subsequence calls a VI that dynamically register for events/queue that can be launched from any step. (in this case there is a VI running in the background that can perform Write/Read/Qurey to the instrument and he is triggered from any step using an event or dequeue element)
This option can be duplicated for any instrument or only once for all of the instrument with prioritizing the event queue.
2. Creating a communication reference in the Setup of the Main Sequence. And passing it to any step that need it. (there is also the question how to pass this reference… in Teststand globals or in LabVIEW queue).
another 2 small questions that I encountered -
Is using LabVIEW queues and notifiers in TS steps and obtaining their reference (in the LabVIEW code) by name is considered best practices ?
If I would like to run only one VI in a new thread, should I use a new subsequnce and set it as a new thread or use the Run VI Asynchronously ? what are the differences ?

I use Action Engines to hold my VISA Sessions and just write my LabVIEW VIs to use those to send commands and read data. Any returned data can be analyzed in the VI or passed on to TestStand as a step result. You just need a sequence to run at start up to initialize your Action Engines and another one to close them.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Probleme fusible pxi 1042

Bonjour, Suite à une coupure de courant nous avons eu des soucis avec l'alimentation de notre PXI-1042 (led d'alimentation qui été verte quelques secondes puis clignote rouge ainsi de suite).Suite a ceci nous avons voulu vérifier le fusible et avons tiré la languette (a l'arrière du châssis "circuit breaker 10A"), elle est désormais en position ou l'on peut voir un élément blanc. Le problème est qu'elle ne reste plus en position initiale (partie noir seulement visible).Pourriez vous me donner plus d'information à ce sujet? Ainsi qu'au sujet de la led rouge? Merci d'avance de toute réponse me permettant de faire progresser mon problème.

Tiré du USER MANUAL :
Resetting the AC Mains Circuit Breaker
If the PXI-1045 is connected to an AC source and encounters an
over-current condition, the circuit breaker on the rear panel will trip to
prevent damage to the chassis. Complete the following steps to reset the
circuit breaker.
1. Set the front-panel power switch to the Off (nonrecessed) position.
2. Disconnect the AC power cable.
3. Depress the circuit breaker to reset it.
4. Reconnect the AC power cable.
5. Set the power switch to the On (recessed) position.
If the circuit breaker trips again, complete the following steps.
1. Press the front-panel power switch to the Off (nonrecessed) position.
2. Disconnect the AC power cable.
3. Remove all modules from the chassis.
4. Complete the procedure described in the Connecting to Power Source
section of Chapter 2, Installation and Configuration. If the power
switch LED is not a steady green, contact National Instruments.
5. Verify that the PXI-1045 can meet the power requirements of your
CompactPCI or PXI modules. Overloading the chassis can cause the
breaker to trip. Refer to Appendix A, Specifications.
6. The over-current condition that caused the circuit breaker to trip may
be due to a faulty CompactPCI or PXI module. Refer to the
documentation supplied with the modules for troubleshooting
Pierre R...
Certified LabVIEW Developer

PXI-8331 MXI-4 interface connection error

I am using the PXI-8331, PCI-8331 MXI-4 to control chassis PXI-1042. I installed the cards, software and connect chassis to the desktop. MAX window recognizes the chassis but on the chassis status under General tab, a message of "The MXI- connection to this chassis timed out" appears. For this reason, I could not see other modules on the chassis.
How do I solve this problem?
Thanks
Phuc

Hi Phuc,
It looks like there is already a discussion forum discussing the same issue: PXI MXI chassis timeout
Thanks,
Best regards,
Rohan B

File adapter with modules

Hi all
Why is the File adapter does not work properly with modules.
The source file does not be picked up from the source directory when I use module with the CC , but when I remove the modules it works fine.
Do I have to activate anything or to do any set up.
any help would be apreciated.
thanks.

Hi .
It is getting a little bit complicated than I can manage to understand -)
Those are the modules I am using
1 AF_Modules/RequestResponseBean Local Enterprise Bean 1
2 CallSapAdapter Local Enterprise Bean 2
3 AF_Modules/ResponseOnewayBean Local Enterprise Bean 3
config.
1 passThrough               true
3 receiverChannel           cc_receive_from_xtl
3 receiverService           FileAdapter
This is what I getting from RWB
2008-02-11 10:36:02
Success Channel cc_sender_com_get_details: Send binary file "D:\usr\xifileadapter\test\in\compget.txt". Size 151 with QoS EO
2008-02-11 10:36:02
Error: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of RequestResponseBean
How can I determine the SP of my xi whether is 19 or not.
I hope you can help.
best regards
Camilla

Communication with modbus devices

Hello All,
My name Peter, I am currently exploring what LabVIEW has for instrument communication. I have explored a little on NI-Visa and used it for instrument communication through USB and Ethernet. My next task just now is to see how I can communicate with Modbus devices. I have done some background reading on modbus communication protocol and now have some level of understanding of what it is about. I hope to understand more as I continue to read more materials.
I came across an NI-Tutorial titled Connect LabVIEW to any PLC with Modbus. It is about communicating with a networked PLC using modbus. I followed all the steps described for creating Modbus master I/O Server, Binding shared variables to Modbus Address through the I/O Server and writing to Modbus Addresses in LabVIEW. On running my VI to deploy the shared variable, the following error occured.
Can anyone please guide me on what to do because I do not know exactly what is going ON. I engaged in this excercise with the hope of getting to understand more about Modbus communication and then see how I can apply thesame idea to communicate with the Modbus device available in my Laboratory. Please note that I do not yet know much about modbus communication and I am just learning about it now. I do not have any PLC connected to the network. Could that be the reason for the error? If anyone has got any other relevant document to help me get started with modbus communication I will be happy to have them posted here.
Thanks very much for taking time to read through my post message. Hope to hear a quick response from you.
Regards
Peter

Hi SmithD,
I would like to say thank you very much for making out time to respond to my queries. I have done as directed but still not getting result. Following the wire mode port setting configuration, I stopped the process and then selected the RS485/wire4 as the wire mode. On running the VI, an error pops up with the information that the Visa resource is Valid but the port cannot be accessed. I noticed that If I undeploy the shared bound variable the error does not pop up anymore. I concluded that maybe I was not supposed to have added the VISA configure Serial port in the first place.
Kindly tell me what to do.
My task is to read the holding register from a Modbus device. I have the register map with me, and know the TCP and RTU settings for this device. After the attempts I have made so far I was forced to believe that perhaps the device was not responding. I then resolved to using the QModbusMaster which was previously used to read the holding register. For reasons I don’t not know, It worked well with the TCP communication and returned an error that read " slave threw exception > unknown error". With that, I am now sure that the device is functioning properly, at least with the TCP.
Having obtained result from the TCP using QModbusMaster application, I want to simply do the same using LabVIEW.
Some few questions for which I would want to ask for clarification are:
1.) When using the Modbus Library, do I need to create both master and slave instance to be able to read the holding register? My attempt was to create a Master instance with the RTU parameters. The starting address and number of registers were specified at the input terminals of the Read Holding Register VI. This VI immediately followed the Create Master Instance VI. I was expecting that that would read the information contained in the specified registers and output it at the register value terminal. One challenge with this attempt was that with RTU it didn't work. I tried selecting TCP as the VISA resource. But the device was not showing on the list. I went to MAX to create a new VISA TCP/IP resource under the network devices but MAX could not detect the presence of the device. I am now thinking maybe the device is not supported by NI-VISA and so it will not be possible to use the Modbus Library with it.
2.) If the device is actually not compatible with NI-VISA, can DSC I/O server be used to read the information on the holding register?
3.) Do I need an intermediate device between a Modbus device and the PC to be able to read its holding register?
Please if anybody has got a good suggestion as to what to do to get my task achieved, kindly leave me a post.
Thanks
PETER

Can't activate on mac 10.7 Lion-Error communicating with server

I followed help to remove former install and manually install; tried to sign in and activate get same error as when I also tried "don't authorize andactivate" which was: Error communicating with AdobeID server. Try again later. E_AUTH_BAD_DEVICE_KEY"
I'm getting VERY frustrated with this new LION OS on this mac. I can't use OVERDRIVE media-it won't work, I can't use ADOBE, it won't work. I'm about to take it back to where I bo't couple days ago and go back to iPhone which overdrive ALWAYS works and forget all else!
If ANYONE knows ANY solution, since it seems one can never talk to a LIVE person at ADOBE to get help, I'd sure appreicate it.

The way that it is supposed to go, is that when you Launch ADE for the first time, there is a system dialog that supposed to come up and ask you for your login password, so that ADE can get access to the keychain to add the "Digital Editions" password entry.
If you cancel out of that dialog, or don't enter in the password, then you will get the "E_AUTH_BAD_DEVICE_KEY" error.
Make sure that when you launch ADE that this dialog doesn't come up behind ADE (minimize ADE).

HT204085 Unable to sign in because of a problem communicating with iCloud

After the newest update, my iMac will not let me sign in to iCloud. This is the error it reads: Unable to sign in because of a problem communicating with iCloud. Both my iPhone and iPad are fine, just not on iMac. Can't find any help!

I had the same problem. I've even tried reinstalling osx.
the solution is to delete
NetworkInterfaces.plist
in
/Library/Preferences/SystemConfiguration/
then reboot. The file is recreated and iCloud works again.

Communicating with modules in PXI-1042 via MXI-3 interface, all I get is PXI0::MEMACC appearing in MAX. I have OEM modules in the chassis, should these be displayed?

Similar Messages

Maybe you are looking for