Jump to content

Sam Taggart

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Sam Taggart

  1. I can only seem to find version 20.0 via NIPM. Is there a special feed or something for 20.1?
  2. I was trying to understand the logic behind this and now that I take a step back, I see. You were trying to prevent people from putting in 2012 instead of 12.0. Makes perfect sense now.
  3. Simply removed the case structure and it seemed to work fine.
  4. I was trying to apply a vipc using the API and it tells me 20.0 isn't a valid LabVIEW version. Digging into I found this: see attached image. Maybe you guys were a little too optimistic about the switch to NXG and figured wed never see 20.0?
  5. Somehow I saw your posted about the error log and somehow skipped over the one about rebooting. That may have worked, but now we will never know (unless someone else ends up with the same problem).
  6. uninstalling and reinstalling via NIPM appeared to work (didn't even reboot in between).
  7. Number 2 would be very useful. Number 1 I haven't run into (yet).
  8. Here is the whole error if that helps: =========== START of VIPM 2020.0.0 (build 2302) Error Message =========== An internal VIPM 2020.0.0 (build 2302) Error has occured on: Friday May 22, 2020 at 10:37:10 PM = Automated Message Start = Error 42 occurred at (http response "404". URL Requested: http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/austin_consultants_lib_finance_ohlc_plot/aus tin_consultants_lib_finance_ohlc_plot- 85294761631CBC58471969C9E99FB95F:2980001 in 34ECF0FD9B9E81860D3E52C65FD0A442->15A1868D1CB3D6176D9B44B0ED323314->C898E814D7E4
  9. I am getting a 404 on "http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/austin_consultants_lib_finance_ohlc_plot/au stin_consultants_lib_finance_ohlc_plot-". any thoughts as to why?
  10. So VIPM 2020 was working fine for me, but now it is not. When I launch it, the icon appears in the task bar and then it disappears and nothing happens. Any recommendations on troubleshooting steps? perhaps some logs somewhere? I'm on the latest update of Windows 10 if that helps. thanks, Sam
  11. I would mark this as an improvement since in the past it could sometimes take a while for VIPM to refresh everything. I am quite happy with the design palette at the moment, but if I think of anything I will let you know.
  12. That did the trick. Curious - I thought that ran everytime you opened VIPM. Is that true? Does it only automatically do it on some schedule? I swear I had restarted VIPM.
  13. By the may thanks for an awesome toolkit and the quick response!
  14. It seems that link is still pointing to the old package even though the new one shows up in the list. See attached.
  15. Curious if there is any plan to ad LV2020 support?
  16. was this ever resolved, because I am currently having the same problem.
  17. I have a library with some VIMs and regular VIs. On the Display information Screen in the package builder I have Edit All VI Descriptions checked. My regular VIs get the copyright notice added, no problem. The VIMs don't. I am using VIPM PRO 2019.0.0.0. Checked for an update. It says I have the latest. Source Code is in LV19.0f2 if that helps. I suspect the vim file extension may be causing the issue. I attached a simple reproduction. thanks for creating such a great product! Sam VIM Descr Issue.zip
  18. Jim, Here is a simple example. Note it appears that also text files (and perhaps any non-LV files) are affected. The .vipb file is from 2017. Sam Simple Example.zip
  19. I am recieving the same Build failed during "source distribution step" dialog box Here is what the error log file says: =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: Thursday February 04, 2010 at 01:02:53 PM = Automated Message Start = Error 1031 occurred at Open VI Reference in Filter Illegal File Names__ogb.vi->Generate Resources Copy Info__ogb.vi->Build Application__ogb.vi->Build Application from Build File__ogb.vi->Build Application from Build File__ogb.vi.ProxyCaller Possible reason(s): LabVIEW: VI Reference ty
  • Create New...

Important Information

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