Hello Guest it is April 19, 2024, 10:11:06 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - poppabear

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 »
1
PoppaBear here just saying hi, been a while, been poking around with 3d printing.
Been gone to the dark side for a while, considering running a 3D printer (industrial grade),
with a Mach4 head. Been a lot of changes since been gone.
Hope you guys are all doing well.

Scott

2
Does anyone have a "Firmware" (post processor) file for Simplify3D to Mach4?

Thanks in advance.

3
Anybody got a lead on where I can get a table top size CNC router no control?

I have a NEMA 23, 3 axis stepper system already.

I am looking for a Small "Table Top" (perhaps max of 2'x4') CNC ready router (not the flimsy ones).
that would already have the ball screws. It can or cannot (I could take or leave the fact that it does
not have a spindle motor) have a VFD spindle motor.

I basically want to get the mechanical CNC ready router, and just hand my control on it for my son for Christmas.
I have seen a few CNC routers on Ebay (mostly the Chinese OEMs), but they all have control systems.

Anyone got a link or advice it would be appreciated.

Scott

4
Mach4 General Discussion / LOVING the PMC!! Thanks Steve!!!
« on: July 03, 2016, 09:54:29 AM »
LOVING the PMC!! Thanks Steve!!!

Scott

5
Lua scripting manual has been removed, use the Mach4 API help file.

The "Mach4CoreAPI.chm" is located here in your Mach4 install folder:

YourDriveLetter:\Mach4Hobby\Docs\Mach4CoreAPI.chm

The help file is UP TO DATE per release of Mach4, there have been many, many changes since the scripting manual was done, and it is now been depreciated and its thread removed to not cause confusion to new (or existing) users.

Scott

6
Here is the latest Parameters, understanding work offsets, and Enum list for using mcLua calls.

Scott

7
Well, trying to port over the plugin I did for Pete's MP-03 modbus pendant to a wxLua Wizard and screen integration for Mach4.
It can do:
MPG, Cycle Start, Estop, FSOVR, Spindle On/Off via buttons, and
27 control functions via Soft buttons, that the user can custom assign,
Plus fire off 15 macros (user or OEM), and optionally map inputs to screenset "Leds" for monitoring or other purposes.

see screen shots of wxLua Pendant config notebook.

Scott

8
When you are in the mcLua scripter, and you want to launch the "Help" (CHM) file for the mc.mc*********x call you wanting to know about.
Put your cursor to the Right of the "Dot" after the second "mc", i.e.  "|" represents the cursor:

mc.mc|*********xx
(see attached screen shot, of cursor position)

then hit the "F1" key this will bring up the CHM file already at the name of the mc.mc call you are on.
NOTE: you will have to have the full name of the mc call typed out.
This will bring up the CHM help file already on the page that has that call defined and explained.

BUT..........

On Windows 8.x (at least on my dev laptop), if you hit "F1" this brings up the Windows Help file instead.
The solution is to turn off the "F1" key from launching Windows Help.

To do that:

  • During reboot hold down “Esc” key, or, what ever key your comp needs to get to the BIOS
  • In the BIOS, go to system->Action Keys and disable them, then F10

Now when you do the above, "F1" will now launch the CHM file from the mcLua scripter.

Scott






9
Here is the current list of working (and recommended) scr.calls...
NOTE: The Button click, down, up, and mdiexe calls do work but they have all been
replaced by newer/better ways to get-to/do those things. So, those calls are NOT shown here.
You can place this code into you lua scripter and put a stop debug break point on each line,
to see how it works and you can mouse over the returned values.

Code: [Select]
function test()
    local mInst         = 0;
    local inst          = mc.mcGetInstance(mInst);
    local NumValue      = 0;
    local StringValue   = "";
    local BoolValue     = false;
 
    --Goto a Page, ("Default" in the wxMach set is the only page at this time),
--it is considered page "0", all after that would be 1, ...
    scr.ShowPage("Default");--"PageName"     

    --Get the Button Up color property, i.e. "Green"(hex value) of the enable button
    StringValue = scr.GetProperty("tbutton2", "Button Color Up");--"ControlName", "PropertyName"
    --Set the blink rate of the up state of enable button to 250
    scr.SetProperty("tbutton2", "Blink Rate Up", "250");--"ControlName", "PropertyName", "Value"
    --Set the blink rate of the up state of enable button back to 500
    scr.SetProperty("tbutton2", "Blink Rate Up", "500");--"ControlName", "PropertyName", "Value"

    --Get the current "Page" number that your on 0 to ##
    StringValue = scr.GetCurrentPage();--no param
    --Does the named control exist in the set (True)?
    BoolValue   = scr.IsControl("tbutton2");--"ControlName"
    --Does the Property of the named control exist (false)?
    BoolValue   = scr.IsProperty("tbutton2", "CrashAll");--"ControlName", "PropertyName" 

--[[
NOTE: scr.ButtonClick, ButtonDown, ButtonUp, ExecMdi; These calls STILL work, BUT!!!! Steve says that
they are the MUCH outdated and older way, and ONLY kept for compatibility for some dark age Mach4 screens.....
These types of functions have all been replaced by mc.calls, or get/set properties... in other words
Use the newer, easier to use stuff!!!
--]]
end

if (mc.mcInEditor() == 1) then
    test();
end

PS. Thanks to Steve Murphy, for the heads up on the old stuff!! And help in general,

Scott

10
Mach4 Toolbox / Quicky Wizard and/or Macro variable value viewer function.
« on: February 23, 2015, 03:45:49 PM »
This is a simple Variable value displaying function, that you can display the
values of your variable that are in you Wizard or Macro as they occur.
it will default to a wxMessageBox display or optional MachErr.

The wxMessagebox is used since it is modal, and "stops"
    the program from continuing till you click the OK button.
    The wxMessageBox is the default behaviour, but you can add
    an optional "1" as a third parameter which will send it to
    Mach Error, which is NOT model. So, if you have this function
    in a series it will log to the error history box, but only the
    last error will show in the Mach error.

    Params:
        1st Param is the Variables Name as a String, i.e. myvar would be "myvar".
        2cd Param is the Variable itself, i.e. you would put myvar as param #2.
        3rd Param is optional, and if a 1 is used, will send the data to Mach Err,
        if there is nothing for a 3rd param or other than 1 it will default to
        display in the wxMessageBox.
        NOTE: The wxMessageBox will sometimes appear BEHIND your Mach 4 window!

the .mcs file is setup as a Macro for your testing to see how it works.

Happy Debugging,

Scott

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 »