开云体育

Hi All:

Version 4.0a is online. It will be moved to 4.0's slot as the new lockdown
when its tested. It is also possible to have OEM button calls to the button
functions Run, Pause, Rewind...ect so they can be hooked to an OEMInput
line.
Les Newell's Pipe version of KeyGrabber is in the relase but untested..
.We'll see how it goes. This is an extra thread which control message
passing in its own thread, so should be faster.

A box has been placed around the MDI window to aid in visability, the IJ
mode on the diags is fixed as well.

Olivier's french screens have been updated. The Rutex tuner has a port
selector. The OCX is now functioning properly from VB as well.

I have kept the changes low until it actually locks down properly, I will
then begin more major modifications as I won't have to worry about the
lockdown being too buggy. I have had very few problems with 4.0, even though
many have upgraded for the first time in a long while...

Thanks,
Art
www.artofcnc.ca

Hello Art,

Can you please post the sequence needed to initialize the OCX
Maybe some demo code you used to test the OCX.
I can use the OCX in VB without crashes, however I did not get any
motion yet and after a while I get "out of memory"

Any help will be gratly apreciated

Best regards
Peter



--- In mach1mach2cnc@..., Art <fenerty@a...> wrote:

Hi All:

The OCX is now functioning properly from VB as well.

Peter:

I don't use VB myself, but Les Newell sent me a test vb application that
will do movement perhaps if you ask him he'll release that test skeleton for
you. You need to

1) SetProfileName( "name" ) // this sets the profile name your going to
use.
2) LoadLayOut( "Name ") // name of the layout screens it will use..
3) InitEngine( ) // this initializes the engine...
4) StartEngine( ) // this starts the engines timer facilities.

At this point you can do movement as long as you press whatever Reset
button you have on your screen.. The is a function called SetHandle( hdl )
that you may have to call to set the windows handle of the window which will
display the loaded screen set. If you don't wish to use the screens at all,
then there are a few other calls you need to make to reset the engine and
monitor its status. Its easier, since your user would need a rest button, to
at least create a screen with just a reset button and indicator on it, and
display that small screen in a button or editbox in a vb form. That way you
don't have to worry about the estop and such. This is only necessary if you
don't intend to load any screens...

I don't know whats causing your out of memory error though, unless your
queueing up moves without the engine running or something...

Good luck,
Art
www.artofcnc.ca