Advanced Search

I was a bit busy with other work, so I didn't respond to your answers earlier.
The barcode has 2 series of numbers with 5 characters x+y, I can do that in the plc controller, but only the positioning is the hardest part for me, that's why I thought that maybe there is a solution, for example in linuxcnc, which is much better for positioning.

jtrantow - Good to hear from someone with the same hardware to convert. I think what I will try first is a slotted disk with as many slots as I can reasonably fit on it with one deeper slot and 2 optical slot detectors. It may wind up less slots than you have and since I would only have one detector reading them, I will have less counts per rev but will see how it goes. I like the idea of the slot detectors because they don't have any moving mechanical parts like a rotary encoder. It should also be less involved to implement than a rotary with the sprockets, belts, brackets etc. Maybe I'll wind up with a rotary but I'm going to give this a try.

Thanks Again.

Thanks for the reply PCW. I guess I will go with a system that has an index and also at least some number of pulses per rev on an additional channel.

Originally all 50 pin FPGA cards were made to be pinout/functionally compatible with OPTO22
relay modules. These are all active low. Some 50 pin cards have plug-in pullup resistors that
you can reverse to change from pullups to pulldowns.

Its also a side effect of Xilinx FPGA characteristics where you can define pre-configuration
pullups but not pre-configuration pulldowns.
 

The ping times look OK but 6000 is not really enough (60000 is one minute
and a more reliable indicator of timing issues)

Note that 184004924 hm2_7i96s.0.read.tmax means about
6ms delay (at a 3 GHz CPU clock) which is why you would
get a watchdog bite.

What host Ethernet chip do you have?

lspci | grep -i eth

Should show this

Have you run a latency test on the PC?

Another question..
Why mesa fpga cards have pullup resistors ?
If i have breakout board with relays that the inputs are active high
when linuxcnc is closed mesa fpga outputs +5v to output pins
and it enables breakout board relays which is unwanted behavior.
Why not have pulldown resistors ?
For inputs this is not a problem because i can read gpio.000.in_not
also for outputs can do gpio.010.invert_output true
but this is when linuxcnc runs when fpga card is powered without
connected with linuxcnc what can i do ?

I am using byte2bot, and my XY axes are based on a CoreXY system.Right now, I’m trying to use homing, but when I enter the system, I can only use the XY axis after the joints are homed. However, I am unable to home both joints at the same time.Is there a way to skip joint homing and directly enter the XY system, then perform homing from there?
Like the attached picture.

Hallo PCW, 

vielen Dank für deine Hilfe

der Befehl hat folgenden Output 

cnc@cnc:~$ sudo chrt 99 ping -i .001 -c 6000 -q 10.10.10.10
[sudo] Passwort für cnc: 
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
6000 packets transmitted, 6000 received, 0% packet loss, time 5999ms
rtt min/avg/max/mdev = 0.066/0.078/0.143/0.007 ms

Bezogen auf den Takt von 1ms sind die Ping Zeiten ja eher gering. 

Was sonst kann den Watchdog Fehler auslösen?
Aus dem halcmd show param *.tmax sehe ich die Werte für read.tmax und write.tmax sind ein vielfaches höher als alle anderen Werte zusammen. Deshalb die Vermutung die Ursache liegt in der Verbindung zur Mesa Karte.

Grüße 
Erwin

 

rodw live view. Hopefully Alfred turns out to be a whole lot of not much.
Live View

what i found out in the meanwhile that at the time where the cyclic of do_homing() seem to be stopped, one of the synchronized joints is still in status "PK_PEAxisState_axHOMING_BACKING_OFF". but it allway seems to stop when the status changed to PK_PEAxisState_axHOME.

in that cas it's legit that one of them is still not homed, but for me is still unclear why the cyclic calls of do_homing() are being stopped.
the other miracle is why the flags of both joints are set to:
.homed = 1
.homing =0

edit 7 new findings:
i now tried to workaround the problemb changing the home Sequences so that the Y will get Home sequence 3. and X&X2 get home_sequence -2: that endet up that now the joint for Y doesnt get homed (i mean halui.joint.2.is-homed still shows 0)
   
that seems that it is not related to the synchronized homing sequence of joint.0 and joint.1, but more likely to the last sequence that is being homed.
and also logging showed that the cyclic calls of do_homing() (or all calls to home_comp) are being stopped right at the moment when the PulseEngine Status changed to 10 (= homed). 

as i'm quite sure that Linuxcnc motion or Halui know nothing about PE_AxisState, i think it is not the status change itself but something related to it, but i didnt see the debug message message. that do_homing() returned 1. so it is most likely something else

Yeh, I saw you had been there. Its still very normal here and Alfred has decided to be a day late.
There is some pretty rough weather to the south of us even though we are closer to the crossing point

M4MazakUser wrote:

Have you checked squareness of the part, using a micrometer measure the height in the 4 corners. It dosent look like a machine problem more like a clamping/squareness or misalignment issue. Unless you are loosing steps....

Indeed, today I checked the perpendicularity of the clamp and the truth is that it was not right, that is why there is this misalignment in the piece. I have aligned it and now it works perfectly.

Thanks! 

ugh. haha

if i know it was gonna be this disorganised i would have not bothered. I though there was a pretty clear instruction path.

I've been developing a new GUI that was originally based off of QtAxis as a starting point.  I'd like to contribute it back as an example UI in official LinuxCNC QtVcp, but I wanted to ask first about whether that was generally encouraged or not.  My GUI may not be 100% ready for prime time yet, especially in terms of being completely generalized for any type of machine config/axis count/etc.  If new GUIs are indeed welcome, where is the bar set in terms of being fully tested and wrung out before inclusion?

 

hey rodw is it ok to post the link of your youtube live view?