Search talk: -128到127是什么数据类型

 
<< < 1 .. 916 917 918 919 920 .. 922 > >> (Page 918 of 922)

Post by dakmueller on Zielsystem Problem nach Bibliotheken hinzufügen CODESYS Forge talk (Post)
Hallo, ich habe ein altes Projekt geöffnet um auf einer Anlage eine Änderung einzufügen. Beim öffnen haben etliche Bibliotheken gefehlt. Diese habe ich dann installiert und übersetzt. Online kam ich nicht, weil kein Zielsystem angegeben war. Beim Übersetzten gab es keine Meldungen. Als ich das Zielsystem XV-1xx-V2.3.9 SP3 ausgewählt habe und das übersetzt kamen viele Fehlermeldungen. Viele Variablen nicht deklariert. Die Steuerung/HMI ist eine EATON XV-102-E8-57TVRC-10. Hilfe
Last updated: 2026-06-22

Zielsystem Problem nach Bibliotheken hinzufügen CODESYS Forge talk (Thread)
Zielsystem Problem nach Bibliotheken hinzufügen
Last updated: 2026-06-22

Post by dakmueller on Zielsystem Problem nach Bibliotheken hinzufügen CODESYS Forge talk (Post)
Hallo, ich habe ein altes Projekt geöffnet um auf einer Anlage eine Änderung einzufügen. Beim öffnen haben etliche Bibliotheken gefehlt. Diese habe ich dann installiert und übersetzt. Online kam ich nicht, weil kein Zielsystem angegeben war. Beim Übersetzten gab es keine Meldungen. Als ich das Zielsystem XV-1xx-V2.3.9 SP3 ausgewählt habe und das übersetzt kamen viele Fehlermeldungen. Viele Variablen nicht deklariert. Die Steuerung/HMI ist eine EATON XV-102-E8-57TVRC-10. Hilfe
Last updated: 2026-06-22

Post by dakmueller on Zielsystem Problem nach Bibliotheken hinzufügen CODESYS Forge talk (Post)
Hallo, ich habe ein altes Projekt geöffnet um auf einer Anlage eine Änderung einzufügen. Beim öffnen haben etliche Bibliotheken gefehlt. Diese habe ich dann installiert und übersetzt. Online kam ich nicht, weil kein Zielsystem angegeben war. Beim Übersetzten gab es keine Meldungen. Als ich das Zielsystem XV-1xx-V2.3.9 SP3 ausgewählt habe und das übersetzt kamen viele Fehlermeldungen. Viele Variablen nicht deklariert. Die Steuerung/HMI ist eine EATON XV-102-E8-57TVRC-10. Hilfe
Last updated: 2026-06-22

Post by alexschooneveld on OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext CODESYS Forge talk (Post)
I am currently investigating an OPC UA PubSub connection over UDP. When I don't use encryption, the publish and subscribe are working correctly. But with encryption it does not. Environment OPC UA PubSub SL 1.3.0.0 (namespace UADP) OPC UA PubSub Security 1.3.0.0 (namespace PSS) OPC UA PubSub Base 1.3.0.0 (namespace PSB, incl. PSS.SecurityGroup / PSS.CONFIG) Programmatic PubSub in a CFC: UADP.Configuration → UADP.Connection → UADP.writerGroup → UADP.writer → writerDataSet, plus a CyclicCall gated by xEnable. Goal: publish secured UADP, SignAndEncrypt, policy PubSub-Aes256-CTR. What I do (one-shot, before xEnable := TRUE): fbSecurityGroup.SetInitialValue( 'http://opcfoundation.org/UA/SecurityPolicy#PubSub-Aes256-CTR', PSB.SECURITY.SIGNING_AND_ENCRYPTION); stSecurityCfg := fbSecurityGroup.GetConfig(eErrorID => eError); // eError=NO_ERROR, udiEncryptionKeySize=32 eError := fbSecurityGroup.SetSecurityKeys(udiTokenId, ADR(abyKey), SIZEOF(abyKey), 2436001000); // eError=NO_ERROR, SIZEOF=68 // writerGroup.itfSecurityGroup := fbSecurityGroup -- set in the WriterGroup block's Parameters (a per-scan code write got overwritten) What I verified eError = NO_ERROR after both GetConfig and SetSecurityKeys; udiEncryptionKeySize = 32. Key length = 68 bytes (signing 32 ‖ encrypt 32 ‖ nonce 4). itfSecurityGroup is set via the WriterGroup's Parameters (so it isn't clobbered each scan). Init runs before xEnable (the writer doesn't run with xEnable=FALSE). The UADP.writerGroup FB exposes only itfSecurityGroup for security — no SecurityMode/MessageSecurityMode property. Result: the published datagrams are still plaintext — ExtendedFlags1 = 0x01 (security bit 0x10 clear), no security header: b1 01 29 00 0f 16 00 … (PublisherId 41, WriterGroupId 22, RawData, no security) Questions With UADP.writerGroup, is assigning a configured + keyed PSS.SecurityGroup to itfSecurityGroup sufficient to enable message security, or is there an additional step/property/method to switch the WriterGroup to SignAndEncrypt? At what point in the WriterGroup lifecycle is itfSecurityGroup read? Must it be assigned/keyed before xActive, and does the group need a stop→start to pick it up? Is there a required call order, and does SetSecurityKeys need to be called once or repeatedly? Should security be configured on the Connection/Configuration level rather than (or in addition to) the WriterGroup? Is there a working example of secured (SignAndEncrypt) programmatic UADP publishing with this library, or a known limitation in 1.3? How can I read back at runtime whether security is actually active (via itfDiagnostics or similar)? Additional information I can confirm that the consumer side works — i.e. a standard subscriber decrypts the same keys fine — so the keys/profile aren't the issue. The Wireshark capture of the published message is: 0000 b1 01 29 00 0f 16 00 df 0d bb 25 01 00 0e 00 1b ..).......%..... 0010 0e 00 00 00 00 00 00 00 ........
Last updated: 2026-06-22

Post by alexschooneveld on OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext CODESYS Forge talk (Post)
I am currently investigating an OPC UA PubSub connection over UDP. When I don't use encryption, the publish and subscribe are working correctly. But with encryption it does not. Environment OPC UA PubSub SL 1.3.0.0 (namespace UADP) OPC UA PubSub Security 1.3.0.0 (namespace PSS) OPC UA PubSub Base 1.3.0.0 (namespace PSB, incl. PSS.SecurityGroup / PSS.CONFIG) Programmatic PubSub in a CFC: UADP.Configuration → UADP.Connection → UADP.writerGroup → UADP.writer → writerDataSet, plus a CyclicCall gated by xEnable. Goal: publish secured UADP, SignAndEncrypt, policy PubSub-Aes256-CTR. What I do (one-shot, before xEnable := TRUE): fbSecurityGroup.SetInitialValue( 'http://opcfoundation.org/UA/SecurityPolicy#PubSub-Aes256-CTR', PSB.SECURITY.SIGNING_AND_ENCRYPTION); stSecurityCfg := fbSecurityGroup.GetConfig(eErrorID => eError); // eError=NO_ERROR, udiEncryptionKeySize=32 eError := fbSecurityGroup.SetSecurityKeys(udiTokenId, ADR(abyKey), SIZEOF(abyKey), 2436001000); // eError=NO_ERROR, SIZEOF=68 // writerGroup.itfSecurityGroup := fbSecurityGroup -- set in the WriterGroup block's Parameters (a per-scan code write got overwritten) What I verified eError = NO_ERROR after both GetConfig and SetSecurityKeys; udiEncryptionKeySize = 32. Key length = 68 bytes (signing 32 ‖ encrypt 32 ‖ nonce 4). itfSecurityGroup is set via the WriterGroup's Parameters (so it isn't clobbered each scan). Init runs before xEnable (the writer doesn't run with xEnable=FALSE). The UADP.writerGroup FB exposes only itfSecurityGroup for security — no SecurityMode/MessageSecurityMode property. Result: the published datagrams are still plaintext — ExtendedFlags1 = 0x01 (security bit 0x10 clear), no security header: b1 01 29 00 0f 16 00 … (PublisherId 41, WriterGroupId 22, RawData, no security) Questions With UADP.writerGroup, is assigning a configured + keyed PSS.SecurityGroup to itfSecurityGroup sufficient to enable message security, or is there an additional step/property/method to switch the WriterGroup to SignAndEncrypt? At what point in the WriterGroup lifecycle is itfSecurityGroup read? Must it be assigned/keyed before xActive, and does the group need a stop→start to pick it up? Is there a required call order, and does SetSecurityKeys need to be called once or repeatedly? Should security be configured on the Connection/Configuration level rather than (or in addition to) the WriterGroup? Is there a working example of secured (SignAndEncrypt) programmatic UADP publishing with this library, or a known limitation in 1.3? How can I read back at runtime whether security is actually active (via itfDiagnostics or similar)? Additional information I can confirm that the consumer side works — i.e. a standard subscriber decrypts the same keys fine — so the keys/profile aren't the issue. The Wireshark capture of the published message is: 0000 b1 01 29 00 0f 16 00 df 0d bb 25 01 00 0e 00 1b ..).......%..... 0010 0e 00 00 00 00 00 00 00 ........
Last updated: 2026-06-22

Post by fabiodasilveira on Dynamic Setting IP Address from IEC code CODESYS Forge talk (Post)
It is a shame that it does not work with Eaton XC303 PLCs :(
Last updated: 2026-06-23

Why Is Academic Writing So Stressful for Many Students? CODESYS Forge talk (Thread)
Why Is Academic Writing So Stressful for Many Students?
Last updated: 2026-06-23

Version management CODESYS Forge talk (Thread)
Version management
Last updated: 2026-06-24

Post by gseidel on CODESYS SoftMotion Generic DSP402 on WAGO PFC200 + Festo CMMT-AS: MC_Power stays Busy, Controlword remains 0 CODESYS Forge talk (Post)
Hi gilad, the missing license does not prevent the axis from being enabled. As far as I know, Festo distributes a CODESYS SoftMotion driver for the CMMT drives together with their software. I would contact Festo and ask for the driver. Best regards, Georg
Last updated: 2026-06-25

Post by rmarco on Generic Variables and FDB CODESYS Forge talk (Post)
Hello everyone, I am running into a highly frustrating issue in the FBD editor regarding a Function Block with generic constants (VAR_GENERIC CONSTANT). I created a FB using ST, with a generic var, useful for having a variable sized array, as follows: FUNCTION_BLOCK Coil VAR_GENERIC CONSTANT maxEvents: USINT := 5; END_VAR VAR events: ARRAY[0..maxEvents-1] OF IEvent; END_VAR These FBs have also several methods. I declare them as follows in code: VAR coil1: CDL.Coil<(maxEvents:=1)>; END_VAR and when using them in ST, I have no problems. However, when trying to use them in FDB, I do not know how to do that, as some strange misalignment happens. Here's what happens: When I add the block to my FBD canvas and assign coil1 as the instance name, the compiler throws this error: 'coil1' is not an instance of 'CDL.Coil<(maxEvents:=1)>'. Same occurs when I try to instantiate blocks such as 'coil1.turnOn' or similar. Here is what I have already tried, none of which worked: - Deleting the <(maxEvents:=1)> parameter from the text inside the FBD box. - Deleting the block entirely, dropping an "Empty Box", and typing coil1 above it to let the IDE auto-complete and format the block. - Running a full "Clean All" and rebuilding the code. I am aware that I could bypass the graphical editor by calling it in Structured Text. However, I need to keep this logic compatible to FBD. Has anyone encountered this specific FBD parsing bug with generic variables? Thanks in advance for any insights. Best regards, Marco
Last updated: 2026-06-29

Post by eschwellinger on Linux ARM64 Deploy Fail - Index out of range CODESYS Forge talk (Post)
Which Deploy Tool version is installed? the ssh login does work? If yes could we get a screenshot of the device information see my example:
Last updated: 2026-07-01

Post by arj3090 on Linux ARM64 Deploy Fail - Index out of range CODESYS Forge talk (Post)
This is the version shown in the CodeSys Installer.
Last updated: 2026-07-01

Linux ARM64 Deploy Fail - Index out of range CODESYS Forge talk (Thread)
Linux ARM64 Deploy Fail - Index out of range
Last updated: 2026-07-01

Post by eschwellinger on Linux ARM64 Deploy Fail - Index out of range CODESYS Forge talk (Post)
I would check the version of the deloy tool using the CODESYS installer. Sure manually installing works too, but woukd nice to know if there is a problem. Currebt version is 4.21.0.0 of the deploytool.
Last updated: 2026-07-01

Post by arj3090 on Linux ARM64 Deploy Fail - Index out of range CODESYS Forge talk (Post)
I used Tools->Deploy Control SL in the IDE that I downloaded yesterday. So I assume it is the latest version. I did a manual install using SSH and it works.
Last updated: 2026-07-01

Phantom Test Slot Preventing Suite Completion CODESYS Forge talk (Thread)
Phantom Test Slot Preventing Suite Completion
Last updated: 2026-07-09

Post by ophelia on Phantom Test Slot Preventing Suite Completion CODESYS Forge talk (Post)
Hi all, I'm working with a CODESYS 3.5 unit test framework on an embedded Linux PLC and running into an issue where a phantom test slot appears in the results that never completes, preventing the full test suite from ever finishing. The symptom: A blank-named test entry appears in the results table with an ever-increasing action count. It stays as "Testing" or "Failing" indefinitely. Because it never closes, bAllFinished never goes TRUE and the final report is never generated. Question: Has anyone seen this kind of phantom slot issue in a CODESYS unit testing setup? Thanks
Last updated: 2026-07-09

Post by yannickasselin on Beckhoff CX9240 : Using Internal EtherCAT Bus CODESYS Forge talk (Post)
Control RTE is for Windows. @arj3090 specified Linux.
Last updated: 2026-07-10

See if application is running CODESYS Forge talk (Thread)
See if application is running
Last updated: 2026-07-10

Post by ttvs on See if application is running CODESYS Forge talk (Post)
Hello, Is it possible to check if PLC application is running or stopped from linux shell? I am using codesys control for linux arm64sl. Tried accessing the plc shell, but get auth errors. Also, when starting/stopping the program via plc shell from codesys IDE it doesnt report that information to log
Last updated: 2026-07-10

Post by hhermsen on Codesys v3.5.22.10 - Internal error:System.AggregateException...Value cannot be null...Parameter name: expLValue CODESYS Forge talk (Post)
I pinpointed down 4 possible causes for this compiler error: Bare/empty statements (;) standing alone inside an IF/CASE branch — just removed two instances. The optimizer that tries to inline/replace expression statements may choke when a statement has no actual assignment to extract. A VAR_IN_OUT parameter used directly as a FOR loop's own control variable (FOR X := X TO Y DO) General deep-nesting complexity — every one of my decode routines has the same shape (IF busy THEN ... FOR loop containing nested CASE/IF chains ... END_IF), and the crash trace consistently shows for loop → sequence → ifst → sequence → ifst → sequence regardless of the code change. This raises the possibility that it's not one specific statement but a structural depth/complexity limit in SP22.x's compiler optimizer — which would mean no small code change fixes the issue. Only restructuring to reduce nesting depth, or downgrading the compiler will. Something entirely outside my library files — which cannot not ruled out since the exact stack trace was triggered by a Visualization object, in a totally different codebase. This means the same crash signature can come from unrelated causes. IMHO cause 3 seems the most probable one..
Last updated: 2026-07-11

Post by hhermsen on Codesys v3.5.22.10 - Internal error:System.AggregateException...Value cannot be null...Parameter name: expLValue CODESYS Forge talk (Post)
Internal compiler error in SP22.x (expLValue null) — SP21 unaffected — need help isolating root cause I'm hitting the same internal compiler crash reported here. Same exact stack trace (AssignmentStatementReplacer → CreateAssignmentExpression → ArgumentNullException: Value cannot be null. Parameter name: expLValue), but in my case triggered by a self-written library, not a Visualization object — so this looks like a general SP22.x codegen regression rather than something tied to one specific language feature. What I've confirmed: Reverting to SP21 — no issue, builds clean SP22.x — internal compiler crash during Build > Application, code generation phase, with zero useful location info (no POU, no line number) check_for_errors/precompile-only passes cleanly; the crash only happens on a real full build, meaning static analysis never sees it coming What I've tried to isolate the cause (without success): Removed a suspected pattern involving a VAR_IN_OUT parameter used directly as a FOR-loop control variable, combined with early RETURN inside the loop — crash persisted identically afterward Confirmed no Visualization Manager or similar object in the project (ruling out the trigger in the linked report) Used an AI coding assistant (Claude Code) to search for other suspicious patterns — no luck pinpointing the exact statement Question @codesys-com Since the compiler gives no location info at all, is there any way to get more diagnostic output from the SP22.x codegen phase (verbose/debug build flags, log level settings, etc.)? Without that, isolating this in a large library means blind bisection — cutting the codebase in half repeatedly until the crash disappears, which is slow and error-prone without official tooling support. Happy to share the affected project or a minimal repro if that helps CODESYS engineering track it down.
Last updated: 2026-07-11

Post by williamcorlin on The future and proper use of CAA.BOLT, CAA.SEMA,.. CODESYS Forge talk (Post)
I've been moving in the same direction. For new libraries, I'm trying to minimize dependencies on APIs that look like they're being phased out unless the documentation explicitly recommends them. For synchronization primitives like CAA.BOLT and CAA.SEMA, I'd love to see an official replacement or abstraction layer that's guaranteed to remain stable across runtimes. That would make library development much cleaner than relying on platform-specific SysLib* implementations or conditional compilation everywhere. Until there's clearer guidance, my approach has been to isolate the locking mechanism behind a small wrapper interface. If CODESYS changes the recommended API in the future, only that wrapper needs to be updated instead of every library that uses it. It isn't perfect, but it's made maintenance much easier. https://forge.codesys.com/forge/talk/Engineering/thread/e6c20a740e/ https://zapgames.io/
Last updated: 2026-07-14

The future and proper use of CAA.BOLT, CAA.SEMA,.. CODESYS Forge talk (Thread)
The future and proper use of CAA.BOLT, CAA.SEMA,..
Last updated: 2026-07-14

<< < 1 .. 916 917 918 919 920 .. 922 > >> (Page 918 of 922)

Showing results of 23037

Sort by relevance or date