Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched. Close

Error when monitoring LAD programs

umdee
2024-03-17
2024-03-19
  • umdee - 2024-03-17

    I get the following error when monitoring my program (see attached screenshots):

    "Unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

    Value cannot be null.
    Parameter name: source.

    And the details say:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ** Exception Text **
    System.ArgumentNullException: Value cannot be null.
    Parameter name: source
    at System.Linq.Enumerable.Any[TSource] (IEnumerable1 source, Func2 predicate)
    at _3S.CoDeSys.NWLEditor.NWLTextCell.OnPaintCellLayer(PaintEventArgs e)
    at _3S.CoDeSys.Controls.Controls.GfxEdControl.PaintCellCellLayer(PaintEventArgs e, GfxCell cell)
    at _3S.CoDeSys.Controls.Controls.GfxEdControl.PaintCellCellLayer(PaintEventArgs e, GfxCell cell)
    at _3S.CoDeSys.Controls.Controls.GfxEdControl.PaintCellCellLayer(PaintEventArgs e, GfxCell cell)
    at _3S.CoDeSys.Controls.Controls.GfxEdControl.OnPaint(PaintEventArgs e)
    at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
    at System.Windows.Forms.Control.WmPaint(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.UserControl.WndProc(Message& m)
    at _3S.CoDeSys.Controls.Controls.GfxEdControl.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ** Loaded Assemblies **
    (3000 lines of assemblies)

    ** JIT Debugging **
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitdebugging="true">
    </system.windows.forms></configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box

    The windows show red X's where the networks should be. Any advice on how to fix this?

    Additional Information
    PLC used: Wago 750-8212, Firmware FW26
    Startup profile: CODESYS V3.5 SP19 Patch 5
    OS version: Microsoft Windows NT 10.0.22631.0
    .NET version: 4.0.30319.42000

    Full Version info attached as .txt

     
    πŸ‘
    1
  • umdee - 2024-03-19

    System Information from the computer being used:

    OS Name Microsoft Windows 11 Pro
    Version 10.0.22631 Build 22631
    Other OS Description Not Available
    OS Manufacturer Microsoft Corporation
    System Manufacturer Dell Inc.
    System Model Latitude 5500
    System Type x64-based PC
    System SKU 08B9
    Processor Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz, 2112 Mhz, 4 Core(s), 8 Logical Processor(s)
    BIOS Version/Date Dell Inc. 1.3.11, 6/11/2019
    SMBIOS Version 3.2
    Embedded Controller Version 255.255
    BIOS Mode UEFI
    BaseBoard Manufacturer Dell Inc.
    BaseBoard Product 0M14W7
    BaseBoard Version A00
    Platform Role Mobile
    Secure Boot State On
    PCR7 Configuration Elevation Required to View
    Windows Directory C:\WINDOWS
    System Directory C:\WINDOWS\system32
    Boot Device \Device\HarddiskVolume1
    Locale United States
    Hardware Abstraction Layer Version = "10.0.22621.2506"
    User Name CARDASSIA-IX\Engineer
    Time Zone Eastern Daylight Time
    Installed Physical Memory (RAM) 16.0 GB
    Total Physical Memory 15.8 GB
    Available Physical Memory 4.67 GB
    Total Virtual Memory 18.5 GB
    Available Virtual Memory 2.52 GB
    Page File Space 2.63 GB
    Page File C:\pagefile.sys
    Kernel DMA Protection Off
    Virtualization-based security Not enabled
    Windows Defender Application Control policy Enforced
    Windows Defender Application Control user mode policy Off
    Device Encryption Support Elevation Required to View
    Hyper-V - VM Monitor Mode Extensions Yes
    Hyper-V - Second Level Address Translation Extensions Yes
    Hyper-V - Virtualization Enabled in Firmware Yes
    Hyper-V - Data Execution Protection Yes

     

Log in to post a comment.