Jump to content

Gribo

Members
  • Content Count

    132
  • Joined

  • Last visited

  • Days Won

    4

Gribo last won the day on September 18 2019

Gribo had the most liked content!

Community Reputation

17

About Gribo

  • Rank
    Very Active

Profile Information

  • Gender
    Male
  • Location
    Toronto, Canada

LabVIEW Information

  • Version
    LabVIEW 2015
  • Since
    2006

Contact Methods

Recent Profile Visitors

2,591 profile views
  1. Type object is in the System namespace. Click .NET connectivity -> Invoke node -> Select class -> System -> Type -> Missing
  2. Here you go. This is not a production code. You will have to close references when you are done with a specific object. 2 things to note: 1. Excel, like VB is 1 based. 1st index is 1. 2. Don't leave an empty property node input. Wire a 'missing' type to any gray (optional) input that you don't use.
  3. The DAQmx objects depend on the VISA version installed on the PC. Somewhere between 2010 and 2015 there was a change and recompilation was required.
  4. You should use the Excel .NET API. You will see your data as it is added to the spreadsheet. Also, you can do this with OpenOffice/LibreOffice if you don't want to pay for Excel.
  5. Where do you write to the different queues? Does it work with only one PLC?
  6. If you know there are no more bytes in the buffer, then you can ignore that error. That is, if the packet size is fixed, and you are receiving correctly, you don't have to reach the timeout. Also, you can set the timeout to a value less than 10 seconds, if you know that all transactions occur before the time is up.
  7. Shameless plug: Here is another example of WebSockets:
  8. Get one, worst case, your slightly older laptop will get a memory upgrade.
  9. Way too many meters of LMR200 inside a 1U enclosure to be comfortable with. Hey, it works!
  10. The Excel .NET API behaves better with LabVIEW than the ActiveX one. From your point of view, they are the same, so why not use .NET?
  11. Don't mix 32 and 64 bit pieces of software, it will not end well.
  12. At the risk of sounding petty: I am using Windows, so the first thing that comes to mind are the GUI Conventions: LabVIEW Undo is ctrl+z, LabVIEW Redo is ctrl+shift+z, while Window's Redo is ctrl+y. There are many more such (minor) design choices. The application should use the OS conventions, not force its own way. And, as an ambidextrous person, Scissors should be designed for both hands.
  13. I have managed to solve it by replacing the EMGU ImageBox control with the standard .NET PictureBox.
  14. I use the Win32 call to bring the current window to the front. LV's bring to front doesn't always get the desired result. I avoid LV's Modal windows, mainly because other Win32 windows might be on top of them. If I do use a pop-up panel, it will have that Win32 call in the timeout event handler. It is annoying to the user, but its the only way I can be certain the user sees the window.
  15. Hello all, I am using EMGU Wrapper and OpenCV with LabVIEW 2017 and I am getting an odd crash. When ever I resize the VI front panel, LV crashes without any warning or prompt. I use the latest OpenCV (4.1.1) and EMGU libraries. EmguOpenCV test.vi
×
×
  • Create New...

Important Information

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