Hello Guest it is March 29, 2024, 01:51:11 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

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 »
421
CVI MachStdMill (MSM) / Re: Compressed screens and buttons
« on: July 17, 2010, 01:59:01 AM »
Hi,
I'm going to have to think about this a bit...
I don't think that during the alpha testing period that anyone ran the screen set on a PC that was lower resolution than the minimum required 1024x768.

I've only seen the "black button" draw happen in conjunction with the dialog box on top of a button (as described in the errata note).

Some questions:
1) When you change to another page and then back to the page that had the black buttons, do the buttons redraw correctly?
2) Are you using the mach menu general config option "auto screen enlarge" to shrink the screens?
3) does your netbook pc attempt to make a smaller vertical physical screen resolution (600) look like 768 high to windows applications? (I"m wondering if there is a netbook specific layer of software in the windows screen driver that could be causing a problem)

Dave

P.S. I moved your post to a separate topic so that this discussion would be separate from the welcome thread.

422
For those watching this thread, the MSM beta is now available from the machsupport site.

The announcement is at
http://www.machsupport.com/forum/index.php/topic,15366.0.html

Dave

423
Greetings!

We have an announcement to make:

Newfangled Solutions LLC and Calypso Ventures, Inc. are announcing that the beta version of the new mill/router screen set for Mach3 V3 (MachStdMill) has been released and is now available for download.

A new web forum section has been set up specifically for all things MachStdMill. It will be the primary support venue for the beta program and can be found at:

http://www.machsupport.com/forum/index.php/board,85.0.html

On the forum you’ll find some sticky topics with
1) Introductory information about MachStdMill and what features it provides,
2) Instructions for downloading MachStdMill from machsupport.com

Finally, for those that heard us say we were targeting the release for the week after the CNC workshop, please accept our apologies for the additional time it took to get the Beta release posted. We think you’ll be happy with the results.

See you over on the MSM forum!
Dave



424
VB and the development of wizards / Re: OEM Buttons ???
« on: July 15, 2010, 10:35:54 AM »
Terry,

The tools added to mach 3.43.6+ have the syntax they have for good reasons. Yes, they are a more modern approach than being restricted to only naming scripts by numbers (and are still quaintly old fashioned when compared to modern computer science techniques). 

One of the nice things about more modern programming techniques, is that they can be used to do do the buggy whipper approach too. :o

Make your script,
call it 444.m1s
put it in mach's dir
call it via RunScript("444.m1s").

You asked how to do something and got an explanation of how you can do it using the tools recently added to mach.

If RunScript("444.m1s") is to different from your preferred DoOEMButton(444), you have a choice to make....
In this case, you can choose to use the available tools to accomplish what you asked about, or you can choose not to.

If you don't want to use/learn the new features, that's fine too, life's full of choices.

Dave

HiYa Dave,  HUM

Lets see  I could do this

DoOemButton(444)   (Simple Call)     or

RunScript(GetMainFolder() & "\TerrysMacros\" & "DispenseIceCream.m1s")     (Reminds me of Egyptian hieroglyphics)

Modern is not always better and change for the sake of change is rarely productive. IF the wheel turns smoothly DON"T cut a flat spot in it just because you got a new saw. On the other hand IF the wheel is squeeky and drags a bit DO put some grease in the bearing.

The problem with Brians IS you cannot call a script to terminate a function. Art left that part out of the ladder structure before he retired. AND it would be darn handy to have when you have to do a work around.

Metal as a matter of fact I do still use a lot of chromeoly that has been around for ages and gues what it STILL works great.

Buggywhipper ??  Better to be an old buggywhipper than a GAMEboydriver.   

Take Care(;-) TP


425
VB and the development of wizards / Re: OEM Buttons ???
« on: July 15, 2010, 10:07:58 AM »
Hi Tweakie,

Well, I  could give you a overly slanted, one sided explanation as Terry did (although my slant would probably be opposite of his   ;) ).... A buggy whip is American slang for something that is obsolete, and a buggy whipper is one that is reluctant to change with the times.

From wikipedia:

Buggy whip and coachwhip

"A buggy whip is a horsewhip with a long stiff shaft and a relatively short lash used for driving a horse harnessed to a buggy or other small open carriage. A coachwhip, usually provided with a long lash, is used in driving a coach with horses in front of other horses. Though similar whips are still manufactured for limited purposes, the buggy whip industry as a major economic entity ceased to exist with the introduction of the automobile, and is cited in economics and marketing as an example of an industry ceasing to exist because its market niche, and the need for its product, disappears. In discussing market regulation, it is often held that the economy would be disadvantaged as a whole if the automobile had been banned to protect the buggy-whip industry.

Buggy whips are not entirely gone. A resurgence of interest in the international sport of combined driving and historical carriage driving, sports enjoyed by people of all ages, has allowed some buggy whip manufacturers to stay in business, serving this specialty niche market. "

Dave

426
VB and the development of wizards / Re: OEM Buttons ???
« on: July 14, 2010, 11:04:13 PM »
Terry -
See below
Dave

DAVE if in VB I say   DoOembutton(100) I can get a Machfunction. The question was can you create your own OemButton()

[DB]: No - you (user) can't. OEMButton #s can only be created by changes to the mach sources.

to do a function(not an internall mach function) AND it be callable from VB

[DB]: You can create a function that is callable from a Cypress Basic script
(Yes, I am playing Don Quixote and using my lance to tilt at this wind mil  ;D   Mach does not implement VB scripts - it implements Cypress Basic scripts. While similar, they are different language specifications. Sorry, it's not you, but I'm tired of questions that result from people calling cats dogs and then wondering why they don't bark....).


or BRAINS for that matter.  

[DB]: I'll skip brains calling scripts for now - that's a whole 'nother ball game... and one I have not looked at in some time so I don't really remember the possible brains to scripts connections.

That way you only create the piece of code once

[DB]: You can create it once, and you can store it in one place, and you can call that single copy of the script from any other script, and it will be called in a straight sequential fashion (not an async execution). This is enabled by the new facilities in 3.43.6+  Get the latest programmer docs from the doc page and look up RunScript().

Let presume that you created a function called "DispenseIceCream" and it now lives in a file called DispenseIceCream.m1s on your hard disk.

AND Can call it into use with a simple DoOemButton(444).

[DB]: NO. since you can not make a new magic #, you can't do DoOEMButton(NewMagicNumber).
(however, only a buggy whipper would want to... ...for those wondering, it's a running gag between Terry and I)

What you can do is run a named script. The call would look like:
RunScript(GetMainFolder() & "\TerrysMacros\" & "DispenseIceCream.m1s")


And Yes numbers make perfect sense to a CNC programmer everything we program in is numbers, Gcode,vars,parameters, gotos,subs,etc.

[DB]: Might be time to learn a new trick - or do you also stick to only metal alloys that were available in the era when gcode was defined...  ::)
 
(;-) TP


427
VB and the development of wizards / Re: OEM Buttons ???
« on: July 14, 2010, 09:15:10 PM »
Terry,
The question does not make sense to me - I'll break it down to explain why...

First I'll try to understand "... create an OEM BUTTON..."

I know you know how to create a button, so I'm wondering: what the qualifier "OEM" is intended to mean in this context?
A button is a screen control object that Mach implements. Mach can do one of three things when a button is "pressed":
1) call a mach internal function
2) run some cypress basic script (FYI - I've stopped calling this "VB" as the language supported is "Cypress Basic" which is not the same as "Visual Basic".)
3) run some gcode

By "OEM BUTTON" do you mean a button that does #1?

Then I puzzled over "... OEM BUTTON that can be called from VB"

A button does not get "called". Cypress scripts can call subroutines or functions. Functions come in two flavors: those built into Mach and those which are defined by a script programmer.

If you mean that you want a Cypress script to invoke the same function that the button would invoke when pressed, just have the script make the desired call to Mach (DoOEMButton()).
(The name of the Mach API "DoOEMButton" is misleading - it would be more correct for it to have been called "InvokeMachFunctionByPassingMagicNumber").

If you mean that you want to create some new function, which is not already part of Mach, then just write it as a sub or function and call it as needed.

As a user, there is no way to define new "OEM functions inside mach" - you gotta change the mach source code to do that.
You can define all the functions you like and call them whatever you like - they just won't be globally known by a magic mach function number.

Dave


428
General Mach Discussion / Re: Strange Problem- Never seen before
« on: July 12, 2010, 05:40:18 PM »
I don't think it's the IJ incremental/absolute mode that is the issue.

A mismatch between GCode assumption and the IJ incr/abs setting can cause the "wrong way loops" that people see. The default IJ mode is controlled by the General config settings. The IJ mode can also be switched within a gcode program by G90.1 (IJ abs) and G91.1 (IJ incr).

Whether coordinates, and hence movement, is incremental or absolute is independent of the IJ setting. 

Absolute coordinate mode is set by G90 and incremental coordinate mode is set by G91.

Dave

429
CVI MachStdMill (MSM) / Where to get MachStdMill
« on: July 09, 2010, 08:56:04 PM »
Hi,

MachStdMill is available for download from the Calypso Ventures web site on the Dowloads - MachStdMill page:

MachStdMill Download

At that page you can download:

1) the MachStdMill Readme file.
2) the MachStdMill installer package
3) the User Maunal
4) the latest Release Notes

Dave



430
Hi -
Status update:
I have the MSM part 99% ready to go.

Brian has the hard part at the moment... There isn't a revised 3.43.x yet so the release will be held up a bit.
(During the past week Brian said something about a heat wave in Maine and something about he and the computers melting into puddles. As I live in Calif, my understanding is that in Maine, a heat wave is anything above freezing <grin> ).

In any case, as soon as there is a revised Mach release, I'll do the MSM testing of the changes to verify the targeted bugs are gone and then we will get the package posted.

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 »