Is there a way to change the photometric file of a defined luminaire to a new photometric file without having to redefine or add a new luminaire? It would be nice if I could define the luminaire using a photometric file...let's say an exterior area luminaire with a type III distribution, and swap out just the photometric file with a new type IV distribution without having to load and define an entire new luminaire. Is that possible?
I think the answer is a partial 'yes' on this one, Jill, but there are gotchas depending on the situation.
Firstly, I'll run you through how it's possible (although for this method to work you can't have any of the fixtures in question on a Frozen project - AGi32 won't allow you to run a calculation, freeze the results, and then change the luminaire type that you've used in that calc), then expand on some concepts from there.
Steps to take:
Cool. I just posted a fairly detailed answer and it disappeared when I posted it.
I can't re-write it all (sorry), but in a nutshell, when you select your new photometric, use the 'Label' of the fixture you're replacing.
AGi32 will unfortunately overwrite most of your old information, but a couple of minor timesavers are:
Is there a real answer to this question???????
What's not real about the answers I gave, Miketrol?
By the way, Flo, nice forum name. Now I'm just waiting to see if Al Eedee turns up here.
I have been searching the forums for a similar answer - dealing with emergency egress lighting. While our state does not require a submittal for code, we typically do them to calculate that we have met the requirements. That said, I would like to alter a few lights that are on emergency battery backup with a lower lumen output. I was looking for a way to modify/copy the existing luminaire and decrease the lumen output, but I cannot. I altered the wattage to see if it would calculate the lumen output accordingly, but it doesn't. Any way around this?
To be honest, it sounds like there's some conflicting information there. You do a calculation to confirm that you've met 'the requirements', even though you do not require a 'submittal for code'. Here in Australia, the methods by which you confirm compliance are very explicitly defined, although I don't assume that is the same for every location around the world.
If your emergency lighting codes are strictly defined, then you should follow their approved methodology - anything else is pure supposition. For example, I could not comply with our emergency lighting standard via the method you're trying to use; how do you know what your lower lumen output is unless you have a proper test report? If you don't know for certain, then all bets are off. If, however, there's some information that you have where you know for certain what your emergency lighting lumen output is from your fixture, and you can't change the fixture lumens (assuming you're struggling with an 'absolute' file where the lumens are 'locked' in AGi32), then aside from actually modifying the IES file your only other avenue is to use the Total LLF text box, or preferably the click on the 'Specify...' button and put your normal depreciation factors in but them also add the reduction factor for emergency in the 'User Defined Factor' box.
Remember that these factors are decimal values from 0 to 1, so assuming your emergency lighting lumen output is something low like 8% of the original lumens, you'd but 0.08 in the User Defined Factor box.
I should clarify something - when I said I couldn't comply with the local requirements here via your method, I'm saying that because it sounds like you're using a bit of guesswork on the reduced lumens.
In the past here we would get emergency classification codes for our fixtures that we could use with tables to determine spacings of fixtures. In the last decade or two it's more common to also receive IES files for the emergency fixture where we can do lighting calculations with the tested reduced lumen output fixture, so we never have to mess around with the file - it's a known entity.
Thank you! I have the lumen output from the specifications, but not an .ies file for that output, which would make life so much easier. I will try the user defined factor as you explained.