Hello Guest it is April 29, 2024, 06:12:31 AM

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.


Messages - django013

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 »
41
Mach4 General Discussion / crash on starting edit mode
« on: January 17, 2018, 08:25:00 AM »
Hi,

I haven't run m4 for long time. As I noticed a new release, I thought give it a try ...
First problem was an unfinished lua panel - wich I removed completely.

Now m4 starts without errors, but as soon as I enter screen edit mode, it crashes.
I have several crash reports, but I don't see any hint, where I should look for an error.

best regards

Reinhard

42
Hi,

the picture before the last one from the second post shows your "problem":
Quote
Enabled = No
So you first have to enable the plugin. Then you can select it as the motion device :)

hth Reinhard

43
Hi,

what about your error about unwritable memory? That can't be related to a forgotten Show()
For me that error looked like a threading issue.
How did you solved that error?

44
So you created a lua dialog from a mach4-screen button?
Duh - didn't know that that would be possible. Good to know ;)

45
Mach4 Toolbox / Re: A new Tool Table for Mach4
« on: June 11, 2017, 12:37:10 AM »
I was working on a tooltable inside mach4 (i wanted to avoid popping dialogs) and wanted to add the cutlength of a flute to the tool table.
So from main menu of mach4 enter "view->tool table", which opens the mach4 tool table dialog.
From there go to "Edit -> Table Fields", which opens another dialog with a notebook control.
Last tab to the right is called "User Fields".
There you can add fields to the tool table.

To retrieve the values from lua there's a mach4-API that takes a fieldname as parameter:
Code: [Select]
mc.mcToolGetDataExInt(inst, toolNumber, userdefinedFieldname)That API has variants for Double and String too, so straight forward :)

See attached picture of my tool table tab page. Column "SL" is a user defined field from mach4 tool table and I don't have to care about storage :)

hth Reinhard



46
Mach4 Toolbox / Re: A new Tool Table for Mach4
« on: June 10, 2017, 11:39:39 PM »
with current mach4 it is possible, to extend mach4 tool table, instead of creating a completely new one.
I did it that way and it works fine.

Reinhard

47
Hi Allan,

as far as I understood Steve in this post, your way won't work.

So I think, you would need at least a luapanel in your screen. Place the button that opens the dialog in that panel. It might work then.
To get your luapanel to work, you'll need mcLuaPanelParent.
So when your button in the luapanel appears, you have your new thread, your lua instance. Of cause, the code for the button must be in your lua-module too.

hth Reinhard

48
Mach4 General Discussion / Re: replacement for mcLuaPanelParent ?
« on: June 03, 2017, 12:03:36 AM »
well - I decided to try a completely different approach, but for that I first have to learn more about it.

49
Mach4 General Discussion / Re: replacement for mcLuaPanelParent ?
« on: June 02, 2017, 03:08:27 AM »
Hi,

I already have a test-environment for wxWindows outside of mach4.
The problem is, that code runs fine in my test-environment but fails inside of mach4.
So creating a dummy panel with a dialog frame around does not change anything. Things work inside that dummy frame, but fail when mach4 runs.

Therefore I'm looking for a test-environment, that is closer to mach4 ...

The refresh-Problem is already known. I do as recommended and restart mach4 as soon as I leave edit mode.

Quote
Before I created my current screen I used the lua panels for everything buttons/dro`s etc and found there was so much more you could achieve than using the conventional buttons/dro`s
Well, based on the ultimate infos from smurph I have to rethink my plans about using lua-panels.
Sure you have more freedom on creating UI-stuff, but if there's no way to exchange data beside using registers ...

Reinhard

50
Mach4 General Discussion / Re: Tool Setup
« on: June 02, 2017, 02:34:00 AM »
Hi,

G40 is ok and quite "normal" when using CAM.

If you then run into differences between distances from CAD and distances in real you have to check your tool definitions in the CAM!
G40 means no tool corrections. So the CAM has to calculate the real tool path and for so has to know the exact tool dimensions.
The tool definitions from mach don't come into play with G40.

That means, if you tell your CAM, your tool diameter is 10mm and in real u use a tool with 8mm then you're 1mm off the path (2mm in distance).

Hth Reinhard

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 »