Hi,

Can you explain where are these coming from, are they predifined by profinet standard/encoder manufacturer, or they are derived from memory words G1-XIST1, G1_ZIST2 and NIST_B?

I am trying to turn on parking mode of the encoder, here is the explanation of G1-STW bit 14 settings:

Measuring system - park mode activation

0: Normal mode

1: Monitoring and position output of the measuring system are deactivated, and the measuring system also does not output any further error messages. The measuring system is inactive on the bus, but the sign-of-life function is active. This function is required e.g. in order to replace the measuring system, without having to change the drive configuration.

Can you say which output it should be, if telegram 81 inputs address are 2...13, and outputs 2...5?

Thanks

In all honesty nothing about your request is clear to me. I gather that you don't know how and where to locate the useful tags in your encoder's IPI/IPO mapping, or find the relevant bits, but since the posted image is not clear either, I hope you will better describe your doubts by posting readable material or the source archive.

The hardware configurator places objects according to the in/out size indicated by its descriptor. The programmer may possibly indicate a different starting address, although in 'TIA portal' the logical address loses its meaning. In fact, I understand that you are, among other things, looking for the bit: #G1_STW.%X14.
After you have assigned the tags in variable table, to the different words of the encoder, e.g. 'g_wG1Stw' AT %IW..., its bit X14 you will easily find. It will be: #g_wG1Stw.%X14.

Yes, I have changed Q addresses of the encoder to 320...323 to be less confused, as you can see in atachment. The problem is that I don't know how to change state of bit 14 of G1_STW.

I am even more confused after I read https://support.industry.siemens.com/forum/rs/en/posts/set-a-bit-in-word-operand/158191/?page=0&pageSize=10 post.

I suppose that G1_STW, according to my addresses, should be declared as G1_STW.%x14, or, according to Williams M322.6, since G1_STW is the second output word which contains 2 bytes where MSB is bit 15 (2 different types of addressing is in question I suppose, symbolic, and "I forgot its name").

I have tried to set bit 14 in different ways, by using memory coil %Q322.6, or something else with G1_STW.%x14 address, but nothing has happened.

In the attached video (15:14 minute) I saw a guy who uses open contact to set bit 14 using %Q322.6 coil (he is setting Kubler's encoder, mine is TR's - I don't see any difference in setting, since it is standard Telegram 81 in question).

Is the only way to set bit 14 if it is represented as %Q322.6 coil, I have tried to use G1_STW.%x14 in different ways, but as I suggest now, G1_STW.%x14 can't be used with coils since it is USint data type (I experimented with Word type, unsuccessfully)?

Gustavo Antonio Banchetti Brucatori

... posting the source archive...
(Archive and post your working project. If it's very big, remove what is not rlevant)

Here is the original, it has only 2 networks:

https://www.gtronic.it/test/index.php/encoder-esempi-e-esercizi-testati-dalling-gottardo/

I am using similar TR's encoder, settings for them are the same, I suppose.

My goal is to learn how to read and set bits of Profinet IO device.

milos23

My goal is to learn how to read and set bits of Profinet IO device.

 It could help learning as well the difference from the 'little endian' and 'big endian' byte orders.

Thanks,

I have tried all three of them, but encoder keeps counting.

I got notifications in case of coils in 2nd and 3rd variants that "access to "..."  with ambiguous address" (tag names are orange).

This description I found in Kubler's Manual for Sendix F5868:

"Parking sensor is active in the initial state

Details about individual application problems are virtually impossible to solve through a forum. You may be lucky to run into someone who has already addressed that exact issue, but you will generically have a better chance of success by consulting the product documentation, which, among other things generically has application examples.

The 'Control Word' is a register that contains bits with various different functionalities. You don't have to look at just one, but at the word as a whole to identify what value it should take on or what machine states to put in place to achieve the desired goal.