Please help with DF1 to DH+ Passthrough

I want to link my office PC to a PLC on our Block Plant floor.
I've run into some snags with "The Money Man" in our main office reguarding the cost of a KTX card. Anyhow...I've run 'blue hose' from the Block Macine PLC to the Office, and used a Spare Rack with a Spare 5/04 as an interface in the office. I hooked it all up but in Linx I couldnn't connect to the Machine PLC through the office PLC DF1 port. I used RS Logix and enabled "DF1 Pass thru" in the status file thinking that it would solve my problem....I got bumped offline from the PLC in the office, which i was hooked into via DF1, and an error message came up saying i had to DL from the eeprom or UL the file. I was THINKING that I'd be Downloading to the office PLC to which I was attached, BUT, when I DL'd the logic to the PLC (blank logic - no rungs)it went into my Machine instead and I lost the entire Day's production figures...not to mention all of the past 6 months of tweaking the settings. Thats about when I took the blue hose off and said to hell with it.

I just read a post about PT (Pass Thru) Drivers and my questions are....

What exactly did I do when I enabled DF1 Pass thru and should I leave it enabled or not?

Should I be using a different driver to "see" PLC's on the DH+ instead of the DF1 Driver ?

My Main goal is to be able to use Excel with DDE or OPC to display real time production figures and also play with my RS View32 project.(Animated Block machine)

Thanks in advance
Jon

PLEASE!!! Any info may be of some help in this, if ANYONE knows or thinks they know ANYTHING that may be of relevance or might help PLEASE share your thoughts. Thanks!

When you configur your driver il RS linx did you try to configur KTX instead DF1?

maybe this will help ...

Jon,

maybe you’ve got this all figured out by now but this is the first opportunity I’ve had lately to work on this problem ...

this morning I went to the lab and set up a pass-thru example ... I used an SLC-5/04 as the pass-thru device ... I connected the SLC’s Channel 1 (DH+) port to the Channel 1 (DH+) port on a PLC-5/11 with “blue hose” cable ... note: I’m betting that all of your processors are SLC’s - but since you called the “Machine” one a PLC (as opposed to an SLC), I decided to use one controller from each platform in my example ... the basic approach should remain the same ... anyway ... I connected the SLC’s Channel 0 (serial) port to the COM1 (serial) port on the back of my programming computer ...

next I set up the RSLinx DF1 Driver to communicate with the SLC ... basically I used the Auto-Configure “sissy button” to make the connection ... this worked fine ...

next I used RSLogix500 to go online with the SLC processor ... I went to the Processor Status screen and clicked on the “Channel 0” tab ... I set S:34/5 (the Pass-Thru Enable Bit) to a “1” ... as soon as I “OK’ed” the change, I lost communication with the SLC (but I’ve done this before so I expected this loss of communications) ...

next I went back into RSLinx and reconfigured the DF1 Driver to set the “Device” entry for a 1770-KF2 ... basically this converts the SLC’s RS-232 port into a “communications adapter” ... (Arik was close) ... see red circle below ...

[attachment]

next I shut down RSLinx COMPLETELY ... and then turned it back on again ... sometimes operations like this need to be “kick started” ... when RSLinx warmed back up again, I could “Pass-Thru” the SLC’s DF1 connection and see the PLC-5 over the DH+ blue hose connection ... SUCCESSFUL COMPLETION OF A PASS-THRU EXAMPLE! ... note: this RSLinx “warm up” period can take a minute or two so be patient and give it a chance to work ... remember that you’ll be communicating through a 19.2K baud rate “bottleneck” and all of the DH+ network addresses are being “browsed” for active nodes ...

and I took the liberty of drawing in the cable connections on the RSWho screen shot above ... I figured that it might help to see what’s hooked up to what ...

and for those who are wondering ... yes, this Pass-Thru approach CAN be used to “work around” the need for a Data Highway Plus communication device (examples: 1784-PCMK or 1784-KTX, etc.) ... sometimes knowing this little trick can get you out of hot water if you show up at a job site and discover that you’ve left part of your “communication gear” back at the office ... specific case in point: the older “classic” PLC’s (example: PLC-5/15) do NOT have an RS-232 communications port ... you MUST use DH+ to go online with one of these animals ...

finally, once you’ve got this thing working, the best way to get “online” with a processor is to go to the menu at the top of RSLogix and click “Comms” and then “Who Active Go Online” ... this will open up RSLinx and give you a chance to “click around” until you’ve highlighted the processor you actually want to communicate with ... this will give you a much better shot at “dialing in” the one you really want and help to minimize the chances of downloading to the wrong one ...

PS Edit ... you said:

My Main goal is to be able to use Excel with DDE or OPC to display real time production figures and also play with my RS View32 project.(Animated Block machine)

Click to expand...

actually you might have a problem achieving this particular goal ... don't forget about that RS-232 "bottleneck" ... your "Pass-Thru" communication link is likely to be too slow for any substantial "data collection" or "animation" projects ... so I wouldn't get my hopes up too high ... and by all means, try to make friends with the "Money Man" you mentioned above ...

option

we had at on time a similar operation on a slc 504 and what we did was run a belden cable thru an AB ST card. to channel 1. then use total control software to create a visual of the machine. Another option is to communicate via modem. which tends to be the standard here for remote operations. keep in mind a network cable will only work to 300 ft serial communications via RS 232 50 ft. Belden DH 485
1000ft.

ALLRIGHT!!!!! You got me going good now RON! Thankyou so much. I'm still not able to "see" my DH+ Nodes on my laptop, however I'm able to see them using my desktop. Maybe I need a linx update? I've never used the desktop to connect to anything because of the distance from the desktop to the SLC's on the plant floor. I got Linx and RS Logix 500 on my desktop PC specifically for this DH+ I was TRYING to set up.

Now that this all works I'm stumped again. I've never really used dde/opc extensively. I've only configured one topic and it was a local connection. Now I need help figuring out how to configure a new dde/opc topic for my Machine PLC - which is also an A/B 5/04.

I think I have to setup the advanced communications tab? See...after loosing all my logic the first time around, I'm not too keen on the idea of screwing things up again due to ignorance. I just need some pointers on setting it up right the first time. So I want to set up hotlinks in excel. Show me the way! Thanks in advance, and Thanks again Ron!

Comunication with cpu 5\04

I've been tried to communicate with a AB 5\04 cpu, but without success. I'd like to know with somebody could help me...We have a machine using a comum PC with a supervisor "WINROBOT" communicating to 5\04 using a COM1, because their aren't near, the PC are using a external converter RS232 to RS422, at the plc cabinet,have another external converter RS422 to RS232 and goes to RS232 of the CPU 5\04. I tried to use the same cable I used with a 5\03, but it didn't work. I'm using a RSLogix 500 version 4.5, RSLinx version 2.1. The drive is AB_DF1(RS232) and I tried the "Auto configuration" button, it didn't find any node...I don't understand, how the PC can communicate using this port (RS232) and I can't...Another thing, I opened the backup and the drive was AB_KT1. Is it possible to communicate without use this drive (DH+)

Need more help - YEARS LATER!

HI! I'm always stunned when I do an internet search and find that I've inquired about something and gotten the answer on a forum...so here I am again. I am trying, again, to do a DF1 Passthrough - same exact configuration however, I am having an issue with this one that I haven't seen before. I have 2 SLC 5/04's and 2 Panelviews inter-connected via bluehose, DH+. I am using SLC #1 as my DF1 connection point, when I set the DF1 passthrough bit to 1, I expected that I would lose communications on Channel 1, however I did not. I can still communicate with the SLC using the DF1 Driver...the KF2 Driver works as well with SLC #1, but neither SLC#2, or either of my panelviews show up in Linx. I do not have terminating resistors installed. Could the lack of the resistors be causing this?

Resistors should be there, but may not be your problem.

Can you post a screen shot of your RSLinx's setup? ( configuration screen)

soop7667,

More info, there are a couple of bits to set and the OS of the SLC5/04 must be OS401
or greater,

See pdf below for how to set it up.

I tried adding a Screen Shot, but I am having issues with that. I picked up some Device Net terminating resistors, 150 OHM, hoping that they would do the trick, and still nothing. I stayed late today so I could be here for the downtime and I played and played with settings. I don't know why, but when I use the DF1 driver configured for KF3 - my nodes showed up, so we're all set there.

Next issue - or you could say this is on my wish list: I have a DH485 network attached to SLC#2, not the one that I am passing through, rather the one I am passing through to. Is there a way for me to see my DH-485 nodes in linx through my DF1 passthrough? I have a 1761-NET-AIC connected to SLC#2's DF1 Port.

If I understand you, you have the DF1 to DH+ passthru working and you have connected to the serial port of SLC#1 and passthru to the DH+ network to see SLC#2. And now you want to go from the DH+ passthru on SLC#2 to it's configured DH485 port.

I don't think you can do that. So if it can be done one of the AB guru's will have to jump in and tell us how.

Well...I learned a good leson today. If you're going to change something with your comms drivers and network set-up while you're down, make sure you are there when it's going to be started back up! I managed to stop production from ever beginning with my little driver experiment. there were some strange things happening with my KF3 driver running. One of my Panelviews, a touch-screen only unit, would not communicate at all and it shut the entire plant down this morning for an hour! I could "see" all of my DH+ devices in linx at first, but then it dropped the panelview from the list. I could get DDE data from either SLC#1 or SLC#2, but once I received data from #1, #2 disappeared, and vice versa. As soon as I disabled the KF3 Driver, all my comms went back to normal. I am at my witts end on why this isn't working. My KF2 driver allows me to see only the PLC I am connected to via DF1 - and the same driver configured for a SLC displays the same way. For some reason I just can't seem to get data from both, and I'm still confused as to why when I enable DF1 passthough I don't get kicked off and have to use the KF2 Driver. SLC#2's serial port is configured for DH-485, could this have any bearing on my set-up?

KF2, KF3 driver? Do you mean device type see picture below.

The driver should be RS232 DF1.

The 1770-KF2 device is used when you are passing thru from DF1 to DH+.

The 1770-KF3 device is used when you are passing thru from DF1 to DH485.

Did you follow the instructions I posted in post #10 above?

To clearify, yes I meant device type. All settings were set as detailed in your post. Error checking is set to CRC however, and matches the comms settings on SLC#1. The KF3 Device worked to some degree - it was allowing the nodes to show up in linx, but DDE data would only work with one topic at a time. For example, I would get data from SLC#1, and SLC#2 would show N/A in Excel. By clicking in the cells formula for data that comes from SLC#2's topic then hitting enter, it would update all of that topics data in the Excel sheet but SLC#1's topic would all display as N/A and I would get no data.

This time around these changes are not behaving as it has with past set-ups, primarily it is not kicking me off once the DF1 Passthrough bit is set to true. My DF1 Driver configured for a SLC device still works.