reading Pokeys pins

[ArtF]

Gary:

  I think I see many of your script  errors. Many lines of the Gcode header include lines
such as

{0.25 inch} in the comments. In Auggie , when it see's a {} in the code, it thinks your
adding a Cscript. Scripts can be mixed with Gcode in Auggie by adding any script call
or special function to the file inside {}'s.

However.. these are inside a comment, and I will see about turning off
script recognition inside a comment block. I hadnt had that error prior
to now so didnt see it.  The errors though wont affect the run, they just
trigger a lot of warnings while loading the file. Ill fix that little bug up first.

Art

[ArtF]

Gary:

  Ive fixed the scripting errors on load, Scipt "{}"s will be ignore if inside a comment.

I need your screenset to test with your dialogs though. I have your panels, but in the Screens folder
should be the screen you have setup using those panels.Can you drop it here?

Thx
Art

[gburk]

Ok Art

Here's the screen

Hope this helps...

I see the {} in the gcode so it's not being ignored event though it's inside () I think that  I used victric to generate that gcode I looked at cambam and sheetcam it doesn't look like they put the {} anywhere in the gcode
I removed the {} from victric's post processor so shouldn't add to gcode now..

I know the scripts are a mess keep adding and changing so go easy on me :)

Thanks gary

[ArtF]

Gary:

I haven't updated the program yet on the web, so only after next release will it ignore the {}'s.
Ill keep back any release till Im finished analysing your screen..

Thx
Art

[ArtF]

Gary:

I just uploaded Auggie 3.6b , test it and see what it foxes and what it doesnt.

  You shouldn't get that dialog anymore, it will skip that call if the axis position was just changed
by a script call such as your scripts. The Dialogs will not have any more than 1 OK and cancel
button combination.  I dont seem to have a problem getting motion right off if I press for a Z-Touch
or such. Let me know whats going on and we'll go from there.

Thx
Art

[gburk]

Art

I Still seem to have to run the scripts first for the toolbuttons and probe to work or there's no motor movement, and also the dialog to continue still pops up on some m6 calls

and I am getting no free axis movement with the freerapid now at all...

I am going to move all the code to another computer and see if I get any better results...

thanks gary

[ArtF]

Gary:

>>I Still seem to have to run the scripts first for the toolbuttons and probe to work or there's no motor movement, and also the dialog to continue still pops up on some m6 calls

  Can you give me a sequence here. For example, you start program, load a Gcode file, then what is the sequence where nothing happens?  What button do I need to press to simulate what your doing? Do I need to load a file to see this or doe yours not move if you simply press the Tool#1 button for example?

>>and I am getting no free axis movement with the freerapid now at all...

  I havent touched anything on the freeaxis. Other than dialog changes and scripting errors I havent
modified anything to do with freeaxis settings.

>>I am going to move all the code to another computer and see if I get any better results.. .

  I cant see that making much difference, the Freeaxis is probably some configuration thing.
Do you get any error when trying to turn on a free axis?

thx
Art

[gburk]

Art

You are right same results on different computer..

I boot auggie, and I do not load any g code files, I hit estop and then hit tool1 button I get all the print messages in the script but no movement.
then I try the z probe button same results.

now I load the lib for toolbuttons and run the script and now I get motor movement fine.. but no freerapid movement only x y z..

now I hit the z probe button again still no movement...
so I load the  probing script and run it, and now I get z axis movement..

make any more sense

also don't seem to be able to get free axis movement at all now in simulator or motion mode..

The auggie dialog to continue seems to only happen while running g code file on a T M6 line

Thanks gary


Thanks gary

[ArtF]

Gary

  I found an issue in script init sequence. So now, using your scripts and panel,
I start up, press Tool #1, the freeaxis move as I assume youve told them to,
and the z axis probes.

  Ill put this online tomorrow and we'll see where you stand then. Nothing Ive done
affects the Free axis though, and before I fixed the init, the free axis only moved
when I pressed the button.  So Im unsure why your free axis have stopped.. check
their config..maybe you changed something in testing..

Art

[ArtF]

Gary:

New version is online that should correct your scripts not starting up.
I tested by simply starting up, and pressing tool#1 button. All involved axis
seemed to do what they should including freeaxis.

  Let me know if this seems to fix most script items. Your dialogs should only
have proper OK and cancel buttons, and motion should be possible right
after startup.

Art

[gburk]

Ok Art

The startup works fine now boot auggie and hit estop press tool1 and x y z run fine. and z probe
But still no free axis's moving I checked the config and it looks good for all 4 of the free axis's don't see any changes..

I tried running Engine.FreeRapid(null,3,2,null); alone from the script window and run it, but there was no movement...

Thanks gary

[ArtF]

Gary:

  Do you get an error if you use FreeSetAxisType(..)?

In the pokeys softwares config for its engine, did the 3-axis checkbox get checked.That would switch
it to a 3 axis controller with no freeaxis.

  Did this happen in testing or immediately after one of my updates? Shouldnt be too hard
to track this down, though I may have to add a couple log mesages to trace whats happening.
Mine seem to run fine as soon as I press Tool#1 button.

Thx
Art

[gburk]

Art

That was it somehow pokeys config was changed, auggies was good, so fixed the pokeys config and now the free axis is working..
I'm thinking mach4 must have changed things in the pokeys config..

Sorry for not checking that..

Is there a way to have the free axis wait for motionstill the block("MotionStill") doesn't seem to wait for the free axis to stop
so the free axis is moving and the next script line is to move x y z and it starts and finishes before the free axis 6 and 7 finish moving..

I am not clear on what you meant to only use the ok cancel buttons in the dialog, you don't want me to call a function with a button I created in the dialog ?.

Thanks gary

[ArtF]

Hi Gary:

>>That was it somehow pokeys config was changed, auggies was good, so fixed the pokeys config and now >>the free axis is working..I'm thinking mach4 must have changed things in the pokeys config..

  It  probably was. Mach uses the Pokeys with a different paradigm, it contains the config inside mach and programs the Pokeys to match. Auggie expects the Pokeys to be configured and doesn't store its
information for the most part. It does keep some and will reprogram a bit, but mostly leaves the pokeys
as it is, which allows it to use any Pokeys without regard to type as long as it has a motion engine (internal or external). Some of the configuration changed after Auggie was written so there is a bit of a problem if
your switching between programs, but if you get used to what changed, its usually only 1 or two settings. If you get a warning that your pokeys isnt the same as Auggies config, it may be safer to select "Use Auggies data" and then check the pokeys config if anything doesn't seem to work. If you change the PoKeys config using their software, make sure you "Send to PoKeys" to keep it saved on the device. I dont switch anymore,
my 2 machines in house are runnign Auggie, and I run Mach3 in my workshop, so I dont run into this, but
when I did share between Auggie and Mach4, I got used to what changed and coudl quickly refix for Auggie by running Pokeys and changing one or two settings.

>>Sorry for not checking that..

  lol, no problem. Its all very complex really and you've dug in very well I think. Almost all of your troubles
were in the end my fault as the functions for them were never tested in the context of general cnc , but mostly only on lasers. Ive used Auggie hundreds of hours on Lasers so I knows its operation is basically
sound and does great motion, but as your probably one of the first to get this deep into general CNC
youll probably hit more things as you go. Ill fix them as I can find them, but always keep in mind
Auggie was meant to be a simple controller, not as complex as Mach3. (Though to be honest its damn near that complex as myself and YaNvrNo went a little nuts while we tested and developed it. For a free
controller its fairly powerfull for Laser use. ). I typically run these days at 25000 mm/min which is pretty
fast for what its doing. I never planned on offsets , which really complicate a planner and which CAM does
better in my view, nor did I allow for G43, though to be honest it is there, just mostly untested.

>>Is there a way to have the free axis wait for motionstill the block("MotionStill") doesn't seem to wait for the free axis to stop so the free axis is moving and the next script line is to move x y z and it starts and finishes before the free axis 6 and 7 finish moving.

  Yes, use "FreeStill" to block on, you can block on either or both. If you command a freeaxis move and want to wait for it, just block on "FreeStill" instead of "MotionStill". The 4 "free" axis are simply a duplicate of the
first axis planner with a few changes such as being able to configure any of them to be constant frequency
outputs. This can lead to some confusion due to the amount of variation possible in the configuration of
these. You can double these up by the way, it should be legal to execute a

Block("MotionStill");
Block("FreeStill);

  in a script, or you can make a global script , name it WaitForAllToStop() and put those two calls in it. 

>>I am not clear on what you meant to only use the ok cancel buttons in the dialog, you don't want me to call a function with a button I created in the dialog ?.

  No, I was only referring to the fact your error dialog , once opened, added another OK and cancel each time it opened, so I ended up with 10 OK's and 10 Cancel buttons on the dialog at once. This is repaired and only 1 OK and Cancel will ever appear at once. Ignore this if its never happened to you, its just something I noticed while testing your scripts.

  So, at this point add your Block("FreeStill") after your rack calls and such and it will wait till their done
to continue.

  Looks like your getting close anyway. Im not able to test exactly as you do as Im not configured exactly
as you but I can usually synthesize an error if you can explain it to me sufficiently.

Thx
Art

[ArtF]

Gary:

By the way, Id recommend instead of using your tool panel the way you do, just instead use the main screen
and edit the 4 axis panel to add your toolpanel as one of its subpanels. That way it wont have to shrink the
screen to open up and just selecting the tab that will show up will get you immediate access to the toolchanger buttons without the screen having to reconfigure.
  The scheme your using is instead similar to my Diags panel which also annoys by shrinking the screen
when it opens. Ive since learned its better and easier to simply add new panels as subpanels to
panels already on the screen. Auggies editor is better than Scream4, but still has its annoyances.

Just an FYI.

Art