Advanced Search

The closed form solution from the Frego paper only works if the clothoid starts with curavture and torsion = 0 aka from a straight line. So for our usecase this can not be used in all situation, only if we we want to connect to a straight line and not to arcs or splines etc.

Thanks for the new paper, I will read it later.

Hobby 3-axis mill, Raspberry Pi 4B, official download - reports as Gmoccapy 3.4.6.
Done several jobs since swapping from AXIS.

Running code - then stop.
No pop-up messages.
Found the Gmoccapy Log - nothing.

Cancelled job, but machine would not jog.
De-activate controls (Green/Red PB), then activate - machine jogs.

Need some hints on where to look, or a list of typical problems.
Thanks,
John.

 

Aciera wrote:

Oh, I just realized, 'pyvcp' panels are for the AXIS GUI.
Gmoccapy uses 'GladeVCP'
linuxcnc.org/docs/html/gui/gmoccapy.html#cha:gmoccapy
 

Ok, not sure how I do that as I used the stepconf wizard to create the config files and it created the pyvcp files.
Do I need to install a different version of linuxcnc if so which one as I just selected the latest 2.9.4 version?

Thanks again for taking the time to help, I really do appreciate it. 

You are of course free to try, all you need is on github. And I am happy to answer questions if there are any.
I just have no working experience with this card.
I did run the previous version in my lathe, so it is does work. I just want to see it work for hours before I put my stamp of approval on it, and it hasn't run for hours.
I do have working experience with other cards, I run the latest EaserCAT-6000 in my plasma cutter and it works just fine for hours, so the concept is validated.
 

Oh, I just realized, 'pyvcp' panels are for the AXIS GUI.
Gmoccapy uses 'GladeVCP'
linuxcnc.org/docs/html/gui/gmoccapy.html#cha:gmoccapy

If you are not loosing steps, like the spindle end up in a different position after you are done, I would guess something mechanical.
45 degree rotated ellipses reminds me of backlash.

I obviously forgot to rename the signals.
motion-type isn't used anymore, so naming should be:
tool-number-s32 and tool-number-float.

Thanks JT, this might be exactly what I am looking for. And is very well documented with many youtube tutorials.

I did manage to get the demo up and running. Will keep you posted about the progress in the next few days.

Thanks all for the help!

Lcvette spent a few hours helping me last night and I learned a ton and made notes and screenshots so that I can do it again later, if needed. The linux kernel was not a realtime version, after following the install directions, so he guided me through fixing that and manually setting the network card and doing auto login for debian. I had done last two items before but did not remember how, and I had no idea how to fix the kernel, but did realize it wasn't listed as rt when seeing it while working through different screens. It was great to have someone walk me through doing it in a way that I knew would be correct. I mention all this so that if someone else finds this thread and has the same problems, they can learn a little more about their situation.

Now, my system is up to date and I was able to get a working Axis installation going. It all seems to run properly, but my ping to the mesa card is high so I will make a new post to ask for help with that (it isn't stopping me from continuing work on the machine setup).

The next steps are to copy the sim.var file and then to copy other files and folders from the machine setup directory.

My "machine setup directory" is missing “user_buttons” folder and the pbsplash.png file.

The left is my folder and the right is from the instructions page for installing Probe Basic.

 

Could I please get firmware for the 7i92 + 7i85 with the index-enable signals and a PWMgen? I've got the control box lying out on the floor until I can get the new firmware going. Thanks!