Jump to content

jcstoke

Members
  • Posts

    3
  • Joined

  • Last visited

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since
    1993

Contact Methods

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jcstoke's Achievements

Newbie

Newbie (1/14)

  • One Year In Rare
  • One Month Later
  • First Post Rare
  • Week One Done
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. I am trying to call a python script function from labview and get the following error, Module Path: C:\STOKE\code\GSW.Deployment.0.1-rc0\yardmaster\yardmaster.py LabVIEW: (Hex 0x683) The specified Python module could not be imported. ========================= LabVIEW: (Hex 0x683) The specified Python module could not be imported. Module Path: C:\STOKE\code\GSW.Deployment.0.1-rc0\yardmaster\yardmaster.py Function Name: exit Python returned the following error: <class 'ImportError'> DLL load failed while importing _ssl: The specified module could not be found. <traceback object at 0x037E3FA8> If I run the python script in a Anaconda Prompt command shell it works as expected. I'm wondering if the Anaconda enviroment has all of the dependancies needed, but not so in the LV session. I've tried passing the parameter "function name" as one of the commands listed below with the module parameter as "yardmaster.py" whcih returns an error in LV but works in the cmd shell (as shown below). Any ideas and/or help is greatly appreciated. SERVO Test Python Node.vi
  2. I really appreciate your (JK, SR, MA, et.al.) responses and expert advice . I am enjoying being back in an engineering/coder role -specifically looking at ZMQ, Python/LV, GIT, etc. In another thread and when time permits, I hope to write about my introduction to LV (way back in the 90's) and some of the jobs/contracts/projects I have been involved with. It has been an interesting journey to say the least. Again, thanks to all of you for your help.
  3. I need advice on SCADA/DAQ options for my company. We are a small (aerospace) startup with app 30 engineers at present and plans to hire many more in 2022+. My background, I am an EE with Math/CS graduate school education, 30 years of industry experience working for various companies both as an FTE and as a consultant/contractor (NI Alliance partner). I have been in a management role for the last several years which I thought would lead to early retirement. As it turns out I'm not well suited to being put out to pasture -not just yet anyway. I had no intention of ever being an FTE again, but never say never is probably a good mantra. I am enjoying the energy, excitement and opportunity to help define and implement our data acquisition and control systems. To that end, I am seeking advice and opinions on using NI SW and HW, specifically LabVIEW licensing e.g. packages (full, professional), subscription vs perpetual, PXI vs cRIO vs cDAQ. In the past as an Alliance Partner I had access to most/all of NI's software. We used LabVIEW/RT/FPGA & TestStand extensively in designing and building rack based functional/end of line testers, embedded controllers and laboratory SCADA systems. In the past few years NI has changed considerably. While I don't necessarily agree with all of the changes -I do understand the motivation. Case in point I never used NGX for a commercial project, we stuck with traditional LV (all the way from 3.x to 2019). My experience with NXG is limited but the little I saw I really liked. I'm saddened to see it die. I've always been a little leery of having a single source solution e.g. LabVIEW but the advantages seemed to out weight my concerns. I've read many posts (on LAVA, NI, Reedit, etc.) with interest regarding NIs (and LVs) future. I agree with most of them. But back to my question, Currently we are using, An inhouse developed SCADA application written in LV 2020 various (cDAQ) chassis and modules (from NI and UEI) LabVIEW is installed and running on a server connected to the HW item 2 above via a fiber based high speed dedicated link appx 200m away writing data to flat files with 3rd party data analysis/visualization packages My current thoughts are to ( I have an aggressive schedule) refactor/cleanup existing LV code (using LV2021) buy LabVIEW 2021 license subscription(s) use the VLA/VLM (start with 5 seats and add more as needed) use PXI as the primary HW (as opposed to cRIO/cDAQ) use external controller (PC) as opposed to an embedded one (contained in the PXI chassis) build the next DAQ system using a 19" EIA rack with PXI chassis and local controller (PC), use cRIO where needed build WEB based HMI for remote monitoring and control use TDMS and/or SQL database BTW, there is a clear negative perception of NI/LV here. Most of the engineers are young (30ish) and pretty convinced Python is the sh*t. I'm not opposed to using text based languages (where appropriate). I still think LV has some advantages, e.g. development time, in this environment/use case. Given my recent experiences (e.g. horrible support, not returning calls/emails, access problems) and perhaps most damning of all, I've lost faith/don't trust them. If I didn't have a 30 year relationship with them, I'd tell them to f-off and vote with my feet.
×
×
  • Create New...

Important Information

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