Messages

5291

General Mach Discussion / Re: Macros And Buttons - Strangeness Abounds....

« on: August 26, 2011, 12:28:00 PM »

Guys after careful thought I believe that the current macro/CB system is a blessing AND a curse. Not many other controllers GIVE the OP this much POWER and flexability. That could be GOOD and that could be BAD.

I can SEE the NEED for both systems Mcode and CBmacro . I have moved all motion Mcodes that I could over to SUBprograms BUT it has problems as well (;-).

I think the only GOOD solution to this is to patch it up as best as can be done . THEN it will be what it will be. I fear any attempt at a major retrofit will just BUST everything in a backwards compatability manner and do little to make it better.

SO maybe the new MACHv4 can start fresh and provide a Mcode enviroment AND A SEPERATE CBmacro enviroment. That way we still have the best of each world.

Just a thought(;-) TP

5292

VB and the development of wizards / Re: Button with two functions

« on: August 25, 2011, 08:21:02 PM »

SOmething along these lines may work,  I have seen a better example on here somewhere.


Sub Main()
If OemTrigger1 And GetVar(1000)< 1 Then GoTo N2
If OemTrigger1 And GetVar(1000)> 0 Then GoTo N3
GoTo N4

N2:
ActivateSignal(output5)
SetVar(1000,1)
GoTo N4

N3:
DeactivateSignal(output5)
SetVar(1000,0)
GoTo N4

N4:
End Sub
End


OR maybe something like this

If OemTrigger1 And GetVar(1000)<1 Then                
   ActivateSignal(output5)
   SetVar(1000,1)                              '
  End If                                        

  If OemTrigger1 And GetVar(1000)>0 Then                '
   ActivateSignal(output5)
   SetVar(1000,0)                              
  End If        
  
  End

Hope it helps, (;-) TP

5293

Third party software and hardware support forums. / Re: USB TO PARALLEL

« on: August 25, 2011, 04:18:43 PM »

USB to parallel will NOT work. It must be a true LPT port. Either onboard, PCI card or PCMCIA .

Hope that helps, (;-) TP

5294

General Mach Discussion / Mach Programer's manual

« on: August 24, 2011, 09:04:15 PM »

This is a request for an addition to the Mach programmers manual.  The LED,DRO,and Button list were a nice addition. Would it be possible to have a second listing based on the functions being in aphabetical order. It would make a search for a specific function much easier sometimes.

Thank You, (:-) TP

5295

General Mach Discussion / Re: cutting problems

« on: August 24, 2011, 06:28:56 PM »

Is the tool you specific in Cut2d the exact same diam as the tool you are cutting with?? That is the only reason for a spur left uncut that Ican think of.

(;-) TP

5296

General Mach Discussion / Re: Adding audible alarm to Mach 3 thru HobbyCNC board...

« on: August 23, 2011, 09:47:22 PM »

You are correct so far(;-) The active low needs to be the RED X that will make it active High.

You can test this on the diagnostic page. There is a LED that shows the state of the enable1 output pin.

When Mach is normal the led should be ON and when you put it into reset it should go OFF.

Remember on the alarm side of the relayy when you wire it up PLAN to put a disconnect switch inline to be able to shut off this function. IF not then when you first fire up the system the alarm will turn on untill you come out of RESET and when you shut it down the alarm will ALSO turn on.

(;-) TP

5297

General Mach Discussion / Re: Adding audible alarm to Mach 3 thru HobbyCNC board...

« on: August 23, 2011, 09:02:50 PM »

Well if all else fails there is always the USB way to drive the relays(;-)

(;-) TP

5298

General Mach Discussion / Re: Macros And Buttons - Strangeness Abounds....

« on: August 23, 2011, 08:58:13 PM »

HiGuys, First off let me say how MUCH I appreciate both of you. By following your examples of code AND by you SHARING it with us I have been able to work in CB ( Cypress Basic) and do things I have NOT been able to master over the years.

I am missing the programmers LOGIC gene from my DNA. I can get lost in the simplest loop of code. Thru both of you and others I have developed a library of code functions that I use over and over again in various applications. There are things I do that take days to make work that you could do in 5 minutes. BUT I do get it worked out.

Also A thousand thanks to ALL that worked on the Mach Programmers Bible. IT is something to be proud of. PS there are a few more things I have found that need to be added.

Brian you got to know I love ya buddy who else would put up with us. Well Art did till we drove him crazy(;-)

SO I will climb off the box now and let it be.

(;-) TP

5299

General Mach Discussion / Re: Macros And Buttons - Strangeness Abounds....

« on: August 23, 2011, 03:13:16 PM »

HIYA IAN, Are you picking on me again?  (;-) LOLOLOL

OK I am taking the stand for the CNC MACHINIST and no one else that uses MACh3 for whatever motion control. This is not for CB applications not pertaining to actual CNC machine use.  I have very little problem using the CB for creating OTHER stuff it works very well

I need a Macro system for Mcodes that BEHAVES exactly like Gcode does.  Run it live , run it from a buffer, run it from down the street, I don't care. BUT MAKE it behave as Gcode does. Simple and 1 line at a time execution if required. IF it takes adding in a header to identify it as a Mcode that is ok too. Use # parms or named Parms I don't care. Just provide a LIST of the params. Think MacroB here, it is not always pretty but darn it it works 99.99999% of the time.

 I  AM a cnc machinist NOT an ADVANCED system programmer. I should NOT have to learn a new Advanced programming language just to be able to create and use a Mcode to do my work.  The basic conditionals + params + math will work just fine.

Thank You, End of rant (;-) TP

5300

General Mach Discussion / Re: Macros And Buttons - Strangeness Abounds....

« on: August 23, 2011, 01:24:05 PM »

HIYA RAY one thing to please remember to fix. In a Mcode that contains CB and code"Gcode motion code" MIX  It is imperative that the macro stays in SIMPLE order of execution WITHOUT having to resort to extra wait states,symaphores and such. That means FIXING While Ismoving(), Isloading, etc so they WORK 100% without fail. I suggested a new function a while back.
SusWhileDo() that could be a big help.

Multithreading is Great but NOT if you cannot control it. With motion codes it MUST behave as it is a huge SAFTEY concern.

Good Luck, (;-)TP