Messages

21

VB and the development of wizards / Re: activate the output to the desired position of the dro

« on: April 27, 2014, 07:48:07 PM »

you can use a brain for it, see pict.

Alex

22

PoKeys / Re: Basic input function

« on: February 13, 2014, 09:41:02 PM »

Just tested latest Plugin Mach3 Ver .062 Pokeys55 ser no 10299. Win7 OS , Pokeys Firmware  2.1.23 Pokeys Software V 3.1.9b

Everything works fine except for pins 35,36,37 (PoExtBus) can not be disabled.
As I mentioned before for unused Pins Set everything to " none "  the funktion is not diabled otherwise. eg.

PIN        Function           LED          Button         IO
 
 1           not used          none           none         none         ====>    disabled

 1           not used          none      307 jogX++    none         ====>    not  disabled !!!!!   ( just found the axis starts running in this case )

Browse through all pins and check.

attached the latest Plugin for Pokeys55

Alex

23

Mach SDK plugin questions and answers. / Re: ShuttlePro V2 with ESS e-stop bug

« on: February 12, 2014, 08:23:36 PM »

Hi,
the same behavior with the USB SS.
Alex

24

PoKeys / Re: Basic input function

« on: February 11, 2014, 11:32:53 AM »

Hi Ron,
the current Plugin always enables the PoExtBus ( pins 35,36,37)  when using the old Pokeys55. No way to disable it within the Plugin.
It is fine with Pokeys56.

Alex

25

PoKeys / Re: Basic input function

« on: February 07, 2014, 03:46:08 PM »

Hi Ron,
just tested a bit around with the Pokeys 55.
It looks like LED's below 1000 didn't work, maybe the are reserved ?
from 1000 to 1999 it is fine.

The config screen shows pins 35,36,37 as outputs, and 35 keeps blinking. I have not configured anything on these pins, and the setup screen shows them as unused. Why are they active?

I would say it is a kind of bug there.

When a pin is activated then it is fix activated in the Pokeys even when you assign it as "not used " in the Plugin setup.

Important is when a pin is set to  "not used " that all funktions for that pin is set to " none " before.

After that you can open the Pokeys software and set the pin to " inactive " and sent the configuration to the device.

After that and reopen Mach all is fine.

Alex

26

G-Code, CAD, and CAM discussions / Re: 4 axis feedrate coordination

« on: January 25, 2014, 08:18:23 PM »

Did you increase the feedrate to F8000 in your G-Code ?
Alex

27

G-Code, CAD, and CAM discussions / Re: 4 axis feedrate coordination

« on: January 25, 2014, 07:26:06 PM »

Ad a G64 to your G-Code.
Alex

28

G-Code, CAD, and CAM discussions / Re: 4 axis feedrate coordination

« on: January 25, 2014, 04:14:43 PM »

Mirco,
if you put in 10.000 as you said, that's only 1G  you need at least 5G ( 50.000) to see a reasonable different. I tested with 10G ( 100.000 )
Whether it will work or not depends on your A-Axis mechanism. ( what diameter, what mass, friction, transmission, transmission ratio, and motor)
At least  you can test it.
Alex

29

G-Code, CAD, and CAM discussions / Re: 4 axis feedrate coordination

« on: January 24, 2014, 09:08:42 PM »

Hi,
forget what I said, I am stupid.   

Yes the limiting factor is the acceleration and a bit the A velocity.
With Velocity at 8000 and acceleration at 10G your attached G-Code runs in 2 minutes and 20 seconds.

You can change the acceleration by typing the value you want into the  acceleration field and klick  Save Axis Settings.
Doen't klick on the acceleration slider after that.
Alex

30

G-Code, CAD, and CAM discussions / Re: 4 axis feedrate coordination

« on: January 22, 2014, 03:40:14 PM »

Cycle time is 2:17 with  " A Rotations Enabled " unchecked in ==> Config  ==> Toolpath.
Alex