(solved) the reason why another identical modbus cp block is not working?

hi, i made two identical modbus cp block in same chart

same id same data type same start address same length etc

however only the second block work, the 1st block just show...nothing, no data, no error, just 0 for everything

is there any

explaination and remedy?

and is there any different between compile all and compile change when i compiling the modbus block?

when to compile change and when to compile everything? 

oh no the FAT is soon

i need to read data from many slaves so that is a lot of jobs, but the job list block got only 5 jobs

is there any solution for this?

Kaulquappe

Hello Tylim,
the Modbus block can only be called once per ID in a cyclic OB.
This is also clearly stated in the manual

Regards,
Kaulquappe

 the only solution that i can come up to is to use counter to "queue" the modbus block with different job, any better solution?

When you download the job list block you get the stl and scl sources of the block. So you could extend the job list block to more than 5 jobs. 

It is described in the manual:

Additional Modbus Block Manual

The function block provides 5 jobs by default. The number of jobs can be increased

if necessary. To achieve this, the following changes are mandatory:

􀁸 Open the source of the job list block.

􀁸 Copy the inputs Job5_DATA_TYPE, Job5_START_ADDRESS,

Job5_LENGTH and Job5_WRITE_READ and insert them below job5.

􀁸 Rename the inputs to Job6_DATA_TYPE, Job6_START_ADDRESS,

Job6_LENGTH and Job6_WRITE_READ etc.

􀁸 Adjust the static variable Count_of_Jobs according to your changes.

Gwawl

When you download the job list block you get the stl and scl sources of the block. So you could extend the job list block to more than 5 jobs. 

It is described in the manual:

Additional Modbus Block Manual

The function block provides 5 jobs by default. The number of jobs can be increased

if necessary. To achieve this, the following changes are mandatory:

􀁸 Open the source of the job list block.

􀁸 Copy the inputs Job5_DATA_TYPE, Job5_START_ADDRESS,

Job5_LENGTH and Job5_WRITE_READ and insert them below job5.

􀁸 Rename the inputs to Job6_DATA_TYPE, Job6_START_ADDRESS,

Job6_LENGTH and Job6_WRITE_READ etc.

􀁸 Adjust the static variable Count_of_Jobs according to your changes.

 

 

Kaulquappe

Hello Tylim,
here you can find the sources of the job_list_block if you haven't got them:
https://support.industry.siemens.com/cs/ww/en/view/62830463

Regards,
Kaulquappe

 what if i have many slave, each with many job?

the job block only allow me to cyclic over data type, length ,read write and start address, but not UNIT (slave id) 

ok, the thing is,

i have one moxa which convert modbus rtu to modbus tcp

the modbus rtu is connected to let say 10 slave, each slave with 6+jobs

the modbus tcp is connected to plc (client)

i need to read data from this 10 slaves

there would be also another moxa (redundant) connect to the secondary modbus rtu port of the slaves i mentioned above 

moxa itself have ip