Jump to content

BramJ

Members
  • Posts

    40
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by BramJ

  1. 7 hours ago, jacobson said:

    One minor improvement (my opinion) is that, in NXG, the scroll wheel will move the diagram up and down but if you shift+scroll, the diagram will move right to left (CG just scrolls up/down faster).

    Would be nice if NXG, like CG, would support the horizontal scroll options available on many mice these days. In NXG that is somehow bound to zoom if the Zoom Control option is set to  "Ctrl + Mouse Wheel"

    if Zoom control is set to "Mouse Wheel" the scroll left/right is bound to scrolling up and down, makes no sense.

  2. Thank you for testing,

    On our systems it usually happens well before the 500 deletions using this VI, when doing it manually in the project explorer it usually within 10 attempts

    The application this is used in is a sequencer application that fills a virtual folder with VI's that are used in the sequence to add them to the build specification. After the build we need to clean the project so we need the folder empty. First we removed all the members of the folder one-by-one but we ran into problems when a VI used in the sequence was also used in the sequencer application itself, it could not be deleted then. Deleting the entire folder and recreating it did work but we sometimes we had labview crash as soon as we try to build.

    we can reproduce the crash by simply creating a new project, create a (empty) virtual folder and delete it. For some reason the crash is a lot more frequent when doing it manually as opposed to the programmatically creating and deleting 

     

    I have added a crash log for those interested, there are quite a bit of DWarn's in there:

    DWarn 0x0E697B77: Caught exception in ExtCode call!
    e:\builds\penguin\labview\branches\2017\dev\source\execsupp\ExtFuncRunTime.cpp(92) : DWarn 0x0E697B77: Caught exception in ExtCode call!

    DWarn 0x50CBD7C1: Got corruption with error 1097 calling library mxLvProvider.mxx function mxLvApi_SetIconOverlaysBatch
    e:\builds\penguin\labview\branches\2017\dev\source\execsupp\ExtFuncRunTime.cpp(275) : DWarn 0x50CBD7C1: Got corruption with error 1097 calling library mxLvProvider.mxx function mxLvApi_SetIconOverlaysBatch

    DWarn 0x50CBD7C1: Got corruption with error 1097 calling library mxLvProvider.mxx function mxLvApi_ServerSite_UpdateItemUIBatch
    e:\builds\penguin\labview\branches\2017\dev\source\execsupp\ExtFuncRunTime.cpp(275) : DWarn 0x50CBD7C1: Got corruption with error 1097 calling library mxLvProvider.mxx function mxLvApi_ServerSite_UpdateItemUIBatch

    lvlog.txt

  3. The following VI creates virtual folders and then deletes them from the project. Running this VI results in LabVIEW crashing on multiple systems in our company. The systems are running LabVIEW 2017, 2017 SP1 or 2018 (32 and 64bit) on Windows 7 and Windows 10. We also have some systems that don't crash.

     

    Would be nice if some people here can try it, it would give us some additional data to send to NI.

     

    The VI is saved in LV2017, I could save it for a previous version if needed. 

    LabVIEW Crasher Virtual Folders.vi

    Virtual Folder Test.lvproj

  4. Just compared the MD5 checksums of the 32 and 64bit 2018 SP1 I downloaded yesterday, they don't match what is listed on the download page now (with the new release date)

    Also, the buildInfo.txt content of both the 32 and 64bit is exactly the same as the version I downloaded last month

     

    (I must say, I have been running the 2018 SP1 the last weeks, have not run into any problems)

  5. If I remember correctly there are freewheeling diodes inside the ULN2803

    a while ago I used a USB6501 with some 7400-series logic chips and ULN2803's to control relais, worked great

    this way I could control 16 relais with 4 outputs on teh USB6501

×
×
  • Create New...

Important Information

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