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

Library Help Plez

11/9/2010 3:47 PM	Rate (0)
michaelgmyers Posts: 7 Rating: (0)	Ok guys heres my problem. I was under the impression that I would be able to make a [FC] then add to my library and use when ever I needed the block. I built a [FC] that simply turns on/off output based on 4-20 ma. I then draged this to my library, because I have several 4--20 instruments that protect a pump I was hoping to drag the element as many times as needed for each instrument Even though the block gets renamed everytime I use it, I get ambigious address when I compile and download. I will attach a small sample file. Thanks all Attachment ANALOG TEST STATION.zip (730 Downloads)
michaelgmyers Posts: 7 Rating: (0)
Suggestion To thank Quote Answer

11/9/2010 4:42 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 11/18/2024 Posts: 15406 Rating: (2446)	I agree the library (both project and global) work needs more work to explain how to use! To address the ambiguous problem, go renumber each instance of the library block you created so they are uniquely numbered. For example, create a new FC, see what the id number is, delete the FC, assign that number to one of your library block FCs. Create another new FC, see what the next id # is, delete that FC (actually, just cancel creating it), assign that number to the next library block FC. Iterate this process until all library block FCs have a unique id number. Compile, and load.
	science guy
Suggestion To thank Quote Answer

11/9/2010 5:00 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 11/18/2024 Posts: 15406 Rating: (2446)	After opening up the program in TIA, I see you have SCALED_ANALOG_TRIGGER & SCALED_ANALOG_TRIGGER_1 both set as FB1. That is not going to work. Set properties of SCALED_ANALOG_TRIGGER_1 to FB2 (FB, number 2). Then update your block call of SCALED_ANALOG_TRIGGER_1 and it will compile.
	science guy
Suggestion To thank Quote Answer

11/9/2010 5:24 PM	Rate (0)
michaelgmyers Posts: 7 Rating: (0)	huggy_d1 Thanks that worked great. Also thanks for the quick reply
michaelgmyers Posts: 7 Rating: (0)
Suggestion To thank Quote Answer

11/9/2010 10:39 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 11/18/2024 Posts: 15406 Rating: (2446)	Glad it worked out! One thing I noticed.. I think you have wire break / overrun detection enabled. I didn't see any diagnostic error interrupt routine (OB82) to handle those errors. What will happen is if you have an overrun condition, the PLC will STOP. Same for a wire break. If you uncheck those hardware detection boxes, you will not have that problem. In another thread on these forums, I show screen shots of diagnostic error handler logic which may prevent the PLC from going into STOP mode on hardware faults. Good luck!
	science guy
Suggestion To thank Quote Answer

Share this page:

Share this page on...