On Saturday 25 February 2017 14:35:16 Gene Heskett wrote: Ping? > Hi all; > > Couple problems with multiswitch. > > Default output for no input is 0001, not 0000. Why? > > Cannot be loadrt'd with the names= option. cfg=4,4 works fine. Why? > I would really like to use the 0000 state as the default, gain=1.0 > position.
Also, the manpage for motion needs updated to reflect that "axis letter of axis" is now "joint.#. of" with a slight change in syntax to numerical. Hooking up to the jog-inputs caught me out for a bit. All this is of course 100% untested because of the way I did the power control. All motor power comes on with the motion.enable button. Not sure if that was the right way, but SSR's beat all them switches when there's not room in that box for the switches. And since I'm doing all this from a sorta comfy office chair and an ssh -Y login, without a camera on the machine, I am not having it do any actual motions for obvious reasons. I need to pull the new apron off, machine it for the dials & pushbuttons, get another piece of that SS pipe across the right side of the saddle to carry this new wiring, and pull the wire I found a couple days ago at Staples in Bridgeport on my way back from a medical appointment, some cat5 "jumper" which is stranded for flexibility, thru all that to actually hook this up. So at the pace I work, and the at least hourly interrupts from the missus, it will be a few days. Ack the manpage, the "parameters" aren't clear to me. First, I'd like to know what happens to the bit line logic progressions when it is asked to decrement to a below zero, aka a - position. Some experimentation may be required. But some clarification of the interaction between writing a u32 or s32 to either parameter, and its effect on the bit.N outputs from the author would be most appreciated. If they track each other that would be great. Humm, I can check that with halshow I believe. Yes. But, while I can read back what I set in the position register, I just spent much of an hour observing the bit.N lines, and only one actually changes its state with a change in position, bit.0 acts as a zero indicator being true if position=0. Any non-zero value written sets bit-0 false which the other 3 bits are and they remain false for any 0-255 value in the position register. A negative written to position is converted to a positive value in a halmeter, so it does not count below zero. Seems to me I either do not understand how to use it, or its broken. In either case, its broken for my use and cannot do this job that I expected it to be able to from the man page. So something is all aglay, me or the manpage? What I wanted was a nibble sized number of bits to drive the sel-0 thru sel-3 lines of a mux16. Help! Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
