branch_copy(checkout=True) liefert ungültigen Projekt-Handle (0) in CODESYS V3.5 SP22 Patch 3 ^{CODESYS Forge talk (Thread)}
branch_copy(checkout=True) liefert ungültigen Projekt-Handle (0) in CODESYS V3.5 SP22 Patch 3
Last updated: 4 days ago

Post by gseidel on Test ^{CODESYS Forge talk (Post)}
Test topic
Last updated: 4 days ago

Post by boiwithproblems on branch_copy(checkout=True) liefert ungültigen Projekt-Handle (0) in CODESYS V3.5 SP22 Patch 3 ^{CODESYS Forge talk (Post)}
Since upgrading from V3.5 SP21 P3 to SP22 P3, this previously working scripted call fails: project, current_branch = project.git.branch_copy(current_branch,new_branch_name,checkout=True) Error: _3S.CoDeSys.Core.Objects.InvalidProjectHandleException Standard Error: The project handle 0 is invalid Workaround: When you do branch copy with checkout=False and then checkout the branch in a seperate line everything works. The issue seems to be that Codesys doesn't give back a proper handle when you do branch_copy with checkout=True. This is mainly so that issue gets noted and resolved in a further Patch and that people with the same issue might have an easier time debugging their scripts. With kind regards Matthias Rudigier
Last updated: 4 days ago

Post by jebu on OPC UA method calls ^{CODESYS Forge talk (Post)}
I'm setting up an OPC UA server in CODESYS. My understanding so far: Calling methods over OPC UA requires an Information Model — the plain Symbol Set / Symbol Configuration alone doesn't support method calls. Is that correct, or is there a way around it? With an Information Model, the Node IDs are auto-generated and I can't set them manually. Assuming that's right: -Are these generated Node IDs stable across builds/downloads, or can they change? -If they can change, what triggers it — renaming a variable/method, reordering objects in the model, a rebuild, a re-download to the PLC?
Last updated: 3 days ago

Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5 ^{CODESYS Forge talk (Thread)}
Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5
Last updated: 1 day ago

Post by mankh on Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5 ^{CODESYS Forge talk (Post)}
Hi, I am migrating an existing IFM system from CR0020 + CODESYS 2.3 to CR710S + CODESYS 3.5. The existing CANopen I/O modules are: CR9011 CR2042 CR2011 My questions are: Can these legacy IFM CANopen modules be used as slaves with the CR710S CANopen Master? Can their existing EDS files be imported directly into CODESYS 3.5? Are there any known compatibility issues with the old IFM EDS files, PDO mapping, or startup SDO configuration? Has anyone successfully used these modules with a CR710S? If so, could you share the recommended configuration procedure? The goal is to replace the CR0020 with a CR710S while keeping the existing CANopen I/O modules
Last updated: 1 day ago

Sort by relevance or date