#1
|
|||
|
|||
auto zero with limited inputs
Is it possible to get all the push buttons, proximity sensors and a zero probe to all work with just one BoB??
Pin 10 - Emergency Stop Pin 11 - Start Pin 12 - Pause Pin 13 - Auto Zero Pin 15 - Proximity Sensors Pin ?? - Probe I was thinking (Something I probably shouldn't do) if there was a way to have pin 13 (Auto Zero) trigger a macro that could temporarily disable one of the buttons so the probe could use that particular input, ie pushing auto zero disables the the start circuit and lets the probe use pin 11 until the zero routine is finished, then it goes back to normal once the machine completes the routine. Don't know how to go about it though. Maybe someone could slap some reality into me, or help me figure this out. I am gonna cross post this over on the Mach forums too. Thanks, John |
#2
|
|||
|
|||
John, why can't you just use Pin 13 for both the Auto Zero and the Probe? Surely, you won't be using both at the same time.
|
#3
|
|||
|
|||
Problem is if pin 13 is set to start the macro, wont it start it again when the probe makes contact if the same pin is used. Unless the macro disables the button press). Which is sorta what I am getting at, I just used the start button as an example.
|
#4
|
|||
|
|||
Start what Macro? Oh, maybe you're seeing AutoZero as a button to start the zeroing sequence? I'm thinking of it as a Z Zero sensor used during the zeroing sequence.
I think you'll find that you don't do the zero sequence often enough to warrant a dedicated button. |
#5
|
|||
|
|||
Dang cell phones, accidently replied to brad or the iternet gods via email instead of here. Apologies if I sounded rude, that wasn't the intention, as I appreciate all the help I can get.
Now for the reply!! Then what the heck is the third button on the y-car for?? Seems to me no matter wether it is used to start the zero routine or something else, we still run into the problem of limited inputs with one BoB. In any effect, I would like to use it to trigger the zero routine as my keyboard isnt right at the machine, and I like to watch it up close |
#6
|
|||
|
|||
John,
I have set up the Z-zero routine and probe on the same pin with a macro. I think it was Greolt that published the script, but it essentially let the probe be a single 1 shot input, while initializing the routine was a 3 second hold. So, since I confused myself, it works like this. *I wired the probe and button in parallel to the pin 13 on my machine* push button for 1 second...sets zero where your at, or where the probe touched push button and HOLD for 3 seconds, intialized routine to start and then waited for a quick 1 second touch from EITHER the button or probe. This let you "escape" from the routine if your not ready. IT was a really nice macro. I don't have the file anymore since my machine #5 is gone, but did work. I was set up for: Pin 10 - Emergency Stop Pin 11 - Start Pin 12 - Pause Pin 13 - Auto Zero / probe Pin 15 - Proximity Sensors (all run in series thru relays) Per the autocad drawing file I just found on my old laptop. Good luck. Sean Last edited by smreish; Wed 04 August 2010 at 13:45.. Reason: I spell like a kiddy. |
#7
|
|||
|
|||
Cool, hopefully he chimes in with the macro
|
#8
|
|||
|
|||
John
I think Sean is talking about a macro that he wrote. Not the one I put up a couple of years ago. http://www.mechmate.com/forums/showt...0&postcount=69 Greg |
#9
|
|||
|
|||
That is a real bummer, hopefully we can solve this problem again, since he no longer has the script!!
|
#10
|
|||
|
|||
If you really want to maximize signals, use some binary logic. With three inputs, you have eight possibilities (really only seven because you'll need an "off" state).
Assuming that you have three N/O switches: 000 = all inactive 001 = function 1 active 010 = function 2 active 011 = function 3 active 100 = function 4 active 101 = function 5 active 110 = function 6 active 111 = function 7 active Having four switches would give you fifteen usable routines. Five switches would gie you thirty-one usable routines, and so forth. Add a delay routine so that you have a second or so before the inputs are judged to be stable, then branch based on which switches are active. |
#11
|
|||
|
|||
Why you gotta hurt my brain, Mike. That is a bit more than what I need
|
#12
|
|||
|
|||
Or, if you just need an extra function or two, a toggle over the pushbutton will give two functions for the one button. Toggle left is function 1 and toggle right is function 2. Use a three position toggle for an extra function (middle position). You could also use a locking toggle so that it does not get bumped when you don't want it to.
|
#13
|
|||
|
|||
...Mike,
I was SO tempted to go there on my discussion. I'm glad you did and not me...I'm not that smart. LOL |
#14
|
|||
|
|||
Actually the toggle doesn't seem like a bad idea!!
|
#15
|
|||
|
|||
The problem with my idea is that it requires a macro that treats a group of input signals as a single entity. It also requires a macro that can handle a time delay. I've done very little programming in Mach, so I really have no idea whether such a macro is even possible. I assume that it would be possible, but it might take more effort than it would be worth.
An alternative approach is to use multiple parallel ports. The I/O pins would still be limited, but you might have enough I/O to do the job without resorting to writing custom code. I've been playing with EMC2 and Linux. It looks interesting, but I dread the learning curve. At my age, I'm never sure that I'll live long enough to understand anything new. |
#16
|
|||
|
|||
I woulda gone with another parallel port, but i am running a itx computer for this machine, so no room for it. Sean says it is possible to do what i would like to, and has even done it, but for now I will just use a toggle switch on the bin and work on a more elegant solution from there.
|
#17
|
|||
|
|||
Okay, now I'm really confused. I thought the issue is that we had more buttons than available inputs. How does adding a toggle switch (another input, or two if it has three positions) help solve the not enough inputs problem?
I've cut this board three times already, and it's still too short! Sean's macro description is to double up the functions of an existing input. |
#18
|
|||
|
|||
Brad,
Sorry, my post was confusing. I was just proposing using a toggle switch (or Switches) to select the binary coding that Mike had suggested. The pushbutton would then just send the binary code to the breakout board. Then there would be no need for the delay routine. |
#19
|
|||
|
|||
Heath, help me understand the practical implementation of that.
Would you have three toggle switches, one for each of the binary digits, and then a single button for all functions? I can see how you might use a number of diodes, or a small logic board in order to have the buttons themselves trigger combinations of inputs, and thus be able to process up to seven buttons with three inputs. I can see a similar technique to allow three buttons with two inputs. But I can't see how one button and a toggle switch can ever consume fewer than two inputs. Two other silly ideas to toss out while we're at it: If you had an analog input, you could use different voltage levels (resistor values) to distinguish buttons. Or, if you have a serial port on the machine, you could use the CarrierDetect, DataSetReady, ClearToSend, and RingIndicator for four more inputs - and DTR and RTS for two more outputs. That's assuming somebody can couple it up to Mach3. |
#20
|
|||
|
|||
Actually, you are correct a toggle switch wont work, since both items are still going to the same pin, either one would still trigger the event. Sean's solution is still the correct one, so I am gonna have to try to either research the heck out of it (mach board is telling me to buy another parallel board) or reinvent the wheel since the macro was apparently lost with machine #5
|
#21
|
|||
|
|||
Brad,
You are right, the toggles just set up the binary input and the pushbutton is just a "send". You would not need the delay routine. My first post did not come out right and gave the wrong idea. You would need to use two inputs min. I just thought the macro would be easier to write and easier for the operator if they could just input the code and then press send. You could also use a rotary switch for the selector as well. Sorry if I confused the situation. |
#22
|
|||
|
|||
Next up, Mach3 macros that understand Morse Code!
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Tilting or hide-away MM? limited floor space | Mike94531 | General - MM Build | 49 | Sat 13 March 2010 03:39 |
Auto Tool Changer | WTI | 50. Toolheads | 38 | Mon 14 December 2009 12:30 |
Auto Toroid Winder | WTI | 702. Power Supplies | 0 | Sat 20 June 2009 19:03 |
Toggling inputs - faulty Campbell BoB | Alan_c | Troubleshooting | 15 | Mon 08 December 2008 10:30 |
Ipac - many extra Mach inputs via the keyboard port | Gerald D | 70. Control Systems | 2 | Thu 21 February 2008 05:06 |