Post by liai on an not create Symbol Configuration in Codesys V3.5 SP20 Patch 4 ^{CODESYS Forge talk (Post)}
Just can not create Symbol Configuration in Codesys V3.5 SP20 Patch 4.Showed in the picture. The same PLC works well in SP19. If it lack of some setting in SP20 ?Thanks a lot.
Last updated: 2025-03-08

Post by timvh on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Maybe the ANY type can help? https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_datatype_any.html
Last updated: 2025-03-08

Post by timvh on an not create Symbol Configuration in Codesys V3.5 SP20 Patch 4 ^{CODESYS Forge talk (Post)}
Go to the menu Tools - CODESYS Installer. Here you can manage your add-on packages. Go to Browse, find CODESYS Communication and install this add-on.
Last updated: 2025-03-08

Post by liai on an not create Symbol Configuration in Codesys V3.5 SP20 Patch 4 ^{CODESYS Forge talk (Post)}
Picture
Last updated: 2025-03-08

Post by timvh on Assignment Efficiency - Repetitive Assignment vs IF statement ^{CODESYS Forge talk (Post)}
You can consider using OR_ELSE: Coils[0] := Coils[0] OR_ELSE (Buttons[0] AND Sensors[0] > 6); https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_operator_or_else.html IF Coils[0] is TRUE, then the rest is not relevant anymore and doesn't have to be evaluated anymore. PS, there is also an AND_THEN https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_operator_and_then.html
Last updated: 2025-03-08

Version Control ^{CODESYS Forge talk (Thread)}
Version Control
Last updated: 2025-03-08

Post by timvh on Version Control ^{CODESYS Forge talk (Post)}
https://store.codesys.com/en/codesys.html#versions
Last updated: 2025-03-08

Post by pernockham on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Interesting, thanks! Didnt know about ANY before, and will sure find a use-case for it. Im not sure it will help me here though, it seems to me that an ANY will not accept a string assignment? I actually think that the "ALIAS" should work, that was a hard found error. I had a fair bit of scratching my head looking for misdirected pointers before I understood what was (not) happening. I will use the work-around of individual structs instead.
Last updated: 2025-03-08

Post by timvh on Problem Reading Registers via Modbus from non Codesys device ^{CODESYS Forge talk (Post)}
According to the documentation: https://wiki.teltonika-networks.com/view/RUT956_Modbus You need to create a Channel to read 2 registers from address 143 to get the lattitude. It doesn't specify if you need to read it as a Holding Register or as an Input Register. You could try both. So in the Teltonika router, you need to enable it as being a Modbus Server. Then in CODESYS add an Ethernet Adapter, then a Modbus Client (Master) and to the Client (Master) add the Modbus Server (Slave). Set the IP address and add the Channel. The please consider that CODESYS doesn't update any variables when they are not used in the application. In the I/O mapping tab of your I/O configuration, you can set the "Always update" to enabled.
Last updated: 2025-03-08

Post by wayne-riesterer on Assignment Efficiency - Repetitive Assignment vs IF statement ^{CODESYS Forge talk (Post)}
Thanks for your responses. I like to write the leanest possible code that I can because it makes it much easier to read/maintain/debug. OR_ELSE is what I was looking for. I wasn't sure if CodeSys short-circuited evaluation and I didn't realize this operator existed. Thanks!
Last updated: 2025-03-08

Assignment Efficiency - Repetitive Assignment vs IF statement ^{CODESYS Forge talk (Thread)}
Assignment Efficiency - Repetitive Assignment vs IF statement
Last updated: 2025-03-08

Post by zdenekkrejci on Issues with Modbus Slave with Raspberry Pi ^{CODESYS Forge talk (Post)}
Did you find out what was wrong? I have the same issue
Last updated: 2025-03-09

Issues with Modbus Slave with Raspberry Pi ^{CODESYS Forge talk (Thread)}
Issues with Modbus Slave with Raspberry Pi
Last updated: 2025-03-09

Post by zdenekkrejci on Issues with Modbus Slave with Raspberry Pi ^{CODESYS Forge talk (Post)}
Did you find out what was wrong? I have the same issue
Last updated: 2025-03-09

Post by nz-dave on Ethernet/IP Scanner Exception ^{CODESYS Forge talk (Post)}
Any ideas?. Still stopping on this exception randomly every couple of weeks. very frustrating.
Last updated: 2025-03-09

Post by struccc on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Strangely reminds me to my struggles... Want to do something "Elegant", reusable, universal, practical... In CODESYS??? 🙃 First of all, before you get too deep into this: If you could find a way, to make a "universal" log entry object, containing the variable length data itself, you wouldn't be able to store them in an array, or access them like an array, or pass them by value as a type. (please correct me, if I'm wrong, incorrect, or not precise). Because... Basically you can't declare a type with variable memory footprint. This is a very deeply embedded characteristic of CODESYS, and all IEC 61131-3 systems, and it has many reasons behind. And yes, it is a very common trap / mistake, to forget about. So, with a log entry - I guess - it's pretty much the purpose: store data and metadata together, and then handle it in a uniform way. There are ways to handle this, really depends on what is the purpose. For example: 1. Entries with fixed length (Maybe it is not as evil as it looks for the first time. Depends on the situation, but definitely the fastest and easiest code) You can have your base object, with an internal, fixed length string or byte array variable. I would go with a string, and call it _Data.; And then you can make properties, like As_Bool, As_Int, As_Real... In the 'set' accessors, you can do like: pReal := ADR(_Data); // POINTER TO REAL As_Real := pReal^; In the 'get' accessors, evidently: pReal := ADR(_Data); // POINTER TO REAL pReal^ := AS_Real; Or, can use ANY type, if you are not obsessed with variable / property like access: 2. Fixed length, but nicer First, some disadvantage to any values: - You can only assign values with write access. No literals, constants, etc... - Can only be used as input variable of function or function_block - Therefore, stg you could reach: LogEntry.Initialize (stVariable|rVariable|iVariable|xVariable); Just a quick example (it's funny to play with ANY): Be careful it was not tested. I'm sure can be done better, please feel free to comment FUNCTION_BLOCK FB_LogEntry VAR_INPUT MsgClass : UDINT; // Like DEBUG, WARN, ERR... MsgCode : UDINT; // Like Errors.ERR_FAILED MsgTS : DT; // The timestamp END_VAR VAR _Data : STRING(80); // Our data container... _Descr : __SYSTEM.AnyType; // A standard descriptor for our data, containing TYPE_CLASS, address and size END_VAR METHOD SET_Value : BOOL VAR_INPUT anyValue : ANY; END_VAR VAR I : DINT; diSize : DINT; pStr : POINTER TO STRING; END_VAR // Check what did we receive in anyValue. diSize := anyValue.diSize; // We use constant __SYSTEM.TYPE_CLASS to identify the received data type CASE anyValue.TypeClass OF // Maybe we don't want to store references, pointers... and who knows what else... __SYSTEM.TYPE_CLASS.TYPE_REFERENCE, __SYSTEM.TYPE_CLASS.TYPE_POINTER : SET_Value := FALSE; // For the planned types we will be just fine. TYPE_CLASS.TYPE_BOOL, TYPE_CLASS.TYPE_INT, TYPE_CLASS.TYPE_REAL : SET_Value := TRUE; // Optionally string can be handled separately, maybe we have received STRING(255), but practically it is shorter than 80 bytes... TYPE_CLASS.TYPE_STRING : pStr := anyValue.pValue; diSize := MIN(anyValue.diSize, LEN(pStr^) + 1); // Get the actual size, and rewrite the received structure member diSize := MIN(SIZEOF(_Data), diSize); // Can chop down the received string to our length... SET_Value := TRUE; // Maybe want to play a little bit more here, to narrow down or convert datatypes, etc... // Or just reject any other datatype ELSE SET_Value := FALSE; RETURN; END_CASE // Fail, if the received value is still larger than our container... IF diSize > SIZEOF(_Data) THEN SET_Value := FALSE; END_IF // Here we should be ok, just set up the _DataType structure, and copy store the data IF SET_Value THEN THIS^._Descr.TypeClass := anyValue.TypeClass; // The typeclass is already filtered THIS^._Descr.diSize := diSize; // Set the (adjusted) size THIS^._Descr.pValue := ADR(_Data); // This will not change, just to be sure {IF defined (pou:SysMem.SysMemCpy)} SysMem.SysMemCpy(_DataType.pValue, anyValue.pValue, TO_UDINT(anyValue.diSize)); {ELSE} // An ugly replacement MemCpy FOR I:=0 TO diSize - 1 DO _Descr.pValue[I] := anyValue.pValue[i]; END_FOR {END_IF} // Otherwise, in case of failure maybe better set an empty value (overwrite the former data descriptor) ELSE THIS^._Descr.TypeClass := TYPE_CLASS.TYPE_NONE; THIS^._Descr.pValue := ADR(_Data); THIS^._Descr.diSize := 0; END_IF METHOD GET_Value : BOOL VAR_INPUT anyValue : ANY; END_VAR VAR I : DINT; END_VAR // We just have to serve the data, using the __System.AnyType structure received // Roughly we can say: IF anyValue.TypeClass = _Descr.TypeClass AND anyValue.pValue <> 0 // This should not be possible, already taken care of by Codesys (?) THEN {IF defined (pou:SysMem.SysMemCpy)} SysMem.SysMemCpy(anyValue.pValue, _DataType.pValue, TO_UDINT(MIN(anyValue.diSize, _Descr.diSize))); {ELSE} // An ugly replacement MemCpy FOR I:=0 TO MIN(anyValue.diSize -1, _Descr.diSize - 1) DO anyValue.pValue[I] := _Descr.pValue[I]; END_FOR {END_IF} // Just to make sure, that our string is terminated... IF anyValue.TypeClass = TYPE_CLASS.TYPE_STRING THEN anyValue.pValue[anyValue.diSize -1] := 0; END_IF GET_Value := TRUE; RETURN; END_IF // ... But can play more CASE anyValue.TypeClass OF TYPE_CLASS.TYPE_WSTRING : ; // Could do conversion TYPE_CLASS.TYPE_XSTRING : ; // Wow, I have to figure this out TYPE_CLASS.TYPE_PARAMS : ; // BTW, what is this, how to use? TYPE_CLASS.TYPE_ANYNUM : ; // ... END_CASE Be careful it was not tested. I'm sure can be done better, please feel free to comment 3. If you really want to do entries with variable size In a standard environment, it would be similar to the previous, except you dont have the container variable _Data, just use a pointer, practically _Descr.pValue At Initialize (SET_Value), you have to allocate the memory, would be easy with SysMem.SysMemAlloc - nowadays with SysMem.SysMemAllocData -, and you make sure to release it after use with SysMem.SysMemFreeData... SysMemAlloc was already hidden. The problem with this, that sooner or later your application will totally fragment the dynamic memory, and fail... So should look for some form of dynMaybe MemUtils.MemoryManager (I am not sure what is the status and the future of it). 4. You will end up by a LogEntry Factory ... 5. You could still have a look at this IEC Snippets BTW, Standard Codesys Logger is not a bad choice either. If you are really interested, I share some more code / library.
Last updated: 2025-03-09

Post by struccc on Problem Reading Registers via Modbus from non Codesys device ^{CODESYS Forge talk (Post)}
Hi, Might be a good idea first to try out the connection and the device with some handy software, like Modbus Poll. There you can see better, what's really going on... - Is it really connected? - What error code does it return? - Can it read from the register address? - Maybe try Input registers and Holding Registers - can make a difference - Sometimes register addresses are messed up: shifted +-1 (mixing of 2 standards) - Sometimes register addresses start with offset 30000, 40000 ... - Are you using the right protocol? - Is it RTU or TCP? Maybe ASCII? - Can even have a look at the data packets, etc... All this is easier to figure out first with some modbus utility... and then to set it up in CODESYS should not be an issue. P.
Last updated: 2025-03-09

Problem Reading Registers via Modbus from non Codesys device ^{CODESYS Forge talk (Thread)}
Problem Reading Registers via Modbus from non Codesys device
Last updated: 2025-03-09

Post by ramesh on DELTA PLC AS228T ^{CODESYS Forge talk (Post)}
Thanks for your reply. Let me try with DIADesigner
Last updated: 2025-03-09

DELTA PLC AS228T ^{CODESYS Forge talk (Thread)}
DELTA PLC AS228T
Last updated: 2025-03-09

Post by nz-dave on ethercat softmotion axis error ^{CODESYS Forge talk (Post)}
Hi all I'm having a little trouble get my axis to work. i can turn them off and on. i can run each servo manually inputting directly to the mapping address. as soon as i try to use any FB's like jog etc my servos wont move and error out. so far I've had error "SMC_ERROR.SMC_DI-POSITIONLAGERROR" and another one about not calling a fb. cheers. in the attachment I have just jogged X_Axis with the MC_JOG FB
Last updated: 2025-03-10

Post by liai on an not create Symbol Configuration in Codesys V3.5 SP20 Patch 4 ^{CODESYS Forge talk (Post)}
Thanks a lot, help me understood more of the concept of sodesys software. May you Have a good day!
Last updated: 2025-03-10

an not create Symbol Configuration in Codesys V3.5 SP20 Patch 4 ^{CODESYS Forge talk (Thread)}
an not create Symbol Configuration in Codesys V3.5 SP20 Patch 4
Last updated: 2025-03-10

ethercat softmotion axis error ^{CODESYS Forge talk (Thread)}
ethercat softmotion axis error
Last updated: 2025-03-10

Post by nz-dave on ethercat softmotion axis error ^{CODESYS Forge talk (Post)}
even tho the drivers are on. it doesn't seem like any online feedback is happening?
Last updated: 2025-03-10

Sort by relevance or date