Hello Guest it is April 26, 2024, 02:14:41 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 - Ron Ginger

781
Newfangled Solutions Mach3 Wizards / Re: New 3D probing routine
« on: November 11, 2007, 09:01:44 AM »
I think intelligent probing is a very complicated subject, well beyond the meager programming capabilites of the Mach wizard and VB environment. In my view that is the domain of plug-ins, where you have the full power of C++ and connection to all of Machs internals.

I did do a CopyCat wizard that lets you walk around a part with manual jogs and build a part file. I had considered a routine to let the probe pick the exact value after you manually moved close, but I never tried to do anything with  it- I didnt have a probe then. I have one now and maybe later this winter I will try some experiments.

782
Newfangled Solutions Mach3 Wizards / Re: V2.75 ready for test
« on: October 31, 2007, 05:38:22 PM »
I just updated the wizard in reply 1 of this topic. I found a bug in the surface wizard that was not handling the top of material correctly- it actually dives into the work and tries to cut the last pass first. Not good !

783
Newfangled Solutions Mach3 Wizards / Re: V2.75 ready for test
« on: October 30, 2007, 11:28:46 AM »
Its on Newfangled, but the link is still broken. Here is a direct URL that will work.

http://www.newfangledsolutions.com/downloads/Manual-V2-75.pdf

784
Newfangled Solutions Mach3 Wizards / Re: V2.75 ready for test
« on: October 29, 2007, 04:20:13 PM »
I have edited the manual to reflect the changes in V 2.75.  Art has placed a copy on the FTP site, and I have sent it to Scott to include on the Newfangled site. Its to big to attach to this forum.

Let me know if you find any errors.

785
Newfangled Solutions Mach3 Wizards / Re: V2.75 ready for test
« on: October 28, 2007, 12:08:14 PM »
Funny to be on the other side of this conversational debate. My first experience with real CNC was when a good friend bought an AcuRite MillPower system. That does ONLY conversational, it didn't allow Gcode at all. I got so excited about it I wrote a similar program that ran under Win 3.1 See http://plsntcov.8m.com/CNH.htm for some info on it. That system worked really well, and I actually made parts with it- the screen shots show a part for a traction engine model I built that actually was made with the software.

That software used a dll driver that could not be ported after Win95. I came to Mach because it promised an interface that could be called from VB. I was going to  port my code to use Mach as a 'back end' I re-wrote it all into very good quality object oriented VB, but I was never able to get the Mach.ocx to work. I don't think anyone else ever did either and Art eventually quit talking about it. I met Brian Barker when I took my code up to U Maine to show him

So, I really like conversational approach. Actually, I am more into what I call 'Interactive Milling' I like an interface that lets me define parts and simply run them without ever having gcode involved. Thats the MillPower model.

MY problem with the wizard set as it exists is the poor VB script environment. I could do lots of neat things to the wizards, but since every button is its own environment and cannot see or use subroutines form any other button or source it becomes very difficult- maybe tedious is a better word. For example if I wanted to add a 'process sheet' to each wizard the code to do it would have to be included into every screen. Ok, so cut and paste would make that possible, but if i ever needed to make a change Id have 20+ places with the same code to change. I consider that un-supportable.

I don't mean to knock the wizard set- for what they do they work very well and a lot of guys have done a lot of work with them. I will support them, fix bugs, and make minor improvements, but I'm not going to try to make a whole new environment out of them.

What I am doing now is learning Flash and Action Script 3.0 That will be a VERY powerful capability and one could build a nice, interactive, conversational package on it. I'm a long way from being able to do that, but I am working on it.

786
Newfangled Solutions Mach3 Wizards / Re: V2.75 ready for test
« on: October 26, 2007, 09:11:23 PM »
Art has promised a new VB function that can read the description from the tool table, so when that happens I should be able to make this look much better.

I could list the entire 255 entries of the tool table in the list box, but that might  make things very slow, and much harder to read. This whole tool table thing was supposed to make entry SIMPLE not more difficult.

Obviously a wizard cannot know that the operator has screwed up the tool table. If you use tool tables I suggest you do it VERY carefully.

I suspect most use of the wizards is for simple, one-off jobs by guys that dont even use the tool table. I have never used it on my mill, I had to fill one in so I could test this code.

I have been adding more comments to the Gcode as I work on the wizards. I intend to make each one write all its major parameters at tehtop of each operation. Its good documentation and it helps me debug.

I am not about to try to make this poor VB script system try to print sumary data. It is an interesting thought to create a separate file with just the wizard input data.

787
Newfangled Solutions Mach3 Wizards / Re: V2.75 ready for test
« on: October 26, 2007, 11:19:04 AM »
I just modified the first topic to replace the Newfangled.zip. This new version now handles the full 255 entries in the tool table, skipping over those that have a zero dia tool. Still no description, but Art has promised a function for the next Mach version.

788
Newfangled Solutions Mach3 Wizards / Re: V2.75 ready for test
« on: October 23, 2007, 08:46:52 AM »
*****I am assuming that if I enter a tool# that the diam info will update to reflect the change If so then it does not work. If that is NOT how it works then it should(;-) IF you are goint to use the tool table info. If that is NOT how it works you need to explain the process

No, that should not work. The idea is if you want to get the data from the table you press the button and select it. If you do NOT use the tool table then you can enter the number and diameter directly into the DRO. Some will likely leave the tool number as 0, just enter the diameter.

*****You could add a label along with the TOOLDESC function to display the description of the selected tool,, also did not ART add a new command to retreive the string for use in VB???

The note I saw only lists the numeric tool table values. I will look a bit deeper. The TOOLDESC would allow me to display the description AFTER it was selected, but not in a way I can pick it up for the list box.

****I have 52 tools and the display only shows 6, and there is NO scroll bar and the up/down buttons scroll but only through 1-6. THat is ALL that displays

Do you have a gap in your list- an unused tool at #7 maybe. The code reads the tool table params unti it gets a null. There is no way to tell how many tools there are.

I was warned the tool table would be a can of worms !


789
Newfangled Solutions Mach3 Wizards / Re: V2.75 ready for test
« on: October 22, 2007, 08:58:10 PM »
Hi ROn it looks really good, But I did find some bugs and offer some suggestions

1.  TOOL properties page it will not let you make a manual entry for the tool selection, it accepts the number but does not update the info.

Works for me- are you sure you are pressing enter?

2.  The tool selection table needs to include the tool description. I have 6  different .500" tools but can't select one without knowing what it is.

Sorry, Art does not make the description available, just the tool params- numbers, not strings. I see the need, but cant be done.


3. the tool selection table will not select tool#1  it  just lets you know you must select a tool.

Found that and fixed it, it will be in the release version

4. The tool table selection does not have a scroll bar to allow you to see all the tools it just display 1-6 that all.

I added 8 tools and a scroll bar pops up just as expected. It works for me.

5. some of the  wizards allow you to set TOM (top of material) other assume the TOM =zero. To be usefull as a program code assembler you need to be able to assign what the TOM is. ( really important)

Yes, this has been raised before. Its a big change, I will try to get to it.

6. On some wizards such as the rectangular pocket there needs to be a reference as to what the width and length refer to is the width Y or X axis, is the length Y or X axis.

Yep, and on the old surface wizards it was confused inside the code- I dont know how that one ever worked. I will try to clean this up.


7. On the drill wizards there need to be a reference as to what the starting angle is referenced to y or x axis and where is zero.

It assumes the CAD convention, 0 degrees is 3:00 O'clock

8. On some wizards the term pitch is used on others it is plunge/ramp on others it is ramp angle. These terms need to be the same for consistancy .

Yep, Ive fixed a couple places, Ill get the others.

9. On wizards that have a drill or hole function the terms step depth, depth,peck depth should just show a value based on TOM  and not allow the +/- sign this can be confusing to newbies. or does the +/- apply to this function??

On most of them I think the code handles the + or - OK. You can enter either, it takes the ABS() of the number and uses it correctly.

10. on the code preview you need to add a rewind button so you can preview the code and tool path easier the second time( GOOD idea the gcode window) Good for proofing the code.

Yeah, I thiught the Gcode window was usefull- it helped me debug the code, so I thoughtit would be good. I just use the scroll bar to move around, Ill see if I can add a rewind button.


All in ALL a very good step forward. I look forward to using them. (;-) TP

Thanks for all the review.

790
Newfangled Solutions Mach3 Wizards / Re: V2.75 ready for test
« on: October 22, 2007, 07:50:35 PM »
Yes, there should be a Shapes.tap file in the Mach\gcode folder. It should have been installed by the mach install. I will attach a copy here.