CRIO not Detected in MAX

Hello,
I'm totally new to NI and LabVIEW, so I may have done many unnecessary steps or missed something obvious, but here's the rundown (what I can remember) of what I tried:
I'm trying to make a cRIO-9073 (newer revision, IPreset switch does not reset IP to 0.0.0.0) work with LabVIEW 2011 SP1 (includes MAX 5.1.0f0 and NI-VISA 5.1) installed on Windows 7 Professional SP1 using a crossover ethernet cable.  MAX does not recognize the cRIO in the Remote Systems tab.  After initial problems, I was able to locate 2 IP addresses corresponding to the cRIO, but its still does not appear in MAX.  I have tried the following:
refreshing the list using F5, rebooting the cRIO, and using the IPreset switch
reinstalling drivers on the computer using September 2011 NI System Driver Set CD
manually adding the a new remote VISA system in MAX (tells me that a device is already using that IP address)
manually adjusted the LAN settings in the Windows control panel and disabled DHCP
edited Internet Protocol Version 4 (TCP/IPv4)
manually set IP address and local subnet mask to match the cRIO settings
Added exceptions to the Windows firewall
NI-RIO RPC Server
VISA Interactive Control
I think that the software and/or drivers on either the computer or the cRIO may not be up to date or compatible with the rest, but I'm not too sure on how to install software on the cRIO if I cannot see it in MAX.  Any ideas?
Thank you!
Solved!
Go to Solution.

Zach-H wrote:
To add the device manually you need to select "Remote Device (not on the local subnet)" not "Remote VISA System". The cRIO should try and default to a link local IP address (169.254.x.x Range) if it can't communicate with a DHCP server. This will likely be the case with the cRIO connected directly to the computer.
If your computer isn't on an agreeing IP and subnet mask its likely that the cRIO wouldn't show up unless you add it manually. You don't want to set them up as the same as the cRIO as they need individual IP addresses. I would recommend setting the subnet masks the same and adding one to the last number of the cRIO's IP address, which should allow it to show up in MAX.
Very useful document for this kind of a situation: http://digital.ni.com/public.nsf/allkb/abe4bc247e8ac9bc8625734e005cab42?OpenDocument 
When I tried to add it as a "Remote Device (not on the local subnet)," I got the error message "The device at this address is not supported by the drivers installed on this host."  I checked that my version of NI-RIO 4.0 is compatible with the cRIO-9073.
Also, I ran through the link you provided, and the steps did not remedy the problem.  When I ran the cRIO with the CONSOLE OUT switch ON, I was able to get lots of information from the cRIO in the command prompt in Windows.  This makes me think that there are no problems with the cRIO, but with the software I have installed on Windows.  I'm not sure what else I can try to install, though.

Similar Messages

  • PXI-8532 DNET card is not detected in MAX

    Hi all,
    I'm using NI PXI-1031(4 slot PXI chassis). I have the following cards in the respective slots
    Slot 1= PXI-8106 Controller
    Slot 2= PXI-6259 card(AI)
    Slot 3= PXI-6509 card(DI,DO)
    Slot 4= PXI-8532 Card(DNET)
    In MAX(Measurement & Automation Explorer), I was expecting all the above cards(PXI 6259, 6509 & 8532) to be detected under Devices and Interfaces. But only the AI and DIO cards are detected in MAX under Remote Systems>>PXI>>Devices and Interfaces.
    PXI-6259 (PXI1 Slot2)
    PXI-6509 (PXI1 Slot3)
    The device net card, PXI-8532 is not detected in MAX. Does MAX shows/detects the DNET card?
    In MAX, I selected Tools menu>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, I pressed OK. A message appears that no device is found.
    Can any one help me how to detect the DNET card in MAX and do the DNET port configuration?
    DNET driver version - 1.6.4
    Thanks,
    Raja
    Solved!
    Go to Solution.

    Dirk,
    Thanks for the reply. After updating the new driver, I am able to detect the DNET card PXI-8532 in MAX
    New driver - NI-Industrial Communications for DeviceNet 2.1
    But Im not able to configure the Device Net port. In MAX, I selected the menu option Tools>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, a message appears that no device interface is found.
    By default, the DNET0 port is configured for the card in MAX. So I tried to communicate from LabVIEW using DNET0 port.
    After installing Devicenet 2.1, an additional function palette has been added for DNET in LabVIEW.
    Old DNET function palette - Instrument IO>>DNET
    New DNET function palette - Industrial Communications
    My original application was written with old function palette VIs which corresponds to DNET 1.6.4 version. In the download link that you shared has a description about the driver compatibility. The description says still the DNET card PXI-8532 is compatible with NI-DNET 1.x LabVIEW VIs.
    With the old DNET VIs, I tried to establish communication with DNET interface port "DNET0". But it shows error while opening the interface.
    Error Code ="-1074388957" - The Interface is invalid or unknown.  Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
    With the new DNET VIs(DNET 2.1.0), Im able to open the DNET interface successfully. But my original application was written in Old DNET VIs (DNET 1.6.4).
    1. Do you know why the DNET 1.6.4 LabVIEW VIs are not working with PXI-8532 DNET card?
    2. Can you help me how to configure DNET port in MAX for PXI-8532 DNET card?
    Thanks,
    Raja
    LV 2009, Windows XP

  • Pxi not detected under max

    Hi...
    I have aPXI 1000B chassis with 8156B controller, i am trying to make the pxi get detected under MAX for 1 month now... still no result... i don know what the problem is...

    i am using windows xp. the labview version is 7.1 with a 7.1 real time. the max version is 3.3 and the controller is 8156B with 1000B chassis. the pxi doesnot boot into anything, but when i connect a vga port the boot screen look like the one in photo i have attached.
    Attachments:
    8156B controller.jpg ‏319 KB
    pxi boots to this screen.jpg ‏311 KB

  • CDAQ-9181 not detected in MAX

    I have NI device which I am trying to connect to in NIMAX however it just not getting connected to it or searched. But I see it running in NI Network browser with some random ip address which I can not ping. Hence I can't configure that device in Network browser either. 
    Any Idea what's wrong? or if there is any utility to configure it? Or it's a NI-DAQ version problem. ??
    I tried NI - MAX 5.1, 5.5 & 5.6 but no use, they all failed to detect it. 
    Where I can download just the device drivers but not whole NI suite?

    Hi prabhushrikant-
    Which version of NI-DAQmx are you using currently?  You can download the latest version here, but make sure first that it meets your O/S and LabVIEW (or other NI software) compatibility requirements.
    What 'random ip' do you see in the network browser for the device?  What happens if you try to click on the link in the network browser?  Can you tell us more about the networking setup on your PC and network?  Do you have multiple NICs in the PC?  What are their networking settings set to (DHCP, static IP, etc)?
    Tom W
    National Instruments

  • Board not detected from MAX

    The machine is equipped with NT4.0 sp5, and was using an old PC-TIO-10 with NIDAQ6.1.
    We decided to sobstitute the board with a PCI-6023E, as we needed some analog signal inputs.
    We installed NIDAQ6.8.1 (without first uninstalling 6.1 version), put away the PC-TIO-10, and installed the PCI-6023E.
    Once MAX opened, it showed the PCI-6023E, but also continued to show the PC-TIO-10 board. We manually removed this old board from the list("delete"). But, at successive MAX openings, it was impossible to find the PCI-6023E board, also refreshing or setting the preferences at "every time I launch MAX".
    We tried unistalling and reinstalling NIDAQ6.8.1, reinstalling NIDAQ6.1 so to try to uninstall it, restarting the machine many times, changing slo
    t for the board, but we never more managed to see the PCI-6023E board among the devices.
    Now the system is on, the board is in the PC, NIDAQ6.8.1 is installed, but we have not the way to use the board.
    We cannot reinstall all (NT, applications, etc.) as the PC is on a plant and cannot be stopped for more than a few minutes.
    We are sure that no secondary things may have caused the problems (bios settings, applications, etc.) as the first time after installation the board was correctly recognised.
    Many thanks.

    Moroli
    Here is what I would suggest to do.
    1. Uninstall NI-DAQ
    2. Clean the registry
    -Click on Windows 'Start' Button and goto 'Run'
    -Type in regedit to open the Registry Editor
    -Follow this path: HKEY_LOCAL_MACHINE >> Software >> National Instruments >> NI-DAQ
    -Delete the NI-DAQ folder
    -Shutdown computer and take out PCI-6023 board
    -Reinstall newest version of NI-DAQ
    (NI-DAQ 6.9.1 can be download from ni.com
    -After installation is complete, put PCI-6023 board back in computer
    By going through these steps, you should be able to use your board normally.
    Brian

  • 7332 is not detected in MAX

    Hi,
    We have a PCI NI7332 motion controller purchased with us. We installed the drivers and softwares  from the cd that comes with the package. The problem is PCI NI7332 showing as NI7330 in MAX . Anyway its listing the two axis in max. When i tried to connect an encoder and read it in MAX nothing is happening.  Do i have to change any setting when using the board for the first time?
    With regards,
    Jerry

    Jerry, 
    I don't quite understand this:
    " The problem is PCI NI7332 showing as NI7330 in MAX . Anyway its listing the two axis in max. "
    I'm assuming that the board just isn't showing up in NI-MAX.  If you are running Windows, I would go to the Device Manager on your machine and make sure the computer is recognizing it first (I'm not familiar with the Mac equivalent of this).  If the computer is not recognizing it as a piece of hardward installed on the motherborrd, there may be a bad connection.  Restarting the computer is also not a bad idea just to make sure everything is operating correctly.
    Hope you get it figured out.
    Adam

  • PXIe-1073 not detected

    I'm trying to install a PXIe-1073 chassis on a new Dell system running Windows 7 x64.  I have the latest version of Labview, NI-DAQmx, etc.  The PCI express controller shows as properly installed in the Device Manager ("PCI standard PCI-to-PCI bridge").  The chassis and installed DAQ card are not detected in MAX.
    I am actually transferring this system from an older computer.  I recall having exactly the same problem before, and I'm fairly certain I solved it by installing the "MXI-Express BIOS Compatability Software".  There was never any way to actually identify the "PXI System" as anything other than "External PC" even when it was working properly.
    After installing the current version of the MXI-Express software, I rebooted and was able to load MAX briefly before Windows BSODed with an error involving "niraptrk.dll".  This proceeded to occur every time I tried to load Windows.  I was able to start in safe mode, but attempting to uninstall any NI software gave me an "error 1601".  I was finally able to load the last known good configuration and uninstall the software.
    When I checked MAX again, the chassis was still unrecognized, but there were multiple broken entries for the DAQ card installed in it, so I assume it was detected at some point.  It looks like the MXI-Express software worked, but it's obviously unusable if it causes the computer to BSOD every time Windows starts.  Why is the computer unable to recognize the chassis without it?  What else can I do to solve the problem?

    Hello Bob_mcbob,
    After looking over this issue, I think we have a problem with the Windows installer on your machine. I have found a KnowledgeBase about the Error 1601 stating that this is a Microsoft Windows installer error and that the installer will need to be reinstalled. The Knowledgebase explains how to do this.
    As for the BSOD, do you have any more information that it provided when this occurred like the address line, etc? Did you do something in MAX before it crashed?
    Since accessing MAX now gives you a BSOD, I think it would be best to uninstall/reinstall the drivers to fix the issue. What cards do you have in this system?
    Jim St
    National Instruments
    RF Product Support Engineer

  • SCXI-1102/SCXI-1303 not detected in SCXI-1000 chassis

    I am using a setup with SCXI-1303 module in a SCXI-1102 within a SCXI-1000 chassis to take voltage and thermocouple measurements.
    Until recently, everything was working fine. but it now appears I am unable to communicate with the interface. I have tried two different computers and the hardware is not detected in MAX. The power light and fan on the SCXI-1000 still comes on, there just appears to be no acknowledgment of the connection to the computer.
    A few more specific error codes:
    * When I double-clicked the DAQ Assistant in the block diagram window and clicked "Test" on one of my inputs, I received the following error:
    "Error -88705:The specified device is not present or is not active in the system."
    * I have also gotten the error code "Error -89130: Device not available in NI-DAQmx" in the DAQ Assistant test panel
    * When closing the DAQ Assistant test panel, I see the error "Error -89130: Device not available for routing"
    * In MAX, if I try to "test" the chassis or module, I have seen errors either saying that the device is not detected, or that the device needs to be reset or is in the process of being reset, or that Traditional DAQ drivers need to be reset (I've tried these reset suggestions with no result)
    At this point I'm wondering if the board or the cable is shot. I unfortunately don't have another 68-pin cable to test at the moment.
    Thanks in advance...
    Solved!
    Go to Solution.

    mtd12 wrote:
    Thanks guys, I was able to resolve the problem. For anyone who might come across this,
    * I noticed in Windows Device Manager that two PCI devices were listed as not being installed properly.
    * After trying to update the drivers, I couldn't start the computer; got BSOD after BIOS load.
    * Some research prompted me to pull out the two PCI cards that I was not using, and I also moved my DAQ card to another slot to force a hardware reinstall.
    * Booted up, loaded the drivers automatically, and off I went.
    Doesn't explain why it didn't work in the other computer, but in the words of Spinal Tap, the authorities said it was better left unsolved at this point.
    You should move the DAQ board back and verify whether it still works. Perhaps one of the slots went bad.
    You didn't notice that you had two PCI devices that were not installed properly before?

  • Parallel port not detected in measurement and automation explorer

    I have installed labview 2010 in windows XP.
    The problem what I am facing is I could not find "Serial & Parallel port" option in Measurement and automation explorer.
    After seeing the similar problem in forum I have installed Ni-Daqmx 9.0.2.  But still I can not see the ports in MAX.
    I think i have attached enough document .
    If the parallel port is not detected in MAX can we send digital data to parallel port.
    I have tested parallel port with LED connecting one leg in 1st data line(pin 2) and another in gnd(pin 25).
    And my program is to blink the led for every one second but I cannot see the blinking.
    Can anyone help in this regards
    thank you
    Attachments:
    max.jpg ‏90 KB
    port setting tab1.jpg ‏30 KB
    device manager resource tab.jpg ‏34 KB

    Thank you for ur reply Smercurio
    I have changed the bios setting now 
    but still i cant see the printer port in MAX
    Regarding my vi, now i changed it please see that also 
    I have given values to element of arrays as (1,2&4) 
    Now also it is not blinking instead it is glowing all the time without blinking.
    What i have to do next.
    Attachments:
    device manger.JPG ‏43 KB
    device manger2.JPG ‏165 KB
    port test.vi ‏9 KB

  • CRIO-9073 is not detected in "Measureme​nt & Automation Explorer" on my Win7(64-bi​t) system. Please help.

    When I connect cRIO-9073 with my Win7(64-bit) laptop via ETHERNET cable, it is not detected in  "Measurement & Automation Explorer".
    I have LabVIEW-2011 installed on my laptop.
    Please help..
    Thank you....

    Is this a new controller?  First time connecting?  Does the controller have an IP address set? 
    The Windows firewall may interfere with detecting a cRIO if it's the first time.  Make sure your fire wall is off and try MAX again.

  • MAX not detecting PCI 6259 connected to BNC 2120

    I have the DAQmx driver 9.0.2
    I have the card (PCI 6259) in a windows XP machine
    The breakout box is a BNC 2120
    MAX does not detect any devices and interfaces.
    Thanks for any help,
    Fmiles

    Does your device show up in Device Manager under data acquisition devices?  If not than it is not being recognized by the computer and you should try moving PCI slots on the card.  If it does not show up under data acquisition devices, right click on it and select uninstall, restart the computer and it should install on its own again.
    Was the card installed during the DAQmx install, try reseating the card.
    Make sure the NI Device Loader Service is started in Control panel»Administration»Services.  It should be set to started and automatic.
    Does DAQmx 9.0.2 appear under Software in the Configuration Pane of Measurement and Automation Explorer, if not, it may not have installed correctly.
    Doug Farrell
    Product Manager - Condition Monitoring
    National Instruments
    National Instruments Condition Monitoring

  • NI 9014 is not detect NI network browser and MUX

    Hi,
    I have been dealing with NI cRio 9014.
    Now, I face a problem with detecting the cRio in MUX and NI network browser after upgrading  the new drives and Labview software. Simply it doesn’t detect at all. I have set correct subnet and IP in my machine.
    Currently install configuration in my machine is shown below
    MUX version = 5.3.0f0
    LabVIEW version =  11.0.1f2 (32bit)
    OS = Windows 7
    I could barely detect the device if I right click on the remote systems in MUX, Create New, Remote Device (not on the local subnet) and then enter the IP address. But I am 100% sure that I have set the correct local subnet in my machine. Interesting even if the NI 9014 is force to detect by this way it still be undetected by NI Network browser.
    In the XP machine, in which MUX version 5.0.0f1 and LabVIEW 10.0.f2(32 bit) installed in, detects NI 9014 within a second.
    This problem is a big headache for me. Specially, after format the disk from W7 machine it is not detected whatsoever from the same machine  and have to reformat the disk from xp machine and need to be configured from the xp machine.
     If you guys could help me to fix this it would be really nice.
    Thank you in advance.

    Hello,
    If you still has problems to detect the cRIO-9014 in MAX you can start to have a look at the points suggested in this article:
    http://digital.ni.com/public.nsf/allkb/ABE4BC247E8AC9BC8625734E005CAB42?OpenDocument
    Especially the points about the firewall and compatibility could be of interest. What software is installed on the cRIO?
    Please let us know how it goes.
    Best regards
    Richard

  • PCI-7344 not found in MAX 3.1.1 after installing NI-Motion 7.0

    Hi,
    I updated my PCI-7344 + LabView 7.0 system with the newest NI-Motion 7.0. After the update the card was not anymore detected in MAX. There was a "broken" device PCI-7344 under NI Motion Devices, which status said something like "This device has been removed or could not be detected" and the Reset command said something like "Could not communicate with the device. Power cycle the computer..". I removed the device from the "Devices and interfaces" list and since that, MAX hasn't had a clue about the card. I've tried the "Create new.." function, but it doesn't show any NI Motion Devices or PCI-7344 anywhere else. I've also tried the Tools/Install legacy driver support, but MAX only notifies that the updates are OK. I've also tried removing the physical device, starting the computer and MAX, reinstalling the device and restarting MAX, but nothing changes. The device is recognised by BIOS as "Unknown device"; in Windows 2000 Pro, the device is well recognised as National Instruments PCI-7344.
    One thing that could cause the problem is that I also have LabView 6i installed on the system, although I'm not currently using it for any purpose. Anyway, this seems to prevent the MAX from detecting the correct updates needed when using the "National Instruments Product Updates.." from Tools menu. Perhaps I need some driver software to correct this problem?
    I also tried to uninstall the NI-Motion 7.0 and to install the NI-Motion 6.1.5, but after this, the MAX did not work correctly. For example, none of the branches in the configuration tree would expand and the MAX locked up when trying to use the Create New.. / NI Motion Device. Is there a way to uninstall the NI-Motion 7.0 and to replace it with NI-Motion 6.1.5 without removing all NI software from the system?
    Before the update, with NI-Motion 6.1.5, the PCI-7344 card was correctly found in MAX and well usable in LabView 7.0.

    Jouni,
    A valid serial number is any number > 0. If you have multiple boards in you system, they must each have a unique serial number. This would be the case for any board coming out of manufacturing. The board Jochen had probably came from R&D and was a prototype board.
    Your problem with downgrading from NI-Motion 7.0 to NI-Motion 6.1.5 was most likely due to the data stored in the MAX database. When you uninstall NI-Motion, the data in the MAX database remains. The NI-Motion 6.1.5 driver would not have been able to read the data correctly. The easiest way to "clear" this database is to delete the c:\Program Files\National Instruments\MAX\data folder. The only other way is to uninstall MAX, which requires that you uninstall everything. WARNING, Deleting the MAX data folder will delete all MAX settings and set them back to defaults for all NI hardware (uninstalling everything has this same affect, by the way). Downgrading is never as clean as upgrading.
    The firmware on a Motion board can always be downgraded by forcing the download of firmware files. To do this, select the board in MAX under Devices and Interfaces. Click on the Firmware tab at the bottom on the window. Highlight "PCI-73XX Firmware" by clicking on it once. Right click on one of the items in the "Firmware name" column to the right. Select "Download All Files".
    I do not have a good explaination for why NI-Motion 7.0 did not recognize your board. Do you have a second board you can try in the system? If not, could you ask your local sales representative if they have one you borrow for a quick test? Since the board is recognized by Windows 2000 Device Manager, I don't think there is an issue with the board, but it doesn't hurt verify this.
    My best guess is that there was a confict during the installation process and your system did not get all of the required files. Though we do significant installer testing, there are rare occasions when a system is in such a state that the installation process does not function as expected. It is my experience that these rare instances do not occur on clean machines, but on machines that have had multiple products installed and uninstalled. If you do get a chance to try NI-Motion 7.0 again you may want to use these parameters to get the installer to create a log of the installation: "c:\setup.exe l*v c:\log.txt". This assumes that the setup.exe is in the c:\ directory. Go to start>>run and type this in without the quotes. The log file will be named log.txt in the c:\ directory.
    Finally, you can technically use NI-Motion 7.0 in LabVIEW 6. You just need to copy the C:\Program Files\National Instruments\LabVIEW 7.0\vi.lib\Motion folder to the vi.lib folder of LabVIEW 6. Though this is not officially supported, there is no reason it shouldn't work.
    Regards,

  • Docsis 2.0 and 1.1 cable modems are not detected via UBR-MC20X20V-5D line card

    Hi All,
    We have uBR10K series CMTS and recently installed UBR-MC20X20V-5D line card, requirement is to configure this line card to support docsis 1.1 and 2.0. Problem is after finished the configurations modems (Hitron and Motorola) are not detected by the system. means no modem mac address listing under "Show cable modem" command. 
    Our CMTS has the following components
    ESR-PRE2: x1
    ESR-PRE-MEM-FD128: x1
    UBR10-DTCC:  x2
    UBR-MC20X20V-5D: x1
    iOS version:     12.2(33)SCE3
    Part of running-config as follows
    cable spectrum-group 13 band 22800000 26600000
    controller Integrated-Cable 8/0/0
     rf-channel 0 cable downstream channel-id 145
     rf-channel 0 frequency 501012500 annex B modulation 256qam interleave 32
     rf-channel 0 rf-power 59.0
     no rf-channel 0 rf-shutdown
    interface Cable8/0/0
     no cable packet-cache
     cable bundle 1
     cable upstream max-ports 4
     cable upstream 0 connector 0
     cable upstream 0 spectrum-group 13
     cable upstream 0 channel-width 3200000 3200000
     cable upstream 0 docsis-mode tdma
     cable upstream 0 minislot-size 2
     cable upstream 0 range-backoff 3 6
     cable upstream 0 modulation-profile 21
     no cable upstream 0 shutdown
    diag output attached herewith. Please any one advice on how to resolve this issue.
    Thanks in advance.

    Hi All,
    We have uBR10K series CMTS and recently installed UBR-MC20X20V-5D line card, requirement is to configure this line card to support docsis 1.1 and 2.0. Problem is after finished the configurations modems (Hitron and Motorola) are not detected by the system. means no modem mac address listing under "Show cable modem" command. 
    Our CMTS has the following components
    ESR-PRE2: x1
    ESR-PRE-MEM-FD128: x1
    UBR10-DTCC:  x2
    UBR-MC20X20V-5D: x1
    iOS version:     12.2(33)SCE3
    Part of running-config as follows
    cable spectrum-group 13 band 22800000 26600000
    controller Integrated-Cable 8/0/0
     rf-channel 0 cable downstream channel-id 145
     rf-channel 0 frequency 501012500 annex B modulation 256qam interleave 32
     rf-channel 0 rf-power 59.0
     no rf-channel 0 rf-shutdown
    interface Cable8/0/0
     no cable packet-cache
     cable bundle 1
     cable upstream max-ports 4
     cable upstream 0 connector 0
     cable upstream 0 spectrum-group 13
     cable upstream 0 channel-width 3200000 3200000
     cable upstream 0 docsis-mode tdma
     cable upstream 0 minislot-size 2
     cable upstream 0 range-backoff 3 6
     cable upstream 0 modulation-profile 21
     no cable upstream 0 shutdown
    diag output attached herewith. Please any one advice on how to resolve this issue.
    Thanks in advance.

  • Change of modes not detected

    I have a yoga 2 13.My laptop does not detect any change of modes i.e it does not activate tent/theatre/tablet.Is there any solution for it or is it a manufacture defect since i was facing the problem from the beginning.Please suggest.  

    Try pressing the rotation lock buttons. 
    Also, install my yoga patch. If it detects slate/laptop mode, it is a software problem, not a hardware problem.
    indest wrote:
    RC8: http://alltechtalk.net/Yoga_Patch.exe
    Just an FYI, this is a RC, not the final product.
    As always, use at your own risk.
    Please report any/all bugs
    Change log:
    RC8.1 Fixed the notification bug, when the screen was resized; ALT + L hotkey activates the Lock.
    RC8: Fixed Lock Password bug, Fixed Lock Siren Bug, Auto max audio upon Lock start, Blocked Muting/Volume down on trigger) when Lock is activated; Added BT Toggle Hotkey Alt+B (thank miru)
    RC7: Added "Yoga Lock" to the program (via tray menu).*****
    RC6:  Removed Battery info to eliminate redundancy with windows app; Refined System Up-time code; Added Estimate Usage Cost (Eco-Friendly initiative)
    RC5: Added Power Plan changer to the trey menu; Added Battery Info, Bug Fixes
    RC4: Update detector/downloader; Fixed "Disable Touchscreen on Boot" bug, cleaned up the Settings app; added quick resolution buttons to the tray menu.
    RC3: Added a Disable Touchscreen on Boot option; Fixed spelling errors.
    RC2: Hopefully fixed the Slate Mode Notification Bug; Auto-Disable Touchscreen, if Touchscreen was disabled before slate mode
    RC1: Notification bug fix; changed the path of the trigger file to AppData; made an installer
    V. 0.5.1 Added DPI support
    V. 0.5: Added a "Close" button disabler (the button next to the volume up button.... this addition prevents accidental program closer); Modified the settings apps; Improved Notification Bar; Removed Tooltips (replaced with Notification Bar) 
    V. 0.4: Added Notification handler for Slate Mode/Laptop Mode; Modified the settings apps; Added tray menu; Removed the Alt + X close hotkey, since try menu was added; Fixed minor bugs
    V. 0.3: Added Power Plan Toggle on Power State change; Added a Settings App; Added switches to the Patch
    V. 0.2: Added Trackpad Fix****
    V. 0.1: Touchscreen Toggle
    ****The trackpad fix only works with generic synaptic drivers. To install the latest driver (17.0.19), please do the following:
    1. Disable signature enforcement: https://www.youtube.com/watch?v=NM1MN8QZhnk
    2. Install the synaptic driver: 17.0.19
    3. Install the aforementioned patch
    Yoga Lock Description:
    Ever wanted to go to the bathroom at Starbuck or in the Library? Afraid to leave your laptop behind? If so, this Lock was made for you.
    Disclaimer: I shall not be held liable for any stolen property!!! As always use at your own risk and please use your brain!
    Once activated the lock has the following potential:
    Covers your entire screen.
    Blocks perpetrators from accessing your desktop.
    Prevents USB drives from being stolen, via Siren Deterrent.
    Helps deter thieves from taking your laptop.
    What can trigger the Lock:
    The slightest mouse movement.
    Removal of a USB drive.
    Attempted power down of the computer (future goal is to suspend all attempts of powering down).
    Change in AC status (i.e. unplugging the computer).
    When triggered, the lock has the following potential:
    Take a picture of the person who triggered the lock and email the picture to you (passwords are encrypted).
    Loud siren is played.
    Activation of any script you write. This essentially opens this feature to endless possibilities. Currently, I utilize this feature to report my computer as stolen to the prey-project's control panel (this script is not fully functional and will not be packaged with this application).

Maybe you are looking for