Hello Guest it is December 01, 2021, 01:10:55 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 - japrenticeuk

Pages: 1
1
Newfangled Mill Wizard / Machine Max Settings not persistent?
« on: November 15, 2014, 12:11:12 PM »
Greetings

I cannot seem to get the Machine Max Settings to stick.

Are they supposed to be persistent for an installation or be a property of a job or (I hope not) need setting every time?

John Prentice

2
Newfangled Mill Wizard / Mill Wizard crash on attempting to save G-code
« on: November 15, 2014, 12:07:07 PM »
Ron - greetings

Running licensed 1.0.17 on Win 8.1 as Administrator.

Very frequently (5 times in 15 saves this afternoon) the program just drops dead with the "Windows trying to find a solution" dialog when trying to save G-code. The frame of the file picker is displayed but with no contents.

I cannot find the sequence to make it happen to order. I had a theory that the problem was a folder with a very large number of files but that does not seem to explain it as it then failed in a small folder.

Job file (which is meant to be a very simple demo for a prospective customer) is attached.

John Prentice

3
CVI MachStdMill (MSM) / Uninstalling MSM
« on: August 10, 2010, 06:15:20 AM »
This feels like a dumb question but a lot of searching has not worked for me.

Beta 3 and Beta 4 require uninstalling of earlier versions. How is one supposed to do this.

I have looked for options in the installer program and eventually resorted to searching for all files with MSM and MachStd in their names and deleting them.

Still the Beta 4 installer tells me I have an old version installed and I must uninstall it.  How?

TIA

John Prentice

4
General Mach Discussion / New procedure to cope with wiki vandalism
« on: June 10, 2007, 03:16:36 PM »
Greetings to all:

I am afraid that some people have more time than sense and so we have had further attempts at vandalism on the wikis.

To *edit* pages of any of our wikis you need to be registered.

I am afraid we have made membership application subject to a moderation process.

ou request membership by sending Art or myself a personal message from the e-mail address you intend to use with the wikis.  State:

(a) which wiki you want to join,
(b) which page you want to contribute to by editing and
(c) your real name and postal address.

This information will be used for no purpose other than signing you up.

You will be allocated a random password which will be emailed to you. We will not know it. You can of course subsequently change it to a memorable string.

Finally I apologise for this additional hassle but reiterate that you can read the information at any time without logging in.

John Prentice

5
General Mach Discussion / Wiki vandalism outbreak
« on: June 03, 2007, 03:48:33 PM »
I am afraid we have had a bout of vandalism in the Wikis.

If the information you expected has vanished then by logging in and looking at the history you should be able to revert to a version that it OK.

Appropriate steps, including some IP address backtracking, may lead to the perpatrator(s) who should expect an unpleasant experience.

John Prentice

6
Greetings

I am struggling with a bug in a plugin for the Shuttle XPress - It makes funny step moves from inner wheel if machine is in G91 (Inc move) mode and I need to find a Mach variable to tell me when G91 is active.

Has anyone any idea? Reading the .H files has not help so far but there is an awful lot of them :=)

Thanks

John Prentice

7
Hi Art,

I am sure I will learn much more by a bit more reading and trying some code. Art does give us license to "play" - and doubtless break a toy or two. A few question relevant to where I am now are:

(a) Would it be possible for the InitControl () routine to be called later in Mach initialization? It feels to me that I might have to have a "first time" flag and test it in Update () so I can be sure all the Mach variables are set up before I do my initialization which is unfortunate. Config is not generally a useful place to initialize things as it will generally not be called in a working system.

(b) Art says that the plugin is not a separate thread when called during Init - Is the plugin always called in the main Mach3 thread (I am not sure I know what I mean by that). What are the "critical section/mutex" issues accessing data in Mach if one gives up control by (e.g.) using a modal dialog box? In particular the engine is obviously a separate thread so one needs to be very careful with its data (e.g. the TrajBuffer).

(c) Is there any mechanism by which a plugin can see the press on an OEM button (e.g. what could a button or macro script do to raise a flag)?

(d) By multiple threading you can "run at speeds up to 100 times per second". Does this implay one can get a latency in a plugin of 10mS? If so can you eaplain a bit further please?

(e) Very usefully it looks as though a G100 (or any other pulser) will be able to co-exist with parallel ports - not to split axes between I/O routes of course but to allow encoders or switches on the parallel. This means that the Mach "port" number range will need extending and Config in plugins needs to be able to say which "port" the plugin "drives" At present Modbus is hardwired to Port 0 and G100 to Port 1 (was 0). The config is needed because of arbitrary combinations of plugins. It may be a bit hard to explain to the user too!

Probably more later :=)

John Prentice

Pages: 1