Hi all!

Running into an issue, that I don't understand completely:

I have an existing network, running 6 converters and an et200 on profinet. I am using an CP, so I added the FC12 and FC13 to send and receive data to/from CP.

Working great.

Now I am trying to add a M-BUS to profinet converter, but somehow I am not getting any contact.

Attached SS's from first attempt. I have already removed some signals to try with 16 bytes, but still no luck.

I have updated firmware to latest version.

Does anyone have an idea what might be wrong?

Thanks!

Please doublecheck:

IP is .13 or .9?

Hello,
You have also a slot with 4 bytes output defined. Do no see this in the Mbus module configuration.
Every slot of the IO-device must match to reach a successful configuration.

Try also to detect the Mbus with the free tool PRONETA with a PC.
It has a GSD Manager. In the GSD (“General Station Description”) files, the properties of a PROFINET I/O
device are saved by its manufacturer. So in general, every device can be inserted into a PROFINET configuration, if only its GSD file is available.

This will give you some info:
- is the device answering
- does it have the correct/expected IP?
- does it have the name set?

Hi IBN

IP is 192.168.2.13, device ID 9.

The Output part is generated automatically, I am not able to change that. The ADF WEB software tool automatically generates the XML file, so I would think they match.

I will try the tool, thank you very much!

Hello again,

See attachment. So it seems the device is available? Name and IP match, but still nothing.

Hello,

I see that you have an X200 swich.
If you connect the device to that switch, and you mirror the port to the PC, you could take a trace with the free tool Wireshark. Wireshark understands PNIO and you will be able to see if the mbus reacts to the CP, what they negociate, etc ...

On the other hand, the blocks for transferring the PNIO data between CP and CPU have error information.

The example here claims to have status evaluation included.
May be interesting to analyze and to investiate if the problem comes from the  Step7 part.

I did check with wire shark, but I can not make much sense of it. The controller keeps asking for the "mbus" slave. I see an some adfweb messages to. But nothing more. I am in over my head here. :)

I appreciate the help!

Hello,

What you have documented are LLDP frames, not PNIO frames.

You can save the trace with file ==> export pacquets.
And post it here.

To get a valid copy on the tracing PC of the traffic between CPU and mbus module, you must activate the mirroring in the X200 and tell that you want a copy of the port where the mBus is installed to the port where the PC is connected.

I will give it another shot tomorrow.

The only PNIO messages were coming from the controller, these messages were the only one that came from the device.

Thanks again, I will get back to it tomorrow :)

Hi again!

Attached the export of wireshark. I am waiting for ADFWEB to get back to me, I think the issue is there. The S7 part looks fine. The program example you supplies is how I actually implemented the system and I have no errors what so ever there, just the working/ successful codes. Just this darn device that is not popping up.

Thanks again!