Jump to content

bbean

Members
  • Content Count

    245
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by bbean

  1. This is a long shot here, but do they all need to run in the UI thread but their preferred execution system is set to "same as caller" and then something gets screwed up when they are called by dynamic dispatch in the runtime? What happens if you set their preferred execution system to "user interface" and retry.
  2. bbean

    Things I Hate

    agreed. As part of my trials and tribulations with MAX I had to repair NI VISA. With NIPM18.5? no option to do that so they recommend uninstalling and reinstalling...fair enough. Tried that and NIPM wanted to uninstall LabVIEW..wtf. Upgrading to the latest version of NIPM (19.6) provided a better experience allowing you to repair installs now.
  3. MAX That is all.
  4. Is the latest version 1.10.9.115? Is there another higher version somewhere because that one seems to still have the issue.
  5. Has anyone used IPFS as a tool for storing and distributing test data (multiple gigabytes)? My use case would be to run tests that store data on local windows machines and then distribute that to other users who may have linux, windows etc and also to a centralized archiving location. The users and test machines are in a relatively strict network environment and most users machines are locked down. Some of the linux users may have elevated privileges to install things like ipfs but I'm worried about a typical windows user who may want to get the files easily without having to go through a b
  6. Thanks for the quick response. its a rather annoying problem. I think this may have been the problem but wont know until I test again on Monday. You are correct that its a PM320E. And so far their driver has been a pain. The suspect command is the error query the parent class implements by default "SYST:ERR?" but PM320E requires ":SYST:ERR?". A nuance (nuisance) that I failed to notice. PS. I think I may have borked the instrument up by upgrading the firmware too. Oh well thats what you get for trying to get something done before a holiday weekend.
  7. I have an issue where reading the VISA Instr Property "Intf Type" of a USB Instrument hangs for about 40 secs: followed by an asynchronous VISA Write hang for 2+ minutes! The timeout on the VISA instr session is set to 1000ms. Here are the other details of the session: and here's a snip of the VI: Any idea why these long timeouts are occurring? or why the 1000ms timeout is being violated for both the Instr property call (no idea what goes on under the hood here) or the VISA write.
  8. If that doesn't work you may have to separate the TestStandAPI calls out. Are you using your TestStand Actor as a GUI or user interface? If so you may have to create another Actor to separate out the TestStand API calls that are causing the log jam into a new Actor....That new actor should not have any property/invoke nodes which would force its VI into the UI thread.
  9. I would imagine the string 127.0.0.1 (or u32 Net Address 2130706433)
  10. I worked on some Ethercat issue a few years back and remember that at the time the cRIO doesn't support Beckhoff array datatypes and we had to make individual IO variables for each item in the array on the Beckhoff side. Were you able to import the XML file OK into the LabVIEW project?
  11. never mind. found a work around to my problem. I was getting runtime errors whenever I saved my VI with the activex control saying the control doesn't support persistence. I fixed by saving a null variant to a connection property before exiting the vi and the problem went away
  12. Did you have any luck with solving this issue? I'd like to do the same thing.
  13. Curious how your company worked or works out the OS licensing. I tried to go down this rabbit hole with MS a couple of years ago and ended up giving up because it was so difficult to figure out for a small business.
  14. Yeah I could see that being helpful at some point. What happens when you have more than one primitive/Subvi on the diagram in the node? Does it just place another entry at the bottom of the unbundle?
  15. If you don't need to do FPGA image processing, I would explore the other options for Camera Link cards that are not FPGA based and see if they will work with Pharlap With regards to the FPGA example, this may be a long shot If you haven't compiled FPGA code and I'm not sure it will work at all. I don't have time right now to fully explain but to summarize: Open the example 1477 getting started project Save a copy of the project and all VIs to a new location (so you don't overwrite the working windows target version from NI) Close the off the shelf example project
  16. I guess I would need to know about your requirements, but I think that would be a road less traveled. Do you need base, medium, full or extended full? do you need power over camera link? etc. Why do you need real-time? In the future I would recommend talking with Robert Eastland and purchasing all your vision related hardware /software from Graftek. He has been extremely helpful with me in the past and knows his stuff. I have no affiliation with the company. Did you try my suggestion to compile the example FPGA code and move the host example to the real-time target to see if its
  17. Unfortunately, the card probably does not work directly in LabVIEW Realtime. NI's specifications and documentation are often vague with hidden gotchas. I had a similar problem with an NI-serial card years ago when Real-time and FPGA first debuted. I wanted to use the serial card directly in LabVIEW real-time with VISA, but I ended up having to code a serial FPGA program on the card because VISA did not recognize it as a serial port early on. Is there anyway you can try to compile the FPGA example and download it to the card? C:\Program Files (x86)\National Instruments\LabVIEW 201
  18. At least for the 1473R according to this: https://forums.ni.com/t5/Instrument-Control-GPIB-Serial/My-Basler-acA2040-180km-NIR-is-not-visible-in-NI-MAX/m-p/2402066/highlight/true#M59080 "The NI PCIe-1473R Frame Grabber contains a reconfigurable FPGA in the image path enabling on-board image processing. This means that the full communication between the camera and the frame grabber goes through the FPGA. It is then a major difference comparing to the other standard frame grabber without FPGA. "It means also that the camera will not shows up in Measurement & Automation Explore
  19. TCP is not free of pain either though. I've been on networks where the IT network traffic monitors will automatically close TCP connections if no data flows across them EVEN if TCP keep alive packets flow across the connections. For whatever reason the packet inspection policies effectively ignore keep alive packets as legitimate. We ended up having to send NO-OP packets with some dummy data in them every 5 minutes or so if no "real data" was flowing.
  20. You would have to create/send the packet header(s) as defined by RUDP in each data packet in LabVIEW on pharlap side by placing it before the data you send. Then you would have to send a response packet with the RUDP header(s) on the LabVIEW host side based on whether you received a packet out of sequence (or invalid checksum, etc). You would effectively be creating your own slimmed down version of TCP at the LabVIEW application layer. Quite a pain unless absolutely necessary.
  21. you could try installing pyvisa-py (partial replacement for ni-visa backend) on the rasberry-pi and see if it can implement remote sessions eg. visa://hostname/ASRL1::INSTR .It doesn't look too promising based on this discussion, https://github.com/pyvisa/pyvisa-py/issues/165 but it seems to indicate if you know the address and don't rely on the pyvisa-py resource manager it may work.
  22. This. I tested NXG for the first time at a feedback session during the CLA summit. So I was learning NXG on the spot in front of one of the NXG developers. When I would get stuck trying to figure it something out, the developer would ask how would you do that in legacy LabVIEW and I would tell him, then he would show me how to do it in NXG. My understanding was that the NXG IDE was designed to make the number of programming number steps more "efficient". Unfortunately this sometimes sacrifices the many years of muscle memory doing things in legacy LabVIEW. A bad analogy would be br
  23. thanks for all the feedback. its why i love this site.
  24. Is there anyway to do this without MAX? or a description of what happens when MAX executes the format? Unfortunately no Windows boxes are allowed in the previous mentioned "secure" area. So the wipe needs to be done without MAX. Once the cRIO is wiped it can leave the secure area and all normal NI stuff (MAX, RAD, windows) can be used. As someone told me, its the security policy it doesn't have to make sense.
×
×
  • Create New...

Important Information

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