Linux Mint - PlasmaC upgrade confusion

More
06 Sep 2020 09:31 #180921 by Clive S
I believe if you change the servo thread to 2ms you have to change all the P values to half ie 500

Please Log in or Create an account to join the conversation.

More
06 Sep 2020 11:56 #180967 by Mud
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?
Attachments:

Please Log in or Create an account to join the conversation.

More
06 Sep 2020 12:11 #180972 by snowgoer540

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 have this EXACT same problem I get a Joint 3 following error at the end of a circle when I create them using conversational... I am guessing you made using the conversational? I never really connected the two, but I ran several jobs before and I dont get the error. So either this is an extreme coincidence, or this something to do with making holes using conversational.

This is when I saw the Z axis offset error crop back up again as well...

Please Log in or Create an account to join the conversation.

More
06 Sep 2020 12:28 #180981 by Mud
Yes, I have only hand-coded a square for a scribe test and made conversational circles thus far.

Please Log in or Create an account to join the conversation.

More
06 Sep 2020 12:33 #180986 by phillc54
Well that is odd. Do the hand coded squares give the following error?

Please Log in or Create an account to join the conversation.

More
06 Sep 2020 12:42 #180987 by Mud
I think that code got nuked so I would have to rewrite it, but I don't think so...I ran it a few times in succession I believe.

Please Log in or Create an account to join the conversation.

More
06 Sep 2020 12:50 #180990 by snowgoer540

Well that is odd.


It's what made me look at the code, and see that Conversational holes only had M5 instead of M5 $0. I'm not sure if that could affect it or not? Maybe a place to start.

I have today and tomorrow to myself, I can toss the $0 in the same code and see if it goes away for some reason...

Please Log in or Create an account to join the conversation.

More
06 Sep 2020 12:55 #180991 by phillc54

Well that is odd.


It's what made me look at the code, and see that Conversational holes only had M5 instead of M5 $0. I'm not sure if that could affect it or not? Maybe a place to start.

I have today and tomorrow to myself, I can toss the $0 in the same code and see if it goes away for some reason...

I had that same thought myself. I can't see how it would make any difference, but you never know...
It's worth trying though.
The following user(s) said Thank You: Mud

Please Log in or Create an account to join the conversation.

More
06 Sep 2020 12:56 #180992 by Mud
This code also trips after it makes the square:
g21 g64p0.1 g40 g49 g80 g90 g92.1 g94 g97
f#<_hal[plasmac.cut-feed-rate]>

g0 x0 y0
m3 $0 s1

g1 x0 y50
g1 x50 y50
g1 x50 y0
g1 x0 y0

g21 g64p0.1 g40 g49 g80 g90 g92.1 g94 g97

m30

Please Log in or Create an account to join the conversation.

More
06 Sep 2020 12:56 #180993 by snowgoer540

Well that is odd.


It's what made me look at the code, and see that Conversational holes only had M5 instead of M5 $0. I'm not sure if that could affect it or not? Maybe a place to start.

I have today and tomorrow to myself, I can toss the $0 in the same code and see if it goes away for some reason...

I had that same thought myself. I can't see how it would make any difference, but you never know...
It's worth trying though.


I'll give it a go.
The following user(s) said Thank You: Mud

Please Log in or Create an account to join the conversation.

Moderators: snowgoer540
Time to create page: 0.090 seconds
Powered by Kunena Forum