Personal Data

Username:
spiessli
Joined:
2023-12-19 10:56:14.653000

Projects

  • No projects to display.

User Activity

  • Posted a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    If I remember well, first you need to delete the current version. Then clicking through the tree as indicated in the previous post, lets you choose the "outdated" libraries.

  • Posted a comment on discussion Motion 🇬🇧 on CODESYS Forge

    Just verified the behaviour. Still is the same. It should be attached here. But I also tried the DCF-file with the axis in the lab with the real drive: The MC_Power block never goes out of busy. Had not time to investigate further, though.

  • Posted a comment on discussion Motion 🇬🇧 on CODESYS Forge

    Thanks for the advise, indeed, this was somewhat, what my intention was. I tried around again with EDSes and DCFs, anyway. It appears that the DCFs end up in a subfolder in the attach device dialog. Astonishingly, when attaching the DCF version I get a device in the device tree, where I can add a SoftMotion axis, whereas when I attach the device not in the subfolder, then I cannot. Further astonishingly, when looking in the CANopen parameters in supported profiles, "402" is listed in the case of...

  • Posted a comment on discussion Motion 🇬🇧 on CODESYS Forge

    Hi, I want to use Maxon IDX drives for some simple robotic applications. I have used Maxon's Epos for generating a DCF file to import in Codesys (attached). Then I can add the IDX motors under a CANopen manager in the device tree. Unfortunately, I cannot add a "softmotion axis" to the IDX motors. Now I am wondering, why? Without being able to attach a softmotion axis to the device in the device tree, the use of the motor is greatly reduced... spiessli

  • Posted a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    Thanks for the suggestion, I have tried it eagerly: I have updated all packages to latest version with Codesys Installer and installed newest runtime and gateway on Raspberry Pi. Unfortunately, the error is still there. As soon as I add the SM_Drive_Servo to the device tree, I get the error below when generating the code. Reverting SM3_Basic to version 4.14 makes the error disappear. ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... Code erzeugen... [FEHLER]...

  • Posted a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    In fact, specifying to use SM3_Basic library in version 4.14 fixes the issues, choosing 4.16 raises the same issues. (Library Manager > Place Holder > Double click on SM3_Basic > Show all versions)

  • Posted a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    Hi, I wanted to use the Adafruit Hat for the Raspberry and get acquainted with Softmotion using servos for RC models. This did work great with Codesys 3.5.19 Patch 1, but with Patch 4 and 5 i get errors. I suspect changes in the SoftMotion library have broken dependencies in the legacy drivers, might that be true? Thanks for any hint, spiessli Here the error log: ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... Code erzeugen... [FEHLER] sm3_drive_servo,...

View All