stickman47

Thanks for the help. I'll have to wait for a non-production day and try all that....

I don't know what it wants me to use...

pcmccartney1,   Attached is the expanded view of the Design Tab. None of the listed devices can be used. I am really at a loss on this one. I have never had this problem before. Maybe I nee to re-install F/T View Studio or RsLinx.

Here are the screen images. I hope this helps. I was unable to resolve this issue by copying the Design to Runtime.

I don't have the ability, on this computer, to take screen shots. IT has such things blocked. I know I am doing something wrong so I'll try to re-cap. I uploaded an existing MED file from a PV600 +. I restored the MER file from that and made some changes and additions. I went to restore the communications protocol, while online with the target processor. My shortcut is shown in the left pane. The Design side is browsing and it locates the target IP address of the processor. It briefly says "This device has been assigned to the shortcut". The Target side says the path cannot be used, try another path. When I verify it says the path is linked to an invalid device. I have this problem with more than one HMI so I know I am missing a step somewhere. Is there a definitive instruction set, or bulletin that has my answer?  

Kaiser_will,   I am using AB_ETHIP-1 as the Ethernet driver.

I have a project in Logix5000 that I am stumped on. I need to track Time Of Day to reset a counter at the start of each shift. I am working with a CompactLogix L24ER. I have done this with Seimens Step7, using their TOD block, but I don't see anything like it in 5000.I tried to understand the GSV block but it was too confusing. Are there any examples I could draw from?

Since the untimely demise of my laptop I have been forced to use a Laitiude X1 with a screen the size of a postage stamp. This little cutie doesn't have any ports, except 2 USB 2.0's and an ethernet. I have a USB to serial adapter cable and have used it successfully on our many SCL500's, using RSLinx Professional to Auto-Configure a DF-1 driver. I haven't had as much success with Micrologix though. I can get to my 1400 as it has a regular DF-1 port and an Ethernet port, but I can't get on with anything lower, 1000, 1100, or 1200. At best I get an error during the CRC/BCC test, but usually it goes through all the settings and can't configure the port. Anybody got any alternative comm. suggestions? I have a program change to do saturday night and I might have to temporarily transfer RS500, and the activation, to another computer that has a serial port. I'm sure RA will appreciate that...

I have 7 AC Masterdrive CUVC drives, in 3 machines. Last week one on the machines started blowing the pre-charge board, for no apparent reason. This machine has an isolation transformer on the line. The transformer was checked out and found to be good. Drive 'A' blew out first. After replacing the charging board, firing card and line fuses, we started up o.k. After about an hour the charging board on drive 'B' blew out the same way. We replaced the damaged boards and started up again, without incident. After a week of running, the charging board on drive 'B' blew again. Again we replaced the damaged boards, but this time we also had to replace the Inverter card as we were getting "F011" Overcurrent fault on start-up. Since then we have been running, without incident. We have a recorder on the line phases and see no ripple or spikes. We had a Siemens technician in to help us explain this problem but he was at a loss to tell us why the pre-charge boards are exploding. We have inserted a piece of teflon, between the pre-charge board and the firing card to prevent losing the firing card again, if the charging board should decide to explode. Has ANYONE experienced this, seemingly random, loss of precharge boards? Drive info is: 6ES7033-7EG60-1AA1-K80 w/ CUVC and CBP2.

Thanks for the Info. I kinda figured that was the answer....

Gents, I have an operator screen running from a PC that is running WinCC Runtime 2007. My boss wants me to make some changes in the screens but I don'thave the .HMI file associated with the RT file. Is it possible to convert the .FWX file back to an HMI for editing?

Is it possible to upload the file from a TP27-6 HMI to a PC running ProTool v 6.0? I need to make changes but I don't have the original file. The ProTool program has an UPLOAD option but I cannot get the serial communications to work. I have the right cable beacuse I am able to DOWNLOAD a screen program to my spare screen. Any suggestions would be appreciated, short of replacing the TP27 with a "real" HMI... Stickman47

Folks, I am stuck on a project using a differential encoder with the 1746-HSCE card. I have a problem with the card not counting after several cycles. In my program a floating register, f8, is tracking pulses at f8:9. This project is tracking end welds in a steel strip operation. The end welds are detected by a luminosity scanner which starts the sequence. This input resets f8:9 to zero and counts pulses. After a pre-determined count an output triggers to open a gate. Once the end weld clears the gate it closes and waits for the next end weld trigger. The problem is that SOMEWHERE the counts are accumulating and the HSCE stops counting. The card is NOT faulting, it just stops counting at what ever value it may be. Is there a limit on accumulated counts? If so, how can I reset, or even monitor this? The HSCE card hardware configuration created an input word, I9.0 thru I9.7. I can see the bits changing as I turn the encoder but I don't know which bit I should be using. The ideal set-up would be the Z channel of the encoder since it only pulsess once per revolution, but I have no idea what the 127 bits of this input represent. Can anyone make sense of my ramblings? Help!

Steve, This is exactly what I am trying to accomplish, and have, in fact, accomplished what I set out to do. Unfortunately, this module has many secrets. It is continuing to acumulate pulses and I don't know how to reset them..

Thank you for that information. I looked over the section and found that bit I:9.0/13, count overflow, is being set after approx. 3 cycles. This bit can only be reset by re-initializing the program (RUN to PROGRAM and back to RUN). This is not practical as the encoder will be constantly turning as the strip passes under it. How can I prevent this overflow? Is this part of the configuration? The manual does not address this issue.

I have a huge problem with an Analog Output project. Normally I would use FC105 and FC106 to accomplish this but, in this program, a previous editor wrote ladder code and STL within FC105. This logic is causing FC105 to not be available. I need to know if there is a way to convert an Integer to a real number, and then back to an Integer for use in a PQW. I am ok with LAD but know nothing about STL or FBD. Currently I am using an Integer, multiplied with MUL_I, to get Analog Out at 0-10VDC. The accuracy is not there since I am using Ingeters, I need to get to Real numbers to properly scale the A/O. Any information would be appreciated.

Awesome! Sounds too easy to be true, but it makes sense. I will need to do the same with FC106 as the provious programmer screwed that up too. Thanks Moggie!

Is there a function to convert a DWORD to ascii? I need to send a speed value to an ascii display via profibus.

I am trying to set up an Analog Output as 0-10VDC in an established program. The basis for this output is an integer. I have read where FC 105 and FC 106 can be used to "Scale" and "Uncscale" an integer to allow infinate control of the PQW output. In my case the FC 105 & 106 already exist in the program. If I try to add either of the FC's from the Standard Library I get a message that they already exist, do I want to overwrite them. The existing FC 105 also has ladder and STL programs written within the block and the STL has syntax errors. I don't know what this logic is performing as all the elements are without labels so I am hesitant to overwrite this logic. Is there any other way to scale an integer to an Analog Output? The integer I have is not large enough to drive the Analog Output. I have tried using MUL_I and MOV to the PQW but the numbers are not accurate enough and I can only multiply by another integer at In2. I will try to add a screen shot of the FC 105, but it is large and I don't know how many sections I can post here. FC105.txt FC105_2.txt

To All, I have resolved my problem with the Analog Output. I didn't take notice that there were already 8 cards in the rack. The analog output I was adding would have been the ninth card. This was not picked up during the hardware configuration because the original programmre did not have the OB for hardware faults installed. I re-programmed my output to another Analog card and it is functioning correctly. THe issue I had with the FC105 & FC106 was resolved by deleting the existing FC's and replacing them with the catalog. The original programmer was using FC105 & FC106 to develop fault messaging to an HMI. This incomplete program was corrupting the SCALE and UNSCALE functions. Thanks to all for your input on this.

I have a nagging problem with OB10. I am using the TOD_INTO to send a reset to a group of counters at the end of each shift. I have configured the OB10 as priority 2, Every Minute, with a start date of 1/01/1994, and the time of day as 00:00. In OB10 I am using SFC1 to read the system clock to temp11, then passing that to FC208. The ret_val of FC208, temp12, is then sent through two compare blocks to test if the time value is between 1380-420, for the third shift, 420-900 for first and 900-1380 for second shift. when the appropriate compare is true it sets an 'M' relay bit, through a one shot that sends a zero to the HMI through a move to a db bit that is read by the HMI. The problem is that I am only getting a zero from the ret_val, temp12. It would seem that FC208 is not processing the time of day, or it is not receiving the data from the SFC1, temp11. I have another program that is doing the same operation, and it works fine. The CPU's are both 6ES7 315-2GA10-0AB0, but the one that works is ver2.6 and the one that doesn't is ver2.0. I also found that the older version CPU does not have "AS A SLAVE" option in the Diagnostics/Clock tab, it only has "AS A MASTER". Could this have a bearing on my problem? Stickman!

I have the ACTIVE check box marked and have performed a warm start when I downloaded the new configuration. I found a quirk in this CPU. The version 2.0 does not have the "AS A SLAVE" option in the Diagnostic/Clock tab on the CPU. The other CPU, with the same catalog number, 6ES7 315-2AG10-0AB0, is a version 2.6. It has this option selected. I am wondering if this has any bearing on my project. Siemens does not have archive information on the older versions.

try this link http://www.used-robots.com/manuals.php?page=xrc-programming_01

FC 105 fault.txt

I have added text files of the STL networks I have in FC105. Both the CALL and END CALL statements are showing as syntax errors. I can't find any other use of FC 105 or FC 106 in hte project. I will try your recommendation, I just hope the other junk in the FC does not interfere with the operation of it. Thanks!