It’s just about a week since MachStdMill started beta, and I’m happy to say that only minor bugs have been reported so far. (I hope that statement is not see as taunting by the gods of software…)
We’ve corrected all the bugs reported and then created an updated release. MachStdMill Beta 2 is now available for DL from machsupport.com.
This is a quick summary of the changes: User manual: • Updated MSM manual screen shots to show sliders full width now that this bug is fixed in mach. • Added foot note 12 to page 38. • Added WC zero setting example pictures and dial indicator touch tool sections to MSM manual. Section 4.3.1 revised. Section 126.96.36.199.1 added.
MSM changes: • Probing page DAO X+ button spots were invoking X+ arrow (non- Down And Over action) probing instead of DAOX+ Arrow.
• Updated Probing Lib to 0.63 o Reworded some error messages that are displayed when ESC is used to abort a probing operation o Changed slow probe back off distance to be clearance distance for the axis (it was MinProbe distance, which was incorrect. MinProbe distance was too small a distance to un-trigger some probes between the fast probe and slow probe operation.
• Changed GotoZero button action. It was not doing same call as 1024 (OEM function 1017) and so it was not paying attention to safe Z.
• Last Page tracking was not getting initialized correctly on MSM load. This could cause return page for M6 sequence to be off if M6 was done immediately after MSM load before a page had been accessed.
• Added #expand to index in programmers manual.
• Made Fly Out background in 12x9 resolution 1024 high. This removes the blank gray area that was below the FO panel area.
The above info is also in the updated release notes installed with beta 2.
Updating MSM Beta 1: If you’ve already installed MSM beta 1, just run the Beta 2 installer and install on top of Beta 1. There is no need to recreate a profile etc – you can use your existing profile. Therefore, at the last page of the installer, you can just uncheck the “run mach3.exe” box and then click finish. The update process is now part of the readme file.
New MSM installs: If you are just installing MSM for the 1st time, follow the first time installation instructions in the readme file.
• This release has implemented a major feature: Support for user customization of MachStdMill. Good news: The feature is now implemented.
Bad News: Implementing the user customization support required massive changes to the entire MachStdMill package. Literally every script file was changed, as well as all the .set files.
This level of change tends to create a decrease in stability. I’m hoping that is not the case for beta 3 – but only you folks will be able to tell me that.
Fortunately, the numerous edits were mostly to change the paths for #Expand statements – so a editing error tends to just not compile, rather than cause subtle runtime differences. I did run thru all the buttons and have been using this change for about a week, so things look OK, but there could be something that was not caught.
A new chapter to the user manual has been added which describes the MSM support for user customizations.
I feel obligated to emphasize this: Customizations are possible – but are entirely your responsibility. CVI will not be supporting user modifications as part of it’s volunteer MSM support effort. (Blatant commercial: You can always contact me to inquire about the consulting side of Calypso Ventures, Inc. <grin>)
• Beta 3 will require that you uninstall beta 1 and/or beta 2. You do not need to recreate profiles etc. The uninstall is necessary to clean out beta 1-2 files that have moved to new locations in Beta 3.
• All verified Beta bug reports (that can be fixed in MSM) have been fixed – see release notes for details.
• Tightened up tests for use of machine coordinate operations on unreferenced machines. While this might annoy some users, it was considered as a safety issue and the run time warnings are considered a reasonable trade off. To avoid the warnings, either don’t use these features when unreferenced, or invest in home switches and reference the machine when you start it.
• Programmer’s manual got some corrections, and a new section that has the best list I know for Mach3 V3 “magic numbers”. The list was compiled by people working to assist in creating the revised numbering scheme for V4. The V3 list in the manual is what I’ve used for MSM V3 development and includes updates from as recently as 2 weeks ago.
• MSM Macropump background task: I’m 95% certain that the cause of the background task stopping has been identified. In beta 3 two things were done re this topic: 1) a watch dog will notice if the MSM Macropump has stopped and alert you. Good news: you will know if it stopped running. Bad news: The watch dog will notify you it is not running every 30 seconds.
2) Some changes were made internal to MSM to reduce the probability of the MSM Macropump getting stopped. However, a proper technical fix will require a change inside Mach. So we’ll need a new dev rev to put this one to bed.
• Mach bugs: Several Mach 3.43.x bugs have been identified and reported to Brian. Due to the nature of some of the bugs, I am recommending that you stick to 3.43.10 for now and not use 3.43.12 with MSM.
[Addition 8-2-2010 midnight] The Programmer ref manual in beta 3 is v0.21 and it had a format issue... the new tables of Button/DRO/LED numbers had the actual numbers off the edge of the page. That made the tables a bit less useful than anticipated. Sad v0.22 of the manual, with this corrected, can be downloaded form the machsupport documentation page. ]
The two changes from Beta 4 are: 1) MSM beta 5 now requires Mach 3.43.16 as the minimum mach version. 2) The MSM installer has support for installing optional (yet to come) MSM components (e.g the bitmap source files).
Mach3.43.16 has fixes for the following Mach bugs that were impacting MSM: MDI command no longer causes loaded Gcode to start execution. PeriodicScript execution time > script period no longer causes the script to hang. Back to Back StartPeriodicScript calls no longer cause syntax errors from scripts being started. Spindle pulley reverse direction repaired.
Mach 3.43.16 is now the recommended version for use with MSM.
Please see the release notes for more info.
The release notes also contain updated info re still existing mach bugs as well as update to probing functionality with Smooth Steppers and multiplexing BoBs.
1) beta 6 now requires mach 3.43.19 This mach dev rev fixes several bugs that were problems for MSM, including: Probing with SmoothSteppers Cycle Start vs tool changes Mach3 XML save vs Current directory
This dev release also changed some script APIs - so MSM was updated to match the changes.
2) Several small MSM bugs related to probing have been fixed
3) An experimental new feature has been included in MSM - see releases notes.
See the release notes (available separately from the download page) for details of what has been changed.
Hi, Beta 7 fixes a bug in Beta 6: Mach 3.43.19 StartPeriodicScript returns error if script is already running. Old semantics (3.43.16) did not return an error in this case. In Beta 6 this caused a error if loading MSM from MSM (as the background scripts are already running). Changed MSM logic to test script state before (re)starting a script.
I missed converting a RunScript call in the M6 sequence - the call was using the old RS semantics not the new ones in 3.43.19. This caused the RunScript call to invoke the M6ATC hook to fail. If that fails, the code aborts the tool change - as it's considered poor form to do an ATC routine without the user supplied ATC script...
Hi, When I announced beta 6, I had thought that the issues in mach re probing and SS were fixed up. I guess i jumped the gun a bit, so I'm letting people know that the mach issues with Probing and SSs are not yet all resolved.
As of Mach 3.43.19, probing with a SS can still result in bad movements and hence possible crunched probe tips.
This is minor rev # change so the installer will require you to uninstall Beta 11 (v0.3.15) before installing Beta 12.
The highlights are: This release has several minor fixes to user reported issues in the probing lib. In addition some internal re-factoring was done of entry points into the probing lib; There should not be any user observable changes resulting from this. The RH/NRH LED has been tweaked yet again for appearance. An obscure installer bug was fixed (only caused trouble if going form an old alpha rev to a newer beta rev). Fixed a bug were the length and diam wear DROs were swapped on the Touch page.