GE 90/30 Horner Profibus HE693PBM101

[Chris Elston 78]

I got this new master module for an upcoming 90/30 profibus system, Horner HE693PBM101 master card. There are some configuration settings for SYNC or FREEZE and other settings I have questions about. SYNC/FREEZE Sync/Freeze Control Area = %Q00001 What exactly does this mean? I have Output cards that start at address %Q00001. Three 32 output cards, so my last availbe %Q should be: %Q97. From doing some light reading, it appears this module needs some outputs to mirror some status somewhere. So being that my last output is %Q96, then do I need to set my Sync/Freeze Area = %Q00097? Can I skip some %Qs? Just in case I add another output card? DIAG DATA SLAVE I am not using an %AQ00001 memory so my Diag Data Slave Address Area could be left alone at %AQ00001 DIAGNOSTIC FLAG AREA This setting is in the same boat as my output cards, I already have some input cards, 3 32 point input cards, so I am assumming I need to change this to my next input %I00097. Can I skip some %Is? Just in case I add another input card? SLAVE MODULES CONFIGURATION In the slave area, it appears I can change the starting input address to anything I want. That seems excellent to me. Great flexiblity for sure. Well hopefully someone out there has messed with one of these Horner Cards and can offer some feedback. I already bought the thing, it appears pretty straight forwarded.

[rocket1010 0]

Hi, new to the forum so bear with me. If the Profi card is anything like the Ethernet cards used on the 9030 platform then I think your assumption is correct "then do I need to set my Sync/Freeze Area = %Q00097?" Ethernet cards need 80 bits of %I memory for status. You must therefore adjust the starting/end point of the real inputs to accomodate the status data area. I think your on the right track. Hope this offers some insight. PS. Love the forum everyone, keep up the good work!

[Steve Bailey 118]

I've never used the Horner Profibus module, but I have used the Horner DeviceNet module. I expect that the rules that apply to DeviceNet addressing will also apply to Profibus. To the CPU, the network interface module looks like a big combo input/output/analog input/analog output module. In PLC configuration, you define a starting address and a length for each of those four data types. The %I addresses for the data from all of the input modules on the network must be contiguous, as must the addresses for %Q, %AI, and %AQ. If you want to leave space for expansion, leave it between the address for the network module and the other I/O modules in the syatem. The module itself will use some %I and %Q address space (possibly some %AI and %AQ too). The %I space will be status bits informing the PLC about the health of the network module and the network itself. The %Q bits will be commands from the PLC to the network module. My experience is that Horner manuals are not models of clarity, but Horner technical support is very good. If at all possible, try to schedule a few hours to set up a network module in a rack with a couple of drops on the network, just to get a feel for how it all goes together. Do this before you commit to an addressing scheme so you don't have to change a lot of drawings later when you realize you left something out. It would be even better if you can get the PLC Specialist from your distributor to come in and help you get it set up.

[Chris Elston 78]

Steve, Your starting to scare with me with that comment. I've done alot of device net systems so I know what you mean about addressing your modules and releasing prints to assembly, then realizing you screwed up your slave module addressing because you forgot to give a word here or there for a status word that comes back to the master (scanner). However after looking at the Horner stuff, it looks more flexible and appears I can move addressing around more a bit in this master than an Allen Bradley SDN (device net scanner) card. I am in the process of getting the rack setup, (I beat you to it), just waiting on some profibus cables to show up. That's great to know that Horner has a great tech support, I've also got some e-mails from GE that said they are willing to help me out with the profibus config if needed. I'd like to take a stab at it myself. So far it looks alot easier to me than an a device net system. I am excited to give it a shot. I've got a TEN slot rack with 3 inputs and 3 out cards and a Horner in the last slot. This leave two spare spaces. I was going to skip two words for both the input and output, because we use 32 point cards, then start the I/O addressing for the slaves. I am using those new Verasa IP blocks. Dual denisty 8 ports, which gives me 16 points of I/O. Input only blocks. So in my mind I want to address it like: RACK - Input Card 32 - %I1 thru %I32 RACK - Input Card 32 - %I33 thru %I64 RACK - Input Card 32 - %I65 thru %I96 RACK - Output Card 32 - %O1 thru %O32 RACK - Output Card 32 - %O33 thru %O64 RACK - Output Card 32 - %O65 thru %O96 RACK - Spare space (two words) future input card - %I97 thru %I128 RACK - Spare space (two words) future output card - %O97 thru %O128 VERSA IP BLOCK - Node 2 Input Only one word - %I129 thru %I144 VERSA IP BLOCK - Node 3 Input Only one word - %I145 thru %I160 VERSA IP BLOCK - Node 4 Input Only one word - %I161 thru %I176 MAC CONNECT VALVES (SM-128 connect) - Node 5 Output Only eight words - %O129 thru %O256 HORNER CARD - Node 1 configuration after that...Last %I177 and %O257 example: SYNC/FREEZE = four output words (%O257 thru %O320) Am I thinking screwy?

[rocket1010 0]

Quick question concerning Profibus comm using 9030. Is the COMREQ function the only way to pass Master/Slave data, or is this done through a data table similar to EGD? Can't find any definative answers on this, my hunch is COMREQ, but I hope I'm wrong! Thanks

[Chris Elston 78]

I am happy to report I cofigured my Profibus system the way I described above and had no problems. Took me 1/2 hour to get my Profibus card talking to my slave I/O points. By far easier than DeviceNet with AB using this GE controller...sweet...Everything is configured in the Master card using VersaPro. No need to by "devicenet" software. Nice setup GE!