Advanced Search

Ah yes, I forgot about those. It's been a while since I used my table or read the Qtplasmac manual.

Thanks very much.

Hi all,

Thanks to this thread I have an axis moving! 

Unfortunately I'm a complete noob when it comes to LinuxCNC and I've been overwhelmed when it comes to looking at other people's setups for how to add PID.

I don't suppose anyone has a simplified setup they're willing to share so I could suss out how it works?

Cheers 

I used AI because my english isn't that good and it explains what I want.

PCW wrote:

kworm wrote:

Thanks Tommy. The attached files will support the 7i97t.  I created a config successfully but I don't have a card to test with so maybe the OP or someone can give it a try and let me know if it works.  I can send in a pull request if it's good.   This will only work with 2.10 master.

After updating to latest master just copy the attached private_data.py file to /usr/lib/python3/dist-packages/pncconf/ and the pncconf.py to /usr/bin/pncconf

I would suggest making a backup copies of the original files first just in case.
 

Can I send you a 7I97T?

 

Hi PCW,

I will email you off list.

 

bentiggin wrote:

I just tried to create a config in pncconf for a 7i97t and I encountered an error.
Attached is a pic of the error.
I am a novice so I may be doing something wrong, I am barely sure I updated to 2.10.

 

I don't think that error has anything to do with the support I added.  I'm not sure what would cause that.

Thanks. That was easy enough!

What the difference between AI and the crazy guy yelling at the sky on a street corner, the advice appears the same.

Thanks AI
Maybe once Debian has got their money from the AI techbros they might be able to fix this.

As Todd mentioned, using a USB/RS-485 interface is likely your best option.

Although the HAL component vfdb_vfd.comp was originally designed for the Delta B series VFD, it seems that the Modbus addresses and commands are also compatible with the Delta 300 series. Since you already have everything needed to run a test, please go ahead and share your results. Your findings could be incredibly valuable to others in the future. As you've probably noticed, many users ask questions but rarely follow up with their findings—your feedback will be helpful for others using similar VFD.

linuxcnc.org/docs/stable/html/man/man1/vfdb_vfd.1.html
 

Segue o vídeo , consegui com uma placa de impressora 3d.
www.facebook.com/share/v/1BzA9DNq27/
Mas parece não ser tempo real.

Simply typing:

linuxcnc

at a terminal window should do.

Use these:

linuxcnc.org/docs/devel/html/plasma/qtpl...l#plasma:ext-hal-pin

I would change these in the ini file
from:

DIRSETUP = 100
DIRHOLD = 1000
STEPLEN = 2500
STEPSPACE = 2500

to:

DIRSETUP = 10000
DIRHOLD = 10000
STEPLEN = 5000
STEPSPACE = 5000

also:

P = 0.0
I = 0.0
D = 0.0
FF0 = 1.0
FF1 = 0.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0

should be:

P = 1000
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0 

These changes apply to all joints.
 

I've went through the pncconf wizard to set up a 7i76eu board. I can get the x-axis to job in Linuxcnc but the motors are not moving.  All wiring is connected correctly to the board and driver.  I know this because it was moving at one point and then i made the mistake of trying to swap from Axis to Probe Basic and ChatGpt was telling me to do some stuff that obviously messed it up.  So my files here are the result of going through the set up wizard a second time.  It's not the originals.  I'm essentially trying to get back to where i was.  I have communication with the board.  DMM Dyn4 drivers has a solid green light on the front of each.  The only thing of note worthy is the Z-Axis pins from the driver are connected to the Step 0 pins on TB2, X axis on Step 1 pins, and Y axis on Step 2 pins.  This is due to short cables and i don't want to move them.  I made these changes in the wizard too.Can anyone take a look at my Hal and Ini files to see any issues?  I'm attaching the files and TXT files for reading.

Linuxcnc fails at startup and just sits there.

My machine does not show the error logs unless I start from terminal.

My machine has been working flawlessly for a number of years and it seems that I have forgotten how to start  it from the terminal.

2.7 debian stretch.