No source code available (cip object)

yotaro
2023-02-06
2024-07-16
  • yotaro - 2023-02-06

    I'm trying to connect CODESYS Scaner and CODESYS Adapter by EhterNet/IP, but getting an error "No source code availible for this object becouse it is in the compiled library "cip object, 4.4.0.0 (3s- ...). Do you want to browse...".
    Target systems are Xilinx KR260.

    My system data:
    Startup profile: CODESYS V3.5 SP18 Patch 4
    OS version: Microsoft Windows 10

    Target system data:
    Runtime version: 4.7.0.0-b.trunk.39 (linux64, arm64)
    OS version: Ubuntu 22.04.1 LTS

     
    • yotaro - 2023-02-06

      This issue has been resolved.
      It was my setting mistake.

       
  • fabiencavalier - 2023-03-14

    Hello,
    How did you solve this issue please ?
    I have the same one at the moment.
    Thanks

     
  • fabiencavalier - 2023-03-14

    Hello,
    How did you solve this issue please ?
    I have the same one at the moment.
    Thanks

     
    • yotaro - 2023-03-16

      Hi fabiencavalier,
      Sorry, I cannnot remember that detail.
      But, it seems that the IP Module could not be added.
      Are your Slave settings like the attached image?

      Regards,

       
  • youness - 2024-07-16

    Hi yotaro,
    hope your problem was resolved. I had the same, but with an other library title.
    This exception is not detected during compilation, but rather at a given position in the program (when switching to a given visualization). Although the exception is generated at this point, it does not involve the visualization in question. This error is due to one of 3 reasons:
    1) A division by zero somewhere: The program is able to detect divisions by zero at compile time. But in the case of a variable, which takes a valid value at init and changes to 0 at a later stage.
    2) An invalid pointer: (either because it has a value of 0, or because it points outside the memory reserved for the program) is being dereferenced. Locate any pointers or interfaces you have in the code and check them - you should also be wary of mixing inline modifications and pointers.
    3) Array overflow: Generally when a processing operation is executed outside the array's definition range. Example: a write loop with n iterations is executed on an array of dimmension n-1. On the other hand, the error message may not appear. In the latter case, the error may have fatal consequences, as the overflow has induced writing to potentially forbidden memory areas.

    This problem can be explained by the fact that it's not always the adjacent memory areas of PLC_PRG that are overwritten, but the memory areas that are randomly allocated to the array during compilation. In this case, however, there is no entry in the log, so you need to integrate the "Implicit Check function", which checks the line of code generating the error.

    To integrate this functions, click on Application --> POU for implicit controls

    Regards,

     

    Last edit: youness 2024-07-16

Log in to post a comment.