Jump to content

task

Members
  • Content Count

    32
  • Joined

  • Last visited

Community Reputation

0

About task

  • Rank
    More Active
  • Birthday July 15

Profile Information

  • Gender
    Female
  • Location
    Michigan

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since
    1994
  1. I'm running Windows 10 and Labview 2014 sp1. For some reason now I cannot do an ALT-TAB to look at my diagram while I'm running a program. The screen comes up but it will not allow me to select it. Did I miss something in Labview? Thanks.
  2. I have a PXI that hosts a shared variables library and a PC running a user interface program. Through the NI Distributed System Manager I can see the shared variables update but the PXI only updates the variables back to the PC if the PXI program is running on a development computer. Simply put, PXI address is 169.254.1.100, interface PC address is 169.254.1.105, development computer is 169.254.1.108. On the PC I enter Width and Height, the PXI calculates Area which is then displayed on the PC. If the PXI program is NOT running on the development computer, I see the Width and Height values u
  3. Not sure if this is the correct forum area for this question...I usually use an Automation Direct CMore HMI to interface with my PXI systems using Modicon Modbus TCP/IP. On a new project, my customer suddenly decided that they need to use a keyboard and mouse instead of a touchscreen and they want at least a 19" monitor. The CMore is only available in 15" and you cannot use a keyboard and mouse. I found one 19" HMI from Beijer Electronics, with a $5500 price tag and of course, new design software to be learned. If anybody out there has any experience with large HMI's that can be interfaced w
  4. I have it installed on my laptop so I can keep working on it at home but there is an issue that I'm currently working with NI on...MAX will not function correctly on the laptop even though it does on another identical one. Very frustrating. I was on the phone with tech support last Friday for 4.5 hours to no avail. I need it to work because I can't haul my desktop with me when I travel to load updates on my realtime PXI systems. I decided to clean up my old code first and then start manipulating it. Worst case scenario, I know the old code works fine. This is probably the best project to expe
  5. Thank you MikaelH and Daklu...I will be looking at the links in a bit. I will be using the bulk of my existing program since I know it works on 3 other machines but I am embarrassed by it! Daklu, I have no idea why the two parallel loops inside of another main loop, I believe I had an issue with both stopping at one point. Probably overkill. 99.99% of my customers never see my code but one time I had a customer basically hand my a$$ to me over how bad my coding style was! He had been afforded the luxury of taking every available class from NI and worked at a very large company where he basica
  6. I have written many, many programs in LV but I'm sorry to say that I have not kept up with upgrading my coding skills. The last few years I've only written very simple programs that didn't have to do too much. We are a very small company that has really been struggling so taking a training class is not on the menu but I'm having a hard time finding examples, the examples I find are so simple. My problem is how to go about selecting a design pattern. I am upgrading/enhancing a program that I wrote over 10 years ago and obviously want to use good techniques. I understand all the concepts but st
  7. task

    canexpert error

    I cannot install any NI-CAN drivers on my Dell Vostro 1510 laptop. I've done numerous uninstall/reinstall procedures to no avail. The desktop I use for development works fine, all identical software was installed on both machines in the same order. I can install the XNET drivers but cannot include anything relating to CAN, even older drivers. What happens is that when I click on the + in front of software, nothing shows up, and no remote systems are displayed (I have a PXI attached). The PXI shows up fine on the desktop. My newer benches have the latest XNET PXI card installed but the older
  8. Found it...looking through the NI site I found a blurb regarding software updates being installed after drivers. Exactly what happened. Apparently the DAQmx drivers were updated 6/18 and Labview 8.5.1 upgrade was installed on 6/20. Since the drivers were the exact same ones, they were not updated. Uninstalled all, reinstalled and problem disappeared.
  9. There are still problems!!! Everything works fine as long as I run the code from the host computer. As soon as I dump it into the RT module, none of the digital works. From what I understand, this happened before on one of the previous machines (I'm working on # 4 of 4). Our local NI rep was in, did nothing, the previous programmer played around with it, and things started working. Well, they don't now. The only difference, and this may have something to do with it, it's a different processor (PXI-8184), same model but physically a different one. We had a hard drive fail in the field (temperat
  10. The problem has been resolved. It was an initialization error. The default case would wipe out the task. Two other people (newbees) worked on this before me so I have a lot of clean up to do! Too many unnecessary variables, cases, etc. Thanks for the reply.
  11. Problem Description : Hardware: PXI-8184 (chassis PXI-1042), PXI-6221 (slot 2 in chassis) Software: LV RT 8.5.1, DAQmx 8.7.1 (see MAX.jpg), Windows XP Problem: Task does not function within program (CounterRead.jpg). I can run the task within MAX (MAX.jpg) while the program is running and I can see the counts. All other tasks work fine. I have eliminated everything else in my program except this task and it still doesn't function and I do not get any errors. I hate to upgrade any of the drivers, if they're available, because I have several other units out in the field with the same configu
  12. task

    Modbus in RT

    QUOTE(David Wisti @ Feb 1 2008, 04:41 PM) Resolved...I had to change the address of the "PLC" in the CMore. It was set to the PC and not the PXI. I put the ModbusSlave under the variables in the RT area (as I mentioned earlier). Now the PXI and CMore are communicating. Now I just have to adapt all the code I previously wrote under the PC for the RT system. Thanks for all the input.
  13. task

    Modbus in RT

    QUOTE(ned @ Feb 1 2008, 04:05 PM) The addresses are correct and I'm using them the correct way...everything worked fine when I was running the program under My Computer and not the Real Time Controller. I guess this is part of the learning curve on how to use the RT stuff. I moved the modbus stuff into the variables-network-RT(separate).lvlib and the "cycle error" went away but I am still unable to read/write anything. I'm doing what I think is logical and I'm probably missing something huge! I'll keep plugging away...
  14. task

    Modbus in RT

    Hi, I'm a long time labview user but new to using a PXI controller and RT module. Here's my dilemma... The PXI (PXI-8184) will be connected to a Automation Direct CMore touchpanel via modbus ethernet. No host PC will be present in the end. I have the PC and the CMore talking via modbus (CMore is the master, PC is the slave). All this works fine. Now I'm trying to write the actual RT code that will eventually run on the PXI controller. My problem is getting the modbus stuff to work. All the IP addresses and subnet masks are set up correctly. Under my PXI system I set up a ModbusSlave I/O se
  15. task

    Motion Control

    Finally got it to work after revisiting calculus and trig...glad my intern is a college student with this info still fresh. None of the examples provided with NI-Motion were very helpful except for the "configure buffer" one. Thanks.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.