SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Profibus OLM addressing

9/23/2014 7:33 AM	Rate (0)
Jengeese Posts: 84 Rating: (0)	Hello all, We have a profibus OLM module which collects more than 10 TAE servo motor drives information via profibus and change it to fiber first and then to ProfiNET (by a scalance). I am able to see profibusaddressing of these motor drives to take or give information on hardware configuration of PLC. However these are so different. I seethe same motor drive's(for example, not real values) profibus address 12 and for communication address W#16#208. And I confused about the translation. How can theprofibus address 12 corresponds to 208 hex?? How I can calculate or see this translation from Profibus address 12 to W#16#208 (example)?? Thanks for your help.
Jengeese Posts: 84 Rating: (0)
Suggestion To thank Quote Answer

9/23/2014 1:06 PM	Rate (0)
Navnag Platinum Expert Joined: 11/21/2007 Last visit: 3/16/2025 Posts: 2326 Rating: (309)	Hello Jengeese Jengeese Hello all, We have a profibus OLM module which collects more than 10 TAE servo motor drives information via profibus and change it to fiber first and then to ProfiNET (by a scalance). Usually this should be a IE/PB LINK and not a Scalance ... Jengeese I am able to see profibusaddressing of these motor drives to take or give information on hardware configuration of PLC. However these are so different. I seethe same motor drive's(for example, not real values) profibus address 12 and for communication address W#16#208. And I confused about the translation. How can theprofibus address 12 corresponds to 208 hex?? How I can calculate or see this translation from Profibus address 12 to W#16#208 (example)?? . If you open the hardware configuration, you will notice that besides the Profibus address ( 12 , 13 etc ) each drive also has a peripheral address area ( PIW / PQW ) assigned to it. What you are seeing in the program is the Peripheral address ( PIW / PQW ) : e.g. W#16#208 Hex = 520 Decimal .. i.e. this is referring to the drive with peripheral address starting with PIW / PQW 520 and so on. Hope this helps Cheers Navnag
	There is no such thing as the last bug in a program There are no stubborn bugs, There are only stubborn Debuggers.
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Fafner

9/24/2014 8:43 AM	Rate (0)
Jengeese Posts: 84 Rating: (0)	Thanks for explanation. Now it is clear for me..
Jengeese Posts: 84 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Navnag

Share this page:

Share this page on...