Jump to content

Antoine Chalons

Members
  • Posts

    846
  • Joined

  • Last visited

  • Days Won

    26

Posts posted by Antoine Chalons

  1. Yep, I remember when Tim Dehne left NI, rumor I heard at the time was he wanted to become CEO and understood he would never make it, then left.
    Indeed it took a long time for Dr T to retire.

    But hey, pretty sure the rumor was not the full story, so many VPs were competing for that.

  2. If I remember well, windows 10 iot was the default option with the industrial computer from Advantech, at least that's what the reseller told me.

    We ordered one to try (with a return option if it didn't work), we tested for a few days, we were happy.

    We were only interested in in having something that worked like windows 10, came pre-installed and didn't have all the media/game nonsense that comes on "normal" computers.

  3. Well "good option" is a bit broad... it was great for my application

    There production line was producing 60 part par minute

    There were 3 C-Link camera, therefore 2 PCIe-1430 frmaegrabbers

    Each cam was acquiring 10 images of each part

    The time available for image acquisition + processing was ~800ms so the acquisition was done in parallel to the processing for each camera.

    At the time (3 years ago almost) we were getting the most powerfull IPC-720 available with 32Gb of RAM and Windows 10 IOT.

     

    The application did not require fanless or RT and it was working 24/7.

     

    We also had similar application with GigE cameras but I never liked GigE.

  4. Indeed the IC line of product was supposed to stand between the cRIO and PXI in term of perf - without offering the modularity that cRIO and PXI offer of course, but for Vision application it was ok with usb3 and GigE.

    But even then, the perf was disappointing for heavy vision application. I use to use Advantech IPC range, updated every 6 month with new CPUs etc.

     

    Supporting 3rd party hardware with NI Linux RT would probably require a huge effort for NI, not sure they're ready for that.

    And where NI is disappointing me a bit more is by not telling us what their plan is for Hardware between cRIO and PXI, at least if they were to say they are only going to maintain cRIO and PXI in the future at least we'd stop hopping a find a different solution.

  5. I understand your concern, NI's commitment to industrial vision has always been a bit loose I think.

    RT vision controllers come and go a bit fast. And there was the fiasco of the EVS, whose long term replacement was the IC-31xx, but when was the last update of that line? Many years ago and there's no communication around the future of this product.

    My advice is to find a different hardware supplier for "vision industrial computer" and use Windows 10 iot, otherwise NI will soon tell you to use a PXI!

    At some point NI was considering allowing to install NI Linux RT on non NI hardware, but I seriously doubt they'll ever to that, it would be in huge contradiction with their business model.

  6. On 10/20/2021 at 10:03 PM, Mads said:

    I have to agree with the requirement (although having an OK and a Cancel would suffice unless you also want to apply prior to closing the window). Stick to the norms established by the OS, familiarity is key. If I regret entering the dialog and/changing something having OK/Cancel there will allow me to recognise what to do in a fraction of a second. If this particular designer though it obvious that closing the window would revert...eh, I mean save the...hmmm. Do I need to change back the changes I did, or is it enough to close the window, I wonder....🤔

    If any change was made while on the config panel, a "revert changes" button would show-up.

    I admit it might not be obvious for everyone - of course what is important is : habit / expectation of the actual targeted users.

  7. Similarly, a few years ago, I was requested to add 2 buttons, "apply" & "cancel" before leaving a config panel.

    I tried to argue that they were useless because authentication was required to access the config panel, and user who got there knew what they're doing when changing a value ; if they change and close, why would the app not keep and apply the changed settings?

    It turned out users felt safer or rather "more in control" with explicit apply/cancel buttons. Meh.

  8. [cross-post]

    I'm starting to use LabVIEW 2020 Sp1 on OpenSuse 15 and the event structure editor - I mean the dialog to add / edit handled event - seems to have localization issues.

    Also, a difference from Windows LV, if a constant is connected to the timeout terminal, LV requires that you handle the timeout event... weird.

    Is it normal / known to have these "issues"?

  9. I've been there a few times.

    The treasure hunt is not really fun.

    2 suggestions :

    - if MAX is installed, you can see from there the NI drivers - and versions - installed, that's a good starting point. Careful though, if it's installed doesn't mean it's required for the application to run.

    - if MAX is not installed, I would go to the uninstall utility of Windows and select National Instruments Software, this will launch the uninstall utility of NI, it displays everything installed

     

    Also, you say the customer doesn't want to share the source, but if they have it, maybe you can tell them how to get the information you need.

×
×
  • Create New...

Important Information

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