Advanced Search

 



jungle boogie is my preferred ...

martin2day wrote:

If the manual is right, can I also connect the analog Driver with encoder output to Linux CNC an make a closed Loop?

Both of the drives have encoder outputs so both can be used to close the loop in LinuxCNC.
If you are eager to get the boards and start wiring, i would go for the Mesa 7i96S with a 7i85 and 7i83 for now and add a 7i84 or two later for more inputs and outputs. This makes it possible to control both types of drives, the step/dir ones and analog ones, even a mix of any of those at the same time.
It is a bit more pricey that say 7i97 for analog or 7i95T for step/dir, and maybe a 7i84, but leaves a lot of options open to expand as you see fit in the future.

Oh, i have to check this, tank you.
The Driver is an Maxsine EP100-3A, this I know exactly... but if the Knuth electrical drawing is right, I don't know... I find many errors there.
So I have to check it.

If the manual is right, can I also connect the analog Driver with encoder output to Linux CNC an make a closed Loop?

Martin

btvpimill wrote:

I had a part that was a little too deep, so I pressed stop and guess what? It plowed through my part before stopping. So that was a $2000 part before we machine it. Turned to trash because something is not right.

To late, but, never ever do production work on a machine that is not tried and tested to function properly.
Can you please attach the hal and ini file you are using here?
In the meantime, check the ini file for "pause_position or tollchange_position" or something similar that would cause such an issue.
Also, does the machine move to the same spot when stopping the execution?
Take some screenshots of the position in DRO before stopping the program and after stopping it and upload those here on the forum.
A video of that happening might also help, use youtube and link here, if you can, or google drive.

On the Mesa configuration page in PncConf, set the encoder number to 0, then it will show input pins so you can select them.

no, it would interfere with the mdi tab widgets which are already compressed for the gcode window there. I have a large machine vmc and have not had any issues with the back plotter size, but i could see a large format router perhaps being a bit of a problem. perhaps you could add a large full screen plotter in the user tab to suit your desired needs!

Not the same drives, pretty sure, this one is step/dir only, the above is analog only.

It's a bit of a mystery for me. A ftdi adapter could help to give some more information. Maybe firmware is missing or a driver is as module but should be built in. When you boot from the sd-card with the rt kernel, the nvme is still recognized? If so, can you show the output of blkid and of dmesg after boot and lsmod?
dmesg > dmesg-output.txt
lsmod > lsmod-output.txt
blkid > blkid-output.txt

did you completely uninstall the previous versions of qtpyvcp and probe basic? key error sounds like you may not be getting everything installed correctly or like you said may have some odd security conflicts with your network setup. i would completely reslve those and then report back if the problem perists.

When it gets to that error:
-remove the USB
-wait 15 seconds
-plug in the USB
-wait 15 seconds
-press or click retry

so what is the error message you get? and does the sim open?

Hello,

thank you... I also have an PDF oft the AC-Driver:
 

Martin

Hard to see on the PDF and my glasses, but those look like analog drives, not step/dir so 7i76E would not be the best option.
Can you take a picture of the drives where the pin naming is?

not had this experience and probe daily on my machine running the latest version. sounds like your machine is not properly setup. if your configuration files are setup correctly according to linuxcnc docs and you are seeing probe input activation in halshow than probe basic only needs to have the probing and tool setting parameters correctly entered in order to function as expected. i would start with you config files and get that sorted first!

I'm not sure how this can be done with the PncConf, it was what I tried first. The extended behavior of the pins in the wizard is set to Quad A/B these can't be selected as inputs for limit switches as far as I can tell. The g540x2 firmware is closest to what I need without having to do a custom version.

I mapped the inputs from the card manually to the same nets same as the parport config and confirmed they are activated by the switches.
net home-a <= [HMOT](CARD0).gpio.014.in_not
net home-x-y-z <= [HMOT](CARD0).gpio.013.in_not

and pass these through to what was generated by the PncConf but not sure where to go from here.

Even if I had the HAL setup incorrectly I expected it to try to move when I clicked home (I also tried individual axis too.)