Graeme Foot <graeme.f...@touchcut.com> writes: > I agree that EtherCAT is dynamic in that it allows Hot Plugging of > modules. But every time a module is added or removed the system is > rescanned, all slaves are put into PREOP, Distributed clocks delays > are recalculated etc then all configured slaves put back into OP. > > So although you can dynamically plug in modules at any time, your > application first of all needs to configure expected modules, and if > they exist know what to do with them. So at some point your > application needs to know all possible modules that could be plugged > in. (EoE modules are slightly different though in that they also work > in PREOP.) > > You say you don't use aliases on your EoE modules, but do you use > aliases on the rest? (or at least the couplers?) If not how do you > know what is currently plugged in?
I think most projects here currently do not use alias. They probably should do that for our couplers. But that does not change that I believe that etherlabmaster should fully support systems that does not use alias. /Esben _______________________________________________ etherlab-dev mailing list etherlab-dev@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-dev
