Advanced Search

Hi,I'm in the early stages of researching a conversion for my PM-25 mill to use stepper motors and encoders, with the goal of creating an easy-to-use system for both manual and CNC operation. Ideally, it will be a 50/50 split between DRO mode and running G-code from my CAM software.

I have experience with 2.5 and 3-axis Southwest/Prototrak systems and really enjoy using X/Y DRO mode for quick manual jobs—especially for things like reworking a part on the fly with handwheels.

Now, for my question: I came across Probe Basic, which looks like a good fit for my needs, but is it possible to have a DRO mode where external encoders on the X and Y axes feed into LinuxCNC, move the stepper motors, and display the position on the Probe Basic screen?

In short:

• Enter DRO mode.
• Turn a custom encoder on the X axis and Y axis (e.g., 100 steps maybe even a fine or course option? ).
• The table moves accordingly, and LinuxCNC tracks the position.
• If needed, I can zero out the position, similar to how old MX2 or K3 Prototraks work.

Would this kind of setup be possible? Im ok with EE and Software, can build a PCB but rather look for some options first. Thanks!

Is the X axis position getting smaller as it moves in?
linuxcnc.org/docs/stable/html/lathe/lath..._synchronized_motion

JT

how setting first time my dual Y axis at setup wizard, i has try add my parallerport pin 8 and 9 is A axis, and setting pins 8,9 to tandem Y step and dir, normal Y have pin 4 Y step and 5 is Y dir, but no working. what i need setting can use 2 motor Y axis. new version 2.9.4 old has 2.8.4.

how setup dual Y axis, just installed new version linuxcnc because i hear support dual Y axis motors, but now first time try setting wizard make tandem Y step ad dir add to pin 8 and 9 (A axis in card) no working.

i just installing ew version linuxcnc old has 2.8.4 ew is 2.9.4 and have dual Y axis problem, i try add parallerport card A axis to second motor to Yaxis but no working, how this setting, wizarrd i has make setting XYZA and pin setting 8 and 9 have Yaxis2 step and dir. all other pins have normal XYZ old setting but now try use tandem Y step and dir, to A axis. no working, how this setting ?

Post the error report here.
Did you try running the included Axis sims?
Usually Axis issues are always related to OpenGL not working, so you can try adding or removing the graphic card.
-
FYI, i have installed this 7-8 times by now, it works as advertised, meaning installs in about 8-12 minutes on some Lenovo i7 6600U and 7600U.
Also axis works always.

So, how did you get this to work:I thought it meant to add 16 to the P word in the M19 command but that does not work as only values 0,1 or 2 are accepted by the interpreter.

I hope that Kuka Robot will be enough to operate in my home.
Ac motor drive
but need installation guide and details

My network supports max imput 220vac, I am not in an industrial environment.
This may be possible but 220v input drive electricity going to the motor can be up to out drive motor 380v but I don't think it is needed because 220v 15 20A would be enough

langdons wrote:

If it works, don't mess with it.

I absolutely agree.

Had the same issue yesterday, PCI-E Sunix card, works perfectly but the error shows up whenever LinuxCNC is started.
Did not bother with it, but i did notice LSPCI does not show loaded module for it at all, but it does show all the other info with addresses and stuff.

Hi Tommy. I installed your build. It works well, loads quickly.
If in the ini file DISPLAY = axis, the screen does not load.
If this is replaced with DISPLAY = gmoccapy or with
DISPLAY = qtvcp qtdragon
PREFERENCE_FILE_PATH = WORKINGFOLDER/qtdragon.pref
it works fine. Maybe I don't understand something.
Translated in Google.

Parameter 82 did the trick! It was set to 600 by default, now I set it to 1000, and works perfectly up to 170mm/s velocity.

That's what I'm starting to realize! Thanks for adding to my confidence on this route.

I have found some good encoders - I'm thinking of going with 10000 PPR for X and Z and 800 PPR for the turret and the live tooling motor as the latter won't need much in terms of resolution, while the Z and especially X will need as much as I can get/afford (maximum count rates of A-B Ultra3000 2.5 mHz).

 

Hi all

Not sure if this is still relevant. I am using this "new" orient comp from Andy (recompiled it as orient2). And I have to say, this actually works great!

The only thing I changed is: uncomment "is_oriented = 0" (otherwise I was not able to run multiple M19 commands in a row).
This changes the behavior of the -is-oriented pin --> So i use the oneshot function to make the signal stay true longer and activate the spindle brake and some other stuff. Might add another input to the comp, so the i"s-oriented" pin can be reset with M5 or an other signal...)

Before I saw this, I had to use tallas83 idea to orient a spindle (which requires much more signals/pins  & connections).

This should be added to the main fork in my opinion (maybe this was already done)?

One improvement in my setup would probably be to run the indexing only once (and then change the mode to 0) and after that do a few orientation commands. That should make it a bit faster as a constant rehoming is not necessary after every orientation (espescially if the spindle is not running in velocity mode in between).
 

It works well in text mode.

I don't think there would be any Mini ITX Boards with onboard GPU and we don't have the space for PCIe GPUs in the system.