Thanks for sharing. How did manage to put on the left side vertical the shortcuts for line, poyline, text, etc...I tried to snap it to that side but it only stays in float mode
Where is the limit for symbol macro, when I should save it like *.ema instead of *.ems and vice-versa? For example I have a black box with several sockets, optionaly inserted circutis inside the black box, but the only part number. Or may be it would be not worse to make only *.ema everytime, but never *.ems or vice versa?
I use ems for only one symbol, I use ema for any component, black box or circuit.. But really it is your decision. Historically it had a specific meaning now they react very similar.
Please advise, How to generate the terminal diagram report for distribution terminal as these terminals are used in different locations with same DT and different connection point designation.
Please contact your EPLAN support team. This RUclips channel is not intended for EPLAN support. The solution is easier to answer for them. If they cannot answer, contact the Canadian EPLAN Team.
Why is this? I believe that very often a special block is required (I am taking the users language) and in deed I can create a symbol macro. I understand macros are much more when you start using them as complete circuits, with placeholder and maybe even Cogineer or eBuild. But at the basic it started as symbols macros. So yes this is the 101 of a symbol macro. Sorry to argue. I hope this help users not to make the mistake of changing symbols which can become quickly very tricky and incompatible to the rest of your projects. The block represented by a symbol macros will be compatible years and years to come.
Thanks for sharing. How did manage to put on the left side vertical the shortcuts for line, poyline, text, etc...I tried to snap it to that side but it only stays in float mode
Glad it helped! I am already with the version 2022...
Where is the limit for symbol macro, when I should save it like *.ema instead of *.ems and vice-versa? For example I have a black box with several sockets, optionaly inserted circutis inside the black box, but the only part number. Or may be it would be not worse to make only *.ema everytime, but never *.ems or vice versa?
I use ems for only one symbol, I use ema for any component, black box or circuit.. But really it is your decision. Historically it had a specific meaning now they react very similar.
@@rolandyounk6169 thank you!
thank you, from Istanbul.........
These macros / symbols will outlast every change in symbol files. This is the best way to keep your EPLAN customizing up for years to come.
Roland
Please advise, How to generate the terminal diagram report
for distribution terminal as these terminals are used in different locations
with same DT and different connection point designation.
Please contact your EPLAN support team. This RUclips channel is not intended for EPLAN support. The solution is easier to answer for them. If they cannot answer, contact the Canadian EPLAN Team.
This has nothing to do with macros..
Why is this? I believe that very often a special block is required (I am taking the users language) and in deed I can create a symbol macro. I understand macros are much more when you start using them as complete circuits, with placeholder and maybe even Cogineer or eBuild. But at the basic it started as symbols macros. So yes this is the 101 of a symbol macro. Sorry to argue. I hope this help users not to make the mistake of changing symbols which can become quickly very tricky and incompatible to the rest of your projects. The block represented by a symbol macros will be compatible years and years to come.