- Posts: 5712
- Thank you received: 0
Linux Mint - PlasmaC upgrade confusion
Can you add a M5 $0 after the G1 X0 Y0 and see it there is a difference?
Does it give the following error after a run with the torch disabled?
I won't see the reply till tomorrow, off to bed...
Please Log in to join the conversation.
Please Log in to join the conversation.
phillc54 wrote: There is no torch off signal in that code, this seems to indicate it is not a M5 error then.
Can you add a M5 $0 after the G1 X0 Y0 and see it there is a difference?
Does it give the following error after a run with the torch disabled?
I won't see the reply till tomorrow, off to bed...
Like this? It still trips at the end.
Edit to add, I'm only running with the torch disabled right now.
Please Log in to join the conversation.
- snowgoer540
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
Mud wrote: Edit to add, I'm only running with the torch disabled right now.
Interesting, I only see the problem when the torch is enabled. I will try to run your code and see what it does for me here.
Please Log in to join the conversation.
Mud wrote: Ok...I'm now in Mint 19.2 with kernel 4.19.106-rt44-lcnc and 2.8.0. Same problem of joint 3 following error (triggers on the arc out of the circle shown), irrespective of IPO cycle time of 1ms or 2ms (and I tried halving P). The halcmd tmax values are now lower though.
Since it's now a fresh install I'll double-check everything again, but it seems I'm back where I was (albeit less legacy to worry about).
I'm assuming I'm going to be very embarrassed by whatever the problem ends up being...
Is it worth me trying to use the 7i96 with the Realtek RTL8196/8110 PCI NIC?
I would say that you have solved the real time issues so there's no point it using a different NIC
Is Joint 3 the Z axis?
Can you post your ini file?
Please Log in to join the conversation.
Should I be getting the line 'Segmentation fault' on running this mesaflash command?
Please Log in to join the conversation.
FERROR = 0.0051
MIN_FERROR = 0.0025
These are too small. I'm surprised you don't get following errors on all axis
Try .05 and .01
The Segv is because you have an old version of mesaflash
Please Log in to join the conversation.
edit: still getting the error unfortunately.
Please Log in to join the conversation.
The only function of the ferror limits is to stop the machine if its out of tolerance
or its trying to runaway due to misconfiguration or hardware fault.
Setting the limits too narrow is going to result in nuisance following errors
due to minor timing variations or sub optimum tuning.
If you still get the error on joint 3 it may be that joint 3 is being asked to do something it cannot.
That is, the commanded positions violate the acceleration or speed constraints of the
stepgen. This may require a halscope plot of the joint commanded and feedback positions
along with the following error to see what's going on.
Alternatively you could just set the joint 3 following error limits to large numbers (say 10 and 10) and see
what happens...
Please Log in to join the conversation.
