Hello Guest it is April 26, 2024, 04:16:10 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 - ART

771
VB and the development of wizards / Re: Using the COM API in VB .NET
« on: January 19, 2010, 07:29:16 PM »
Tony:

  There isnt. I wrote an application called Mach3 remote that exemplifies how to use the interface though , and I believe its downloadable somewhere
on the web site. IF you cant find it I can send you a copy of the C++ application if you contact me offlist at fenerty@artofcnc.ca


Art

772
VB and the development of wizards / Re: Using the COM API in VB .NET
« on: January 19, 2010, 04:08:20 PM »
Tony:

  Wont be many that can help I think. I wrote that dispatch for use in C++, where you specify more data and get the actual scripter dispatch from mach3 before
using it.. as in

LPUNKNOWN lpUnk;
LPDISPATCH lpDispatch;
CLSID   clsid;

CLSIDFromProgID(OLESTR("Mach4.Document"), &clsid);
GetActiveObject( clsid, NULL, &lpUnk);
lpUnk->QueryInterface(IID_IDispatch,
      (LPVOID*)&lpDispatch);
lpUnk->Release();
mach4.AttachDispatch(lpDispatch, TRUE);
lpDispatch = mach4.GetScriptDispatch();
scripter.AttachDispatch(lpDispatch, TRUE);

   Now how that translates to VB, Im not sure.. I only program in C++..

Art


773
LazyTurn / Re: LazyTurn
« on: January 17, 2010, 08:55:17 PM »
Hi Guys:

 Just thought Id post a note so you know work progresses.. That algorithm failed, but now..3 new algorithms later.. Im producing fairly good finishing passes.
Unfortunatley, this pointed out some failures in the roughing, which Ive now rewritten for greater accuracy.. my roughing wasnt near as accurate as the finishing,
and I didnt notice till the finish path was laid on top of it.. anyay..better now. :)

   Cant say how long till I nail down the finishing.. but its half way there anyway..

Art

774
General Mach Discussion / Re: Driver Test Not What Expected
« on: January 09, 2010, 10:17:25 AM »
Hi:

 No, the second .035 is the final release number. SO what you have should work.

( I still woulnt use the special driver unless the machien reboots with the original one..)

Art

775
General Mach Discussion / Re: Driver Test Not What Expected
« on: January 09, 2010, 12:23:40 AM »
Hi:

 The driver wont impact performance of MAch3 other than making feedrates and frequency more accurate. Performance MAY be enhanced by other fixes Brian may have done..
But in general, you shouldnt see any real change, unless previosu versions wouldnt lock in properly.

  As to the Apic, doesnt matter if your in apic mode or standard mode , most cpus still use the apic driver. Only machines that reboot on run usually require the non-apic driver. Non-apic meaning the motherbaord has no apic in the cpu chip.. most now do.


Art

776
General Mach Discussion / Re: Driver Test Not What Expected
« on: January 08, 2010, 07:07:51 PM »
Hi Guys:

 First, enevr run the specialdriver.bat unless the computer is simply rebooting when attempting to run MAch3. All the special driver does is turn off Apic usage, tring to use a
non available apic will reboot the system.

   It sounds like the .035 version driver fixes this problem of low frequency for you, so Id wait for Brians re-release of it. It shoudl be within a day or so I suspect.
Let me know if theres any trouble when .036 is released...with driver 517

thx,
Art

777
LazyTurn / Re: LazyTurn
« on: January 04, 2010, 10:59:44 AM »
Dave:

   True. You see similar outputs from some programs that dont really do roughing.. its an offset series of passes that evolve eventually yo the actualy profile
by the time the tools gets to the target profile. The problem with many of those profilers is they dont take the tool into account, so the finish pass is simply the drawn profile.
That of course doesnt work as youll collide in many spots between tool and profile.
   What Im attempting is first calculating where the tool will actually fit, that being the finsh pass, and then offsetting outwards and doing pass after pass outwards until a pass
hits no left over material. Then the order will be reversed, and the finish passes output as a toolpath.

  SO it will be posssible to simply do finish passes, but thats not a great way to rough really.. though for some they'd see no real difference in time, in theory roughing, then finishing is the way to go, the roughing tool being capable of removing more material in a pass..

Art

778
LazyTurn / Re: LazyTurn
« on: January 03, 2010, 05:37:41 PM »
Rich:

  It seems to be working. But the results are still preliminary. Im working on an algorithm to
do it faster and then I need to consolidate it to a path.

  Its amazingly complex. To take two polygons, ( a tool and a profile), and calculate how that
polygon can traverse the edge of the second polygon , where it will hit and where the optimal route is
is more complex than is believable.. I have to take into effect the possability of undercuts too which makes it a bit
more difficult.
 
   Its looking like we'll do any mixture of rough and fine cuts, rought is no longer necessary to do a fine, but then the fine
will take a great many passes, the number of final passes is dependent on the amount of material left over from the roughing.
In fine passing, you specify the final pass size as well as pass size. The algorithm will look to see when a pass hits no material,
and will make the next pass the first finish pass, so the number of finish passes will totally depend on if it is roughed or not.

  To that end I have added a finish button and removed the sensing of "finish pass allowed".

Cant promise when , but thats how its working out so far. Ill post when I have the initial test version ready.

Art

779
Show"N"Tell ( Your Machines) / Re: My new project
« on: December 31, 2009, 12:47:14 PM »
Monty:

   Thats one sweet unit, you should be very proud..

Art

780
Mach SDK plugin questions and answers. / Re: Wiimote plugin
« on: December 30, 2009, 05:27:26 PM »
Hi :

 Seems that that would be specific to the wii dll as to function, but I suspect if more than one ispresent, that the dll will create the additional arrays..
Since its a pointer to a pointer its probably simply sending you the internal pointer to that data..

Art