Advanced Search

Hi, I am building a CNC adhesive dispenser. Two closed loop stepper motors will be used to control the X-axis, one will be used to control the Y-axis and one to control the Z-axis. Here are the 4 motors: P Series Nema 17 Closed Loop Stepper Motor 72Ncm(101.96oz.in) with Encoder 1000PPR(4000CPR) - 17E1K-07|STEPPERONLINE (omc-stepperonline.com) And here are the 4 drivers: Closed Loop Stepper Driver V4.1 0-8.0A 24-48VDC for Nema 17, 23, 24 Stepper Motor - CL57T-V41|STEPPERONLINE (omc-stepperonline.com) I was wondering if these motors and drivers will be compatible to interface with MESA 7i96s: eusurplus.com/index.php?route=product/product&product_id=159 and LinuxCNC. And additionally if this is the most suitable MESA card choice for my build (note that I might also need to connect up an additional motor and driver). I am working on doing this for my company (budget isn’t an issue) but I am very hesitant to buy anything without being certain that it is the right choice. And yes I have read the description that the 7i96s can control up to 5 stepper motors, I just wanted some extra clarification from someone with more experience on the topic as I am only a couple weeks deep into learning about CNC.Any help would be greatly appreciated.

Check dmesg output and search for parport.
Check lspci (-v), which ports are listed for the card.

is this the same card: forum.linuxcnc.org/16-stepconf-wizard/46...card-ax99100?start=0

pippin88 wrote:

The ideal setup is estop kills the servo drive motor power input, and spindle power input.
Most servo drives have two power inputs: control power, and motor power

Estop circuit should signal to Linuxcnc that estop has occurred.

Most servo drives will have a digital input that can be configured as estop/fault

 

Ok well on the new spindle drive that I’m working with it has something in the manual that talks about estop signal but there’s no documentation on how to use it.  The other drives for the stepper motors to the axis's XYZ have no such thing.  I really think my machine was originally so old and cheap that the stepper drives didn’t have a control power option built in when manufactured, so it was designed to kill the control board all together instead.  I might have to do the same thing here with this estop or do something at least with figuring out how to signal the spindle drive to receive the estop alert then on the control board signal it the estop function but not completely kill the power to it?

I posted this on Facebook's LinuxCNC users but figured I'd try here too:

I recently purchased a parallel port based 6040 router and at the recommendation of a coworker I'm trying to run LinuxCNC to control it and finding it problematic. I'm using a Dell Inspiron 3668 with a StarTech PCIe card (I only have PCIe slots) with an AX99100 based port. Latency appears to be about 19000, although it's mostly not more than 4000.

I downloaded the Linux driver from Asix websites, and made it, and then did the install as they suggested. It seems to install on base address 0xd010. After install of the driver LinuxCNC no longer complains about the port not being configured. I turn ESTOP off and turn on the machine (via the interface) and nothing happens. I put an o-scope on pins 2 and 3 (X direction and step) and they look like they are low even when commanded to move on the X-axis. So it looks like it's not the router here but something weird about LinuxCNC or the parallel port.

Also worth adding that for whatever reason I had rmmod the parport_pc module and reinstall after a reboot..

Any thoughts on the next step diagnose and fix?
 

Askjerry wrote:

RODW -> The pin you specified requests the machine to home, not return when homed.

ACIERA ->

I put a line in the custom_postgui.hal file...  <= motion.is.all.homed but when I run it, I get the following...

Debug File Information:
custom_postgui.hal :70: motion.is-all-homed does not exist.

The text you referred to says it should exist... but it's not there. I may have to save my configuration and update...
this is Axis 2.7.14 on this machine.


 
 

"Update: I could NOT find the signal for all homed... or any variant of it. I can find individual axis... but not "all"."
-> combine all individual axes with an and component to get all_homed bit should work

Another idea: create a simple python hal component that runs the commands after all axes are homed.
I used that in my lathe setup. It has a serial port controlled tool changer and the hal component handles tool changes. But the relevant part here is that you can wait in a loop that all axes are homed and then execute a command. Then sleep forever.
Code is here: forum.linuxcnc.org/24-hal-components/364...trol?start=20#151315
 

Ok, thank you....

A little update, I made a telescopic way cover for protect linear guide .

 

 

 

 

 

 

 

 

I made a video compilation.  I had to make an additional metal construction to level the table.   In the video you can also see a test measurement with 0.002mm dial indicator .

It won't take nearly as long as you think with modern ai tools

Go to chat gpt or any other ai

Give it your post, gcode, and explain what is not working and how tofix it. About 33% of the time it will right out the gate. 33% needs tweaking but points you in the right direction, the other third it's way off. In either case where it doesn't solve it. Ask it to explain how things work, etc

Be the 5 year old who asks the parent why, why, why, how do you do that, what does this mean, etc. you can learn a crazy amount these days in almost no time.

 

Yes, just make a new configuration for Probe Basic and leave your old one untouched.

Estop should kill power to dangerous things
This means things that cut and things that move
The ideal setup is estop kills the servo drive motor power input, and spindle power input.
Most servo drives have two power inputs: control power, and motor power
Do NOT switch the power out of a servo drive (wires between servo drive and servo motor)

Better not to kill power to control

Estop circuit should signal to Linuxcnc that estop has occurred.

Most servo drives will have a digital input that can be configured as estop/fault
When triggered the drive will actively stop the motor. This can be faster to stop than removing input power to the servo drive. There are big capacitors in the drive, so killing input power does not stop output instantly.

So mine will be setup with estop resulting in a digital signal into each servo drive AND cutting the power (using a contactor) input to the servo drive motor power inputs.
Servo drive control power stays on.

The "relays" are actually contractors
Pretty much the same.thing but designed for higher currents. Correct term may help you if need to search in the future

Ok will im all gutted an onto the reinstall. I figured id start the big red physical estop button and connecting it to one of the two relays that are available. Should I make it so the estop just kills all power to the control board(the 7i96s) or what should the the professional way of configuring the estop? I didn't pay attention to what all it shut off before I tore it apart. I do know that the motor drives stayed on even with the estop engaged originally though.

My best guess is configure it to kill the control board and kill the spindle power

sorry for later reply.

I am totally new about ARM.

I think this is what you really need. github.com/Douglas-d/MYD-AM6254/blob/master/my6254.img.gz
If it's not, I will check again.

Thank u sincerely!!!

What have you changed and what does the ping test show now?

andypugh wrote:

Cant do this anymore bye all wrote:

drive.google.com/file/d/1-akVp7OStuMzRxG...Rgi/view?usp=sharing

Here’s a link to an iso that needs testing that attempts to solve that issue
What did you change? Do you want to submit a pull request to: github.com/LinuxCNC/linuxcnc-live-build ?

Yep did that, my GitHub name is different to my user name on here. Got am email saying that it had all been accepted.