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-26-2011 11:05 AM
Hi,
I know this is a bit lenghty but I wanted to describe it in detail.
Bottom line is that the NI Device Loader cannot start when no camera is found and hence no PXI cards can be used. I would expect that the driver could be updated to improve this behavior. It is clear that the camera does not work when it is not connected but I expect that the other PXI device work normal.
The Driver for the PXI-8231 card in Network adapter in Windows Device manger is "National Instruments GigE Vision Adapter #3". This was the case in all steps below, also after the reboots (as expected).
I have the following PXI cards in my system (Slots that are not listet are empty/have SlotBlockers):
Slot 1: PXI-8108 (Embedded Controller)
Slot 2: PXI-8511 (CAN)
Slot 3: PXI-8231 (Ethernet) My camera is connected here via a LAN cable
Slot 4: PXI-8430 (RS232)
Slot 6: PXI-6259 (DAQ)
Slot 8: PXI-4130 (SMU)
Slot 10: PXI-4130 (SMU)
Slot 12: PXI-4130 (SMU)
I performed the following steps:
1) I booted the system with all cards as described above
NI Device Loader runs (Status: Started),
All DAQ and SMU cards pass the Selftest in MAX
The camera on the PXI-8231 card works as expected
2) I disconnected the camera from the LAN cable while the system was running, nothing unexpected happened
NI Device Loader runs (Status: Started)
All DAQ and SMU cards pass the Selftest in MAX
The camera is not visible in MAX anymore
3) I connected the camera again to the LAN cable while the system was running: as expected same results as in 1)
4) I shut down my system, disconnected the camera from the LAN cable and booted the system up again
NI Device Loader Status is Stopped
All DAQ and SMU cards are visible in MAX, but the Selftest fails for all those cards with Error -88705 "The specified device is not present or is not active in the system."
The camera is not visible in MAX
5) I connected the camera again to the LAN cable while the system was running
NI Device Loader Status still on Stopped
all DAQ and SMU cards are visible in MAX, but the Selftest fails for all those cards with Error -88705 "The specified device is not present or is not active in the system."
The camera on the PXI-8231 card works as expected
6) I started the NI Device Loader manually => same results as in 1)
7) I rebootet the system (same configuratin as in 1 and 5/6) => same results as in 1)
05-27-2011 12:10 PM
Thanks for the detailed info. I'll pass this on, and we'll see if we can recreate this.
Jon
07-11-2011 04:34 AM
Hi Jon,
any news on the described problem? Please reply in the forum or let me know if you prefer to discuss it ia e-mail or so.
07-12-2011 04:34 PM
Hi,
What chassis are you using? Can you recreate this behavior with minimal hardware in the chassis. Try this setup:
PXI 8108
PXI 6259 in slot 2
PXI 8231 in slot 3
Do you still see the same behavior? I'd like to try and recreate this, and in order to better diagnose if it is a bug I need as simple a setup as possible that can recreate the issue.
Jon S
07-14-2011 03:15 AM
Hi,
I use chassis PXI-1044. I recreated the same problem with the setup you suggested, the numbers explain the setup as in my long text on 05-26-2011 11:05 AM (I did not try 2),3) and 5), but am sure that they are equal as well).
1) same result
When I started MAX I received the following error message.
MAX: error message at start
The exception occurred in the NIMax process in the function (Unknown).
See these files for details:
C:\ProgramData\National Instruments\MAX\Logs\20110714_085425-NIMax-00000C84.log
C:\ProgramData\National Instruments\MAX\Logs\20110714_085425-NIMax-00000C84.dmp
4) same result
6) same result
7) same result, this time w/o the Max error message
08-01-2011 03:17 AM
Hi Jon,
any news? Did you recreate the issue? Any solution in sight?
Regards,
Tobias
09-14-2011 04:12 AM
Jon, do you have any news or a solution?
09-15-2011 12:57 PM
We haven't been able to replicate this on our end. Is the mDSN service also not started when this behavior occurs? If this is the case, you can try the following steps:
1. Install the latest version of Java
2. Turn off the 'User Account Control' in the control panel
3. Open a command prompt as an administrator
4. Type 'netsh int ip reset' into the command prompt and hit return
5. Reboot your PC, this should solve the issue with the mDNS Responder
Jon
09-16-2011 09:04 AM
Tthat worked!
As you suggested the National Instruments mDSN service was also not started. I tried to find out my installed Java Version, but that was not possible and sometimes even my Browser crashed. So it seems that my Java was somehow corrupt. Following your suggested steps solved the issue. Thanks a lot.
Tobias