electrical Legend automatic population lisp?
That doesn't sound very likely exactly as described, because an AutoLisp function can't start in one drawing and continue in another. But consider another approach such as a text file. It should be possible to make a routine, dedicated to only the Blocks that would go into such a legend, that would check for a Block-listing text file name, if it doesn't exist make it, and write the Block name used as a line in that file. That could be done from any number of different drawings, as long as you don't have more than one User wanting to have it open to write to it at the same time. Then when you're all done [assuming you used only that routine to Insert such Blocks], another routine could open that file, go through the lines containing the Block names, and for each one it hasn't Inserted yet, put one in, with some kind of positional relationship to the last one, such as below it by a defined distance.
Kent Cooper, AIA 
That's a lot of work, considering that most of the time the legend sheets would look the same. Fill out a standard legend sheet (or sheets) with *all* of the standard symbols (leave some space for extras), then add a copy of it to every project.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
@Anonymous wrote:
.... is there a way to take that xlsx sheet and have a route insert the blocks listed into a different sheet?
Yes. Exactly how may depend on the format of that .xlsx file, but if you post a simple one, people can experiment. I haven't used them with AutoCAD, and wonder whether maybe a .csv file would be better -- I'm not sure how many file types AutoLisp's (open) and (read-line) functions can work with, but others here can probably answer that easily.
If this is the only purpose for that file, I would recommend a plain old .txt file, with each Block name on a line, if extracted data can be sent to something like that. That would be quite simple to use to bring them in.
Kent Cooper, AIA
It would be a little more straightforward if it could write them out [in addition to or instead of, as appropriate] a .txt file with only the Block names, not also the drawing file names they come from. But if that's impractical, the format you have can be used -- a routine would have to lop off everything starting with the tab \t character from each line as it goes.
But a question: You have some Blocks that came from being nested in Xrefs [the ones with $0$ in their names] that have the same names except for the source drawing part, such as many of those with names starting with ES. Are those the same, or should they be dealt with separately?
Putting them in would involve an (open) function to get into the .txt file, and a series of (read-line) functions to pull the text of each line, and use of the first part of each line [or all of it, if you make a file with only the names] in Insert commands or (entmake) functions. Those would have to increment the insertion points. Are these things of similar-enough size that one increment-spacing size would space them all appropriately? If not, it could be done by reading each one's bounding box to determine how far to move to put in the next one, but then there's the question of whether their insertion points are in similar positions [all in the middle of Blocks, or some in corners, etc.] -- could get complicated. I think I may have something that deals with that kind of situation, if I can find it. EDIT: It's >>here<<. It does it with all drawings in a folder, but could be adjusted easily enough to use a file like yours instead, assuming the Blocks themselves are all in some place it will be able to find [in the Support File Search Path list].
Kent Cooper, AIA