Hello Guest it is April 26, 2024, 08:07:16 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 - DaveCVI

11
Works in progress / Re: MSM Turn and Mill-Turn screens
« on: May 27, 2013, 07:43:03 PM »
Hi Mark,
I have a question when I make a program lets say with Aspire and there is a tool change do I need to add a sub program (g code, script) into the program for the tool change to happen? I really like the sounds of this program and want to install it but just wanted to confirm how it works in this regards.

Mark
Aspire is an example of a "CAM" program. You work in Aspire, and Aspire generates an output that goes to Mach (the CNC control).  The contents of the output of a CAM program is G-code.
There are slight differences between the gcode languages that different CNC controls speak, and this is generally handled by what is known as a "post processor" or a "post". The "post" logic is how a CAM program tweaks it's gcode output to match a specific control.  When adding MSM to mach, the gcode language that mach understands does not change. So if you are using Aspire with mach today, you will continue to do the same after enhancing mach with MSM.

Dave
 

12
CVI MachStdMill (MSM) / Re: Uninstalling MSM
« on: April 29, 2013, 02:08:09 PM »
Raptor,
I would like to help you.  To do so, we need to alter the course this conversation has taken.  

I respectfully ask that you lower the emotional content of your posts and that you stop accusing Calypso Ventures, Inc. and me personally of having nefarious motivations and of having intentionally written software that disables mach after the MSM software package has been uninstalled. Any such accusations are both false and defamatory.

The tone of your posts make me think you are trying to bait me into entering a flame war style online debate.
I decline to do that as I do not see how that would assist you with any technical issues you may have had.

If you are willing to engage in a 2-way dialog about technical issues, I will continue to offer technical assistance (even though you have clearly stated that you will never be a MSM customer). I am also willing to "hit the reset button with you" and start a fresh interaction as if I had never seen your prior posts.  

However, if, for what ever reasons, we can't find a way to have a productive interaction which focuses on resolving any technical issues you may have experienced, then I do not see how Calypso Ventures, Inc. can be of further assistance to you.


As an effort to help, I will describe how the relevant parts of MSM are constructed.
MSM is implemented via mach's CB scripting facilities.
Anything MSM can do is initiated via mach opening and running a mach script.

The MSM logic to check MSM's trial expiration status is in the MSM init routines.
The MSM init routines are invoked by mach when
a) mach is loading a profile that has MachStdMill.set or MachStdMillLathe.lset as the screen set to load, and

b) mach looks for and runs init scripts (for any screen set) in a location based on the name of the screen set file being loaded, and

c) mach runs the init (ScreenSetLoad) scripts if they are present in the proper location within the Mach directory structure.

To get a notice from MSM that an MSM trial period has expired, mach has to have been started up with an MSM screen set file specified in the mach XML profile, and mach also has to have found the associated scripts in the right place.
I do not know of any way that mach could possibly run scripts that are physically not present on the HDD.

Even if the MSM uninstaller faulted somehow and left ever single MSM related file in the mach dircetory, checking (and deleting manually if need be) the directories I listed in my previous post will make sure the scripts are not present.  I provided the entire MSM directory list set in my prior post. I also said that the dirs listed assumed the default mach3 install dir of c:\mach3\.  If you installed mach and MSM into a non-default directory, just change c:\mach3\ in the list to the directory that you installed into, and are running Mach 3.43.x and MSM from.  


David Bagby
President
Calypso Ventures, Inc.


13
CVI MachStdMill (MSM) / Re: Uninstalling MSM
« on: April 27, 2013, 09:22:19 PM »
Hi,
Ok, I'll start off my saying that I hope posting that helped you to feel better. It sounds as if you have been frustrated for some time - no one finds being frustrated very much fun.

Frankly, to get assistance with MSM, all ya gotta do is ask....    ;)
FYI - The primary way to ask a MSM question is via the MSM support forums at www.calypsoventures.com/forums
You can also email the company - our support email address is easily found from our web site.

Now to the business at hand, I see two ways we could go in this conversation:
a) I could try to help you figure out what tech problems you're having and get you to have a nice working, reliable MSM install that works day in and day out like so many other MSM customers enjoy.
or
b) I can help you to get the system cleaned up so that you are not using MSM at all.

I'm going to concentrate on b) as (given the tone of what you posted) that sounds like what you'd prefer.

Since you claim MSM is saying it is past the trial expiration date, I know that MSM has NOT been uninstalled. Your claim that MSM is both uninstalled AND shutting down Mach is simply, factually incorrect. You may be frustrated, but trust me, software that is not present can't get started and hence can't check an expiration date.  
Since you are getting a dialog box saying that the trial period has expired, then you are starting mach with a profile that is starting MSM (The expiration check is done during MSM initialization, and that can't be run unless MSM is installed).

So step 1 is to uninstall MSM.
To uninstall MSM, simply run the MSM uninstaller - that will remove the MSM software from the PC.

If you want to check Manually that MSM is gone, you can check that these directories are gone:
(all these assume you installed mach and MSM into the default c:\mach3 directory, if you installed to a non-default directory, adjust the paths accordingly)

c:\mach3\bitmaps\MachStdMill\
c:\mach3\brains\autoload\MachStdMill*.brn
c:\mach3\CVI Shared Libs\
c:\mach3\documentation\
c:\mach3\MacshStdMill\
c:\mach3\ScreenSetMacros\MachStdMill.set\
c:\mach3\ScreenSetMacros\MachStdMillLathe.lset\
c:\mach3\Tool Tables\
c:\mach3\WCO Tables\
c:\mach3\MachStdMill*.*


I can also tell from what you wrote that this may not compete the process for you -  

I suspect that when you installed MSM, you did not make a separate Mach profile for running MSM (as called for in the installation instructions in the MSM readme file). The documentation calls out that this is a very good idea - in fact it makes it a required step.
Why? Because MSM alters some Mcode macros for any mach profiles used to run MSM.

When you uninstall MSM, the supporting program code for the MSM specific profile macros are now gone. So when you try to run that MSM specific mach profile, you have the left over MSM specific macros, but not the components they rely on - so mach complains when trying to run the macros.

Uninstalling MSM can not magically revert your profile Mcode macros to a pre-MSM use status.
Profile Macros are stored in a mach profile directory.  The MSM installer & uninstaller can't know which profiles you have are for MSM and which profiles are for other uses. If the MSM uninstaller tried to "undo" that by editing those dirs and "restoring" the mcode macros to stock 1024 state, you'd be yelling about how the MSM uninstaller clobbered your profile macros when it uninstalled...

All this is explained in the various MSM docs, and is the motivation for why one runs MSM via a separate profile.
If one follows that installation instructions, then when MSM is uninstalled, you can simply delete the directory for the profile that ran MSM.

Non-MSM profiles are never touched by MSM.
Assuming you have separate profiles, all you need to do after uninstalling MSM is to run mach from one of the older (non-MSM) profiles.

It sounds to me like the profiles were not kept separate. I'd guess that you
1) Used a single profile (hopefully not the only one you had),
2) Converted it to load MSM (which updated the profiles macros to MSM specific versions),
3) uninstalled MSM, and
4) are still using that same profile to try to run mach without MSM.
Simply changing the loaded screenset name used by a profile is NOT the same as uninstalling MSM.  Attempting to do just that will cause the exact problems you "described"...

If you did not keep your profiles separated, you will need to manually restore the Mcode scripts for your profile to the stock mach-1024 versions.

In case you don't know how to do that, here are the steps:
1) Find a profile that has not been used to run MSM.
Profiles are stored in c:\mach3\Macros\<profile name>\
if you want stock 1024 mill macros try <profile name> = Mach3Mill
if you want stock 1024 lathe macros try <profile name> = Mach3Turn
These should be clean macro copies since the MACH documentation and installer also tell users not to run the stock named profiles (as any customization you make to them will get clobbered by the next mach install).

2) select *.m1s from the non-MSM profile directory and copy them to
c:\mach3\Mcaros\<the profile name that you want to convert back to using stock 1024 macros>

Note: if you have used every profile you have to start MSM, then they will all have MSM versions of the profile macros.
If that is the situation, you will have to reinstall mach to get the mach installer to put mach 1024 stock macros in the default mach profile directories.
If you only have ever used the stock mach profile, you had better copy off that profile's XML before the mach reinstall so that you don't clobber the settings from your one and only profile XML....

I'll also observe that you seem to have concluded that MSM is not for you. That's ok. Sorry you didn't like it.
I agree that you should not purchase an MSM license.

While MSM works great for many, we realize that "one size does not fit all". That's why we offer 30 days free trial use.
Finally, as to your complaint that MSM will not run after the trial period has expired, all I can say is that's pretty much the definition of "trial period"... :o

Dave

14
CVI MachStdMill (MSM) / Re: not using master tool
« on: February 27, 2013, 08:00:27 PM »
Hi,
If the "Master T Mode" button on the Tooling page is not on (I.e. not green) then the value in the Master Tool # DRO does not matter as the DRO value is only used when in master tool mode.

Dave

15
Mach Screens / Re: Looking for a screen seen before...
« on: January 21, 2013, 03:42:26 PM »
Hi,
You may want to take a look at MachStdMill (MSM). The Hardware diagnostic pages provide both the mach logical signals and the raw pin states for 2 parallel ports. MSM also correctly handles the 2nd port as either input or output configuration.

Much more info avail at www.calypsoventures.com

BTW, the PP diagnostic stuff is included in the free Personal Edition of MSM.

Dave
 

16
General Mach Discussion / Re: Mach 3 made unexpected move.
« on: January 18, 2013, 10:51:06 AM »
Hi,
I believe you have hit a known bug in mach 3 (known, reported, but not fixed).

From the MachStdMill release notes section that documents known mach bugs:

4.27   Mach handling of T#M6G43H# in a single block
There appears to be a bug in Mach when it is asked to execute a single block of gcode that contains T#M6G43H#.

It appears that mach is processing the G43H# part of the block before the M6 portion of the block has completed.

In the Mach Gcode documentation, it says that mach will do the M6 code before the G43... but this is an area where weird stuff happens and it's been problematic for Mach in the past. Mach implements the M6 as calls to user scripts and it appears that Mach is not waiting for the M6 scripts actually end before it starts the G43 action.

The result appears to be that Mach can do the G43 in parallel with the M6 sequence and thus the TLO gets (re)applied part way thru the M6 processing - that really upsets  the MSM M6 handling code as it turns off TLO and then TLO gets turned on again out of left field...    The symptom is that sometimes T#M6G43H# will work and sometimes it will cause a tool crash. The exact result each time depends on when different processes get the CPU...

Recommended Work Around:
Place the T#M6 and G43H# into separate blocks (separate lines). This removes the potential for parallelism as Mach is forced to finish one block of code before it can to the next one.

If you are using a CAM post processor that creates a single block for T#M6G43H#, change the post processor to emit two separate blocks (lines) of gcode instead.

Verified on Mach 3.43.37

Dave

17
CVI MachStdMill (MSM) / Re: edit/add hot keys
« on: January 16, 2013, 07:02:52 PM »
Hi,
Well, yes - but due to the way Mach implements screen sets, it's not as easy as one could wish for...  ;D

Key strokes and mouse events are handled by Mach, and mach is responsible for doing whatever action is appropriate for a given key stroke. Mach can be instructed what to do for some keys, but not all keys. For example the Tab key always toggles the mach flyout page; you can't assign any other key to do that, nor can you use the tab key for something else.

Fortunately, many keys can be mapped to some action. This correspondence between keys and actions is defined when a screen set (Set file) is created - it is not a "run time" defined facility.

What you can do is make a customized version of the MSM set file and change the hot key mappings in your customized set file.

The basic process is:
1) Make a clone of the MSM set file to serve as a base for your changes (See section 15 and 10.3.1.1.2 of the MSM user manual)
2) Use a screen set file editor to change the default MSM hot key mappings (I recommend MachScreen for set file editing). You will have to find the buttons you want a hot key mapped to and set that key as a property of the button via the screen set editor.
3) tell MSM to use your customized MSM set file (user manual section 10.3.1.1.1)

BTW, since you mentioned spindle on/off, in case you were not aware of them, there are already hot keys set up in MSM for those actions. See section 2.2.4 of the user manual for the MSM hotkeys.

Dave

18
CVI MachStdMill (MSM) / Re: Bitmap images not showing
« on: January 07, 2013, 05:36:58 PM »
Keith,
I was wondering why, in Mach3Screen designer, do the bitmap images not show?  Without seeing the images
I cannot place features in the correct position.

My prior response may have over thought the question - If you are already using machscreen, check the bitmap path in machscreen, it may not be pointing to the MSM bitmap files.

in machscreen: options; settings; Generic progr settings, then check the "user defined image path".

Dave



19
CVI MachStdMill (MSM) / Re: Bitmap images not showing
« on: January 07, 2013, 05:29:28 PM »
Are you using screen4 as the screen set editor?  If so, 99.9% probability that is the problem.

Generally this is a problem with the contents of the set file as written by screen4 and how mach renders the set file when loading mach.  There are known cases where screen4 will corrupt a set file in such a way the images will not be rendered correctly by mach (it's a "layering" issue). Alas, Screen4 is a very old program that has not received any maintenance work for many years.
The issues are more common with lset files (lathe mode screens) than set files (mill mode screens) - it turns out that mach does not render lathe and mill screens using the same rules (known bugs in mach3).  See item 4.35 in the MSM release notes for some more info. That item lists some of the known bugs in mach wrt to lset/set file rendering - I suspect there are more than the ones I managed to find :-(

I'd highly recommend that you use MachScreen to edit set files instead of Screen4.  When the image rendering problems were discovered, Klaus (Machscreen's author) included features in machscreen to work around the problems. You can also swap order of bitmap images within the set file with machscreen to fix this type of problem.

Machscreen can be found at http://www.kd-dietz.com/klausphp/index_eng.html

Dave

20
CVI MachStdMill (MSM) / Re: setting up tcp tp
« on: November 09, 2012, 11:01:24 AM »
Hi,

Hi Dave
I checked settings,altered them  for max z travel but now getting
PROBE FAST FEED <=0, OP CANCELLED
Check the value for Probe feed rate in the probing parameters panel - I'll bet it's set to 0.

I'm guessing that this the first time you've ever attempted a probing operation with MSM.
An important concept is that a probe (G31) Operation is "feed rate move to location but stop if probe input line goes active".   Thus probing ops are used to run not only a 3d probe, but also to run the TCP TP etc.
Therefore, the movement used (feed rate, max distance etc) for all probing ops is configured by the various values in the Probing Parameters panel.

It would probably be a good idea for you to read section 8 of the MSM user manual which covers MSMs probing operations. In particular see section 8.5 which covers the probing parameters and section 8.11 is a step by step tutorial to set up probing the first time.

Dave