Hello Guest it is May 04, 2024, 06:55:45 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.


Messages - DaveCVI

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 »
321
Please check the path for the PDF reader utility - w/o knowing where the PDF reader is, MSM can't open any of the PDF format manuals.
You need to set the full path and file name of the reader .exe file.

Settings-Common page, "set utility paths" button.

Dave

322
FYI -
V0.22 of the manual is avail on the machsupport documentation page.
This revision also adds tables of the magic numbers to the manual.

Dave

FYI - As I have access to the Programmer's manual, I have taken the liberty to edit the relevant sections of the manual to clarify this topic.

The new revision (0.21) It will be included with the next MSM beta release. When that is ready, I'll also send the revision to Scott so he can update the version linked to from the download page.

Dave


324
I've done what I can about this in MSM beta 3. A complete fix will need some mach.exe support.
See the beta 3 announcement post and the beta 3 release notes for more info.

Dave

325
CVI MachStdMill (MSM) / MachStdMill v0.2.1 Beta 3
« on: August 02, 2010, 09:52:10 PM »
Hi,

I have sent to Scott the MSM Beta 3 release files for posting on the Machsupport download page.  Due to the fact he and I are 3 time zones apart, the files may not be available for download until tomorrow sometime. I’ve also asked that the release notes be avail from the download page so that people can read about the changes before installing the package.

•   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.  

Dave

[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.  :(
v0.22 of the manual, with this corrected, can be downloaded form the machsupport documentation page. ]


326
CVI MachStdMill (MSM) / Controls not responding / MSM background task
« on: August 02, 2010, 01:23:17 AM »
An update:
I think I have figured out what is happening when some MSM controls stop responding.

I'll skip the gory technical details other than to say that the background task that MSM is using to drive those screen controls is getting killed/hung.   

All the controls impacted are things that were designed to be inside mach for V4, but I had to fake them on V3 - hence the background task that updates a bunch of User DROS and LEDs (this makes the V4 controls work on V3). When the task stops running, the controls stop getting updated.

I've contacted Brain to confirm the theory as to why this happens... I suspect it will take an update to Mach to cure this one.

Right now, I'm planning to hold the next beta release until we can sort this out.

I'll let ya know more then I can.

Dave

327
You need to tell us what version of mach you ran the script on...
Dave

328
If you are asking why you see this sequence:
1) moves down (using Probe Fast FR), until it touches
2) moves up by Z clearance amount
3) moves back down to touch again (using Probe Slow FR)
4) Moves up by Z clearance amount

This is normal when you have the Probe Slow FR set to non-zero.

See user manual section 7.1.5.5

Dave

329
Thanks for the testing.
I'll inform Brian that it appears that the bug has crept back into 3.43.12.

Dave

330
FYI - As I have access to the Programmer's manual, I have taken the liberty to edit the relevant sections of the manual to clarify this topic.

The new revision (0.21) It will be included with the next MSM beta release. When that is ready, I'll also send the revision to Scott so he can update the version linked to from the download page.

Dave

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 »