Advanced Search

Bonjour, 
Je construis une CNC multifonction avec 5 axes , et 2 axes rotatif fraiseuse et pas a pas.
J ai actuellement 2 cartes chinoises mach3 des NEMA des DM556 . Un pc DELL optiplex 7010 .
Le pc n' a pas de port parallèle, j' ai donc commandé une PCIe 2 ports puce ASIX 9865 , impossible de la faire fonctionner, elle n' ai même pas reconnue sûr le slot pcie. Sûr le slot bleu PCI+PCIe elle est reconnue "lspci -v" mais , je me retrouve avec quatre adresses.
J ai essayé toutes les combinaisons possibles dans le "Hall" .
J en ai conclu que il y avait un problème de compatibilité.
Ma question est donc :: que dois-je choisir comme système, continuer a chercher des cartes PCI ou PCIe/parallèle ou une autre solution tel que les cartes MESA ? Pour les quelles je n' ai aucune connaissance.

Merci de vos réponses 
Florent 

 

Okay, will try that when problems retturn. Thanks!

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.8
Machine configuration directory is '/home/ricco/linuxcnc/configs/mill_touch_sim'
Machine configuration file is 'mill_touch.ini'
INIFILE=/home/ricco/linuxcnc/configs/mill_touch_sim/mill_touch.ini
VERSION=1.1
PARAMETER_FILE=emc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=
DISPLAY=qtpyvcp
COORDINATES=X Y Z
KINEMATICS=trivkins coordinates=XYZ
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./mill_touch.hal
Found file(REL): ./custom.hal
Starting TASK program: milltask
Starting DISPLAY program: qtpyvcp
Can't execute DISPLAY program qtpyvcp  
Shutting down and cleaning up LinuxCNC...
task: 29 cycles, min=0.000006, max=0.012605, avg=0.005740, 0 latency excursions (> 10x expected cycle time of 0.010000s)
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
Unexpected realtime delay on task 0 with period 100000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.
3180
3212
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

Z400 are very good, so i would not change it, but in case you have issues again, try removing memory modules, never happened to me on a Z400, but happens sometimes on Z420 and happens a lot on Z600, at boot reports of memory issues that mostly disappear on their own.

How did you design the process?
You write the values for homing in 0x6041 and 
then set a bit for start homing, right?
The servo should then respond with a status bit that can be monitored.

Or I have three other suggestions that could be considered 
1. 
After writing 0x6041, read the register again and check the consistency.  Then start homing and monitor a status bit

2. 
Monitor the axis movement.
The axis must start moving after start homing.
A minimum distance could be specified here, otherwise an error will occur.

3.
Gantry version
The axis positions could be compared with each other.
If the difference is too great, then there is a malfunction.

PS: There was once a project called “Ethercat auto configurator.”
Is this still being pursued?

Today all is functioning normally again. Ran a 30 minutes program without errors. So I don't know what happened yesterday, maybe I need a new pc.

remember limit switches need to stay triggered to the end of travel.

Hakan wrote:

From what it looks like, the only way out from homing is that is finishes.
This could probably be expanded to include error states and whatever can occur.

 

Back after my IP being banned for a week! (Thanks for letting me out of Jail Andy!)
Maybe thats an oversight. the homing process is managed by  the cia402 state machine. Homing completed is returned in Bit 12 (from memory) and if it errors, that is returned in bit 13). The function of these bits are often not well documented but its really standard cia402 behaviour.

The problem is that the dongle resets itself. Basically the same as pulling it out of the USB port and reinserting it.

In the situation where you try to jog with the pendant while running a program, this is caused by a too long time during which the xhc-whb04b-6 component does not poll the dongle. This we "fixed" with the loops=10.

In the other situations that happens "randomly" after some time, I do not know what the reason is.

My original Maho wiring diagram was wrong for the EXE wiring. I also had to try other pin outs. IIRR Heidenhain seemed to always use one of two pinouts, and the other one worked for mine.

What did you find as being the problem? You probably already wrote it, can you do it again?
What is the way to fix?

New PR from YangYang is ready, hopefully will be merged soon in master

This adds ruckig in the planner type 1
if you want to test it get the binary from

github.com/LinuxCNC/linuxcnc/actions/runs/21975584400

or build source from my repo

github.com/grandixximo/linuxcnc

Testers are welcome to report here or in github, thanks!

Mekanoid wrote:

output of lspci shows no parallel port controller

 

Not sure what to make of that. I was under the impression the motherboard parallel port and any PCI parallel ports always list in lspci. Maybe someone else can confirm this. My suspicion would be the controller I.C. for the parallel port is dead...

edit:
just learned onboard parallel ports don't always list in lspci

Do you have a parport in /dev?
I would also check output of sudo dmesg

My next step would be to check the parport voltage outputs with a multimeter or oscilloscope to verify the voltages on the pins change as expected when commanded in LinuxCNC. I would do this with the parallel cable disconnected from the cnc machine.

5_Zylinder wrote:

I'd like to know why this is happening.

For what it's worth, I once worked on a machine that did a similar thing. I my case it was encoder counts. The entire system was Seimens brand electronics from the 1980's. One day they switched it on and one axis experienced runaway until following error stopped it (nearly instantaneously). We had no documentation for that machine and nothing was labeled. I ended up swapping A and B from the axis feedback glass scale encoder then everything worked again.

We assume a logic fault somewhere in the computer's many circuit boards caused the mysterious fault.

No problem, I talk to myself a lot when I'm programming.