Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

S7-300 and Prosoft PDPS Profibus SLave

Created by: ostarated at: 7/17/2012 3:29 PM (2 Replies)

Rating (0)

Thanks 1

3 Entries

7/17/2012 3:29 PM	Rate (0)
ostarated Posts: 17 Rating: (0)	Hi, I am trying to use the Prosoft profibus slave interface. I have configured the card as address 50. In my simatic manager hardware configuration I have added the Prosoft GSD file and then added the Prosoft module to the DP network. I filled the slots 1 to 5 with 16AI - 16 word Input, slots 6 to 8 with 16AO - 16 Words Output and the remaining 6 slots with Empty Slot. After downloadiung the configuration and restarting the PLC, the PLC does not recognize the new profibus node. We have checked the cabling - the node is the first node after the PLC, there are 65 nodes after this and they are visible. The network card is CP 5613 and the PLC is a micorbox WinLC RTX v4.6. I have spoken with Prosoft tech support and they have run out of ideas to try. Thanks
ostarated Posts: 17 Rating: (0)	Last edited by: ostarated at: 7/17/2012 3:30 PM
Suggestion To thank Quote Answer

7/17/2012 7:24 PM	Rate (0)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 11/18/2024 Posts: 12294 Rating: (2691)	Hello ostarated; Do you have any diagnostic LEDs, either on your DPDS module or on the Profibus-DP master? If you have a BF LED active on the Dp master, have you checked the diagnostioc buffer (it should contain data on the event that caused the appearance of the BF). From the Prosoft manual for your DPDS: Master/Slave Communication Phases The communication between the Master and the Slaves takes place in the following phases: · Parameterization and configuration phase · Usable data transfer phase Before a DP Slave can be integrated into the usable data transfer phase, the parameterization and configuration phase runs a device identification test that verifies that the planned configuration matches the actual device configuration for each slave in the PROFIBUS network. The test verifies that: · the device is actually there · it is the right type of device · the address, which is set on the device, matches the station address on the bus · the formats, telegram length information, and bus parameters are correct and · the number of configured inputs and outputs is correct. If the DP master finds anything in the slave that does not match the configured values, it might declare the slave deficient and not "see" it anymore on the bus.Try to find out what is not acceptable in the slave. For example, posting a scrrenshot of the modules configured for your slave in the S7, compared to those of the Prosoft configurator, might help, that is where most of the mistakes are made when inserting a 3rd-party slave to a Siemens DP-master. Hope this helps, Daniel Chartier
	Last edited by: dchartier at: 7/17/2012 7:26 PM
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users SOble

1/29/2014 1:20 PM	Rate (0)
CS Moderator Moderator Joined: 9/1/2005 Last visit: 11/18/2024 Posts: 4113 Rating: (195)	follow up question published by RBMis split to a seperate thread with the subject S7-300 and 5205-BACNET-PDPS Client. Want to send 200-250 words Best regards CS Moderator
	My Forum is the place to personalize your profile, track your topics, and maintain content that interests you. Best regards CS Moderator
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on