Addressing input variable ^{CODESYS Forge talk (Thread)}
Addressing input variable
Last updated: 2006-07-21

J1939 addressing ^{CODESYS Forge talk (Thread)}
J1939 addressing
Last updated: 2009-01-08

indirect addressing ^{CODESYS Forge talk (Thread)}
indirect addressing
Last updated: 2011-12-06

UDP Modbus Addressing ^{CODESYS Forge talk (Thread)}
UDP Modbus Addressing
Last updated: 2009-11-22

Modbus Slave Decimal Addressing ^{CODESYS Forge talk (Thread)}
Modbus Slave Decimal Addressing
Last updated: 2022-02-07

Indirect Addressing ^{CODESYS Forge talk (Thread)}
Indirect Addressing
Last updated: 2020-10-14

Memory addressing ^{CODESYS Forge talk (Thread)}
Memory addressing
Last updated: 2022-07-03

Devices addressing ^{CODESYS Forge talk (Thread)}
Devices addressing
Last updated: 2019-03-14

Addressing memory area ^{CODESYS Forge talk (Thread)}
Addressing memory area
Last updated: 2022-08-31

Bit Addressing in integers ^{CODESYS Forge talk (Thread)}
Bit Addressing in integers
Last updated: 2010-03-16

Modbus non-standard addressing FC3 ^{CODESYS Forge talk (Thread)}
Modbus non-standard addressing FC3
Last updated: 2019-02-08

Integer Addressing at the Bit Level ^{CODESYS Forge talk (Thread)}
Integer Addressing at the Bit Level
Last updated: 2018-05-30

How to Fix gateway automatic addressing? ^{CODESYS Forge talk (Thread)}
How to Fix gateway automatic addressing?
Last updated: 2013-12-06

Indirect addressing memory/input/outputs ^{CODESYS Forge talk (Thread)}
Indirect addressing memory/input/outputs
Last updated: 2017-06-07

Addressing I/O by string configuration ^{CODESYS Forge talk (Thread)}
Addressing I/O by string configuration
Last updated: 2019-02-14

addressing other memories than register memory ^{CODESYS Forge talk (Thread)}
addressing other memories than register memory
Last updated: 2009-06-05

Indirect addressing for bit number of a DINT ^{CODESYS Forge talk (Thread)}
Indirect addressing for bit number of a DINT
Last updated: 2021-04-01

BOOL ARRAY direct addressing on modbus area ^{CODESYS Forge talk (Thread)}
BOOL ARRAY direct addressing on modbus area
Last updated: 2005-10-11

Addressing Beckhoff KL Terminals with BK9100 Bus Coupler ^{CODESYS Forge talk (Thread)}
Addressing Beckhoff KL Terminals with BK9100 Bus Coupler
Last updated: 2021-11-02

Modbus issue with addressing for Read Coils ^{CODESYS Forge talk (Thread)}
Modbus issue with addressing for Read Coils
Last updated: 2023-01-31

PLC symbolic addressing with weintek panel ^{CODESYS Forge talk (Thread)}
PLC symbolic addressing with weintek panel
Last updated: 2021-04-17

BOOL ARRAY direct addressing on modbus area ^{CODESYS Forge talk (Thread)}
BOOL ARRAY direct addressing on modbus area
Last updated: 2005-10-11

Post by smartcoco on Bit / Bool data types in function parameters ^{CODESYS Forge talk (Post)}
Memory addressing is measured in bytes, with BOOL occupying one byte. BIT is quite unique as it occupies one bit. So, try not to use BIT in the program. You can use the Unpack function to solve your problem.
Last updated: 2024-01-18

Post by vernon-laurence on EtherCAT fieldbus ^{CODESYS Forge talk (Post)}
The simplest way to do this would be to add a bus coupler dedicated to the expansion IO. The EtherCAT network does not fault when modules connected to the expander are not present. In the image below, nothing below the red line is present in the network - with the network working correctly. In your "base" project, simply include all of the possible modules, and then plug them in as you add pumps to the system. I would also highly recommend against the use of direct addressing. There are other methods to accomplish this, including using the "Optional" checkbox for modules and explicitly addressing them. Although, this would require more upfront work to design the network, and some additional work each time modules were added. https://content.helpme-codesys.com/en/CODESYS%20EtherCAT/_ecat_edt_slave_slave.html
Last updated: 2024-04-09

Post by mubeta on STRUCT AT %MW1000 ^{CODESYS Forge talk (Post)}
This is normal and correct since in CoDeSys static addressing of variables uses the IEC method. A LONG tag has the size of 8 bytes, so %ML0 coincides with %MB0 ... %MB7; %ML1000 with %MB8000 ... %MB8007. (Similar reason for word and other formats). Also the reason the compiler won't let you map the structure to a %MW depends on the fact that the individual base elements are manipulated to 64 bits regardless of the smaller size. That said, it makes me strange that you cannot write a parser without making use of static memory allocation.
Last updated: 2024-08-13

Sort by relevance or date