Chris Morley wrote: > Hi Guys > > Looking for opinions on Classicladder ver 7.124 in TRUNK: > > Keeping in mind EMC 2.3 it's acceptable to break configs: > > CL V7.124 has slightly different timers that require a small > change in the ladder program to work the same (you must > connect two ladder pins together). This allows added features > to the timer. Right now I force the added pin to act connected > But would prefer not to do that-one less thing to change > from main stream CL and you lose the added features.
Again, as long as it's documented, it should be fine. Of course it's better to have an automated tool to convert for you, but that's just gravy on top of documentation. > CL V7.124 defaults to 15 each of hal in/out pins while > CL V7.100 had 50 each. To me 100 pins adds a lot of > clutter but any existing config that uses more then 15 > pins needs a change. As long as the changes to defaults are documented (in the "moving from 2.2.x to 2.3.0 doc, once it's written :) ), I don't see a problem with changing the defaults. > There are lots of changes from V7.100, and lots of work > on the serial MODBUS routines. > any comments would be appreciated. Question about MODBUS: I haven't looked at the CL modbus code, but would it make sense to put the modbus stuff into a separate driver (at least for master mode, where CL is getting info from slaves), and connect it via HAL? - Steve ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
