Messages

1

Mach4 Plugins / Re: Mach4 Plugin-Development

« on: March 15, 2017, 04:41:36 AM »

I learned you have to sign a non disclosure agreement with newfangled Solutions to get the SDK and documentation.

By the moment I'm waiting for it ;-)

2

Mach4 Plugins / Mach4 Plugin-Development

« on: March 08, 2017, 07:35:48 AM »

Hi,

i have some Plugins developped for Mach3. I would like to do the transfer to Mach4 with starting to port the plugins.

How can I get a development tutorial or documentation? Couldn't find anything yet.

best regards,

Steffen

3

Mach SDK plugin questions and answers. / Re: Plugin Access to GCode Window

« on: January 21, 2012, 10:34:15 AM »

You mentioned to call VBA from Plugins, he didn't

So I have no idea why you mentioned, HE wanted to do something like that

Anyway, Mach3 gives lots of ways to add features by Plugins, VBA and operations.
It's the programmers chance to use any of them.

Steffen

4

Mach SDK plugin questions and answers. / Re: Plugin Access to GCode Window

« on: January 21, 2012, 10:15:38 AM »

Huh? I do not understand?

He didn't want anything like that...

Steffen

5

Mach SDK plugin questions and answers. / Re: Plugin Access to GCode Window

« on: January 19, 2012, 09:26:02 PM »

Also correct, you can do that.

But I have no idea, why you should use parts of your code back to this Basic-side, when you know how to code in Plugins.
Maybe to have user-changeable parts, but when there is no need for this, it is strange to go back into vba.

I also do not see, where VBA is simpler for people who already have plugins.

Steffen

6

Mach SDK plugin questions and answers. / Re: Plugin Access to GCode Window

« on: January 19, 2012, 10:06:58 AM »

You're right, but he wants to see the G-Code in the gcode window and the path preview.

This is only possible with loaded G-Code files, as far as I know.

Steffen

7

Mach SDK plugin questions and answers. / Re: Trouble saving plugin cfg from Plugins Control menu

« on: January 12, 2012, 02:06:41 PM »

Hi,

my honest opinion? You don't do anything wrong, it's Mach3's sometimes strange behaviour 

I do write the parameters to the XML during the DLL call StopPlug. Then they are in the XML.

best regards,

Steffen

8

Mach SDK plugin questions and answers. / Re: Plugin Access to GCode Window

« on: January 12, 2012, 02:01:17 PM »

I used BCX, this does the most stuff.

String concatenation had to be changed from VBA to C:

Code "G90G53G0Z" & PositionZ

to

Code(Format("G90G53G0Z%f", PositionZ));

then indent with my favorite settings:

indent -ts2 -npsl -bad -bap -bl -bli0 -di10 -bc -lp -l200 <filename>

Then of course the changes to better coding with the methods of C++ 

9

Mach SDK plugin questions and answers. / Re: Plugin Access to GCode Window

« on: January 12, 2012, 12:43:39 PM »

Hi,

I don't think there is a way to write code to the codebuffer of Mach3.

But you can write to a teachfile as you can do it with your wizards.
Generally spoken, you can do everything in a plugin what you do in a script, and something more 
So I have moved some bigger VBA-Skripts to a plugin just by a VBA to C converter and a little handwork.

Code: [Select]


  scripter.OpenTeachFile("teachtest.nc");

  // some sample code for the teachfile
  scripter.Code("G0X100Y100");
  scripter.Code("G1Z-10");
  scripter.Code("G1Z0");
  scripter.Code("G0X0Y0");

  // finish and load it
  scripter.CloseTeachFile();
  scripter.LoadTeachFile();

just tested this code, but I'm not working with the VS2008 wizard, I'm with VS 2003

regards,

Steffen

10

Mach SDK plugin questions and answers. / Re: Notify plugin or have plugin detect when OEM Button is pushed

« on: December 06, 2011, 08:34:40 PM »

Hi,

I would like to know the same.
It would be nice to have a handler for OEM-Buttons, that are unknown to Mach3, but I didn't find anything yet. The advantage over the actual method is, that there is no vba involved.

A working way to call Plugins from Mach3-Buttons is to have a Button with a vba-script, that calls a function in the DLL:

Code: [Select]

Declare Sub CallDLLFunc Lib "MyPlugin" (ByVal Parameter1 As Double)

Call CallDLLFunc (1.234)
and then the plugin has to have the function exported:

Code: [Select]

EXTERN_C DLLEXPORT void CallDLLFunc(double whatever)
{
  // Do something
}
Steffen