![]()
Loadrt classicladder_rt numRungs=12 numBits=100 numWords=10 numTimers=10 numMonostables=10 numCounters=10 numPhysInputs=10 numPhysOutputs=10 numArithmExpr=100 numSections=4 numSymbols=200 numS32in=5 numS32out=5 numS32in and numS32out control how many HAL signed integers (+- integer range) pins are available.įor example (you don't need all of these to change just a few): numPhysInputs and numPhysOutputs control how many HAL bit (on/off) pins are available. ![]() Objects of most interest are numPhysInputs, numPhysOutputs, numS32in, and numS32out.Ĭhanging these numbers will change the number of HAL bit pins available. If you do not configure the number of ladder objects Classic Ladder will use the default values. It is possible to configure the number of each type of ladder object while loading the Classic Ladder real time module. If the scan time is longer than one millisecond you may want to shorten the ladder or put it in a slower thread. The current scan time will be displayed on the section display, it is rounded to microseconds. #Usb block 1.7.1 registration code update#If you put it in a slower then one microsecond thread then Classic Ladder will update the rungs slower. You can put it in a faster thread but it will not update any faster. The fastest that Classic Ladder can update the rungs is one millisecond. If you can turn a switch on and off faster than Classic Ladder can notice it then you may need to speed up the thread. The speed of the thread that Classic Ladder is running in directly effects the responsiveness to inputs and outputs. This line makes Classic Ladder update at the servo thread rate.Īddf classicladder.0.refresh servo-thread The second line adds the function classicladder.0.refresh to the servo thread. ![]() The first line loads real time the Classic Ladder module. Loading the Classic Ladder real time module (classicladder_rt) is possible from a hal file, or directly using a halcmd instruction. Ladder files (.clp) must not contain any blank spaces in the name. These must not be placed in the custom_postgui.hal file or the Ladder Editor menu will be grayed out. Typically classic ladder components are placed in the custom.hal file if your working from a Stepconf generated configuration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |