I went through the JA switch with LinuxCNC when I started using a Mesa 7i96 which was only supported in 2.8pre1 not 2.7. 2.8+ will prompt to rewrite the hal and ini files automatically, but I had a PIA of a time with Python stuff because they added an extra argument to select control of the joint or the axis but didn't document it well.
I was kind of wondering about the JA inclusion into MK but seeing as how MK is super far behind in Mesa drivers and plenty of other things I'm not sure it's at the top of the list. Not sure about the remote setup but machinekit doesn't seem to like to print to the terminal like LinuxCNC does. If you set the debug level it with throw errors to a logfile in /var/log/linuxcnc.log or something like that. Might try looking there. On Monday, December 2, 2019 at 4:26:53 PM UTC-5, sliptonic wrote: > > I've made some progress on my side-by-side configuration. I can now > selectively start either LinuxCNC or Machinekit in a RIP. > The linuxCNC config still isn't working since it's at version 2.9 which > has the JA branch merge and some part of the configuration is causing > following errors. > My present configuration not withstanding, the JA changes look really > interesting, especially for my Scara robot. What's the outlook for the > JA changes to be ported into machinekit? > > My machinekit install will start and run locally on the mill with the > gmoccapy UI. > > When I try to start with mklauncher, mkwrapper and cetus, however, I get > results that I don't understand: It starts without error on the mill > machine. > I launch the client on a remote machine and it instantly finds the mill > machine. I browse for remote UI and select cetus. > Cetus launches with all controls greyed out for approximately 45 seconds. > Then the controls activate for a few seconds before greying out again. > This continues indefinitely. > > Instead of the machinekit client and cetus, I tried connnecting with > mlampert's FreeCAD machinekit workbench and get similar behavior. It seems > to find the mill machine immediately but takes a long time to > communicate anything with it. If initiate homing, the homing sequence > actually starts about a minute later. > > I'm not sure how to troubleshoot further so I'm looking for suggestions. > > Mill machine is running Debian stretch with 4.9.0-11-rt-amd64 kernel. > > > > > > > On Saturday, November 23, 2019 at 12:42:48 PM UTC-6, sliptonic wrote: >> >> I converted my mill back to linuxcnc a while back because of >> compatibility problems with gmoccapy. >> However, I'd like to experiment with mlampert's machinekit workbench in >> FreeCAD. >> >> Is it possible to install both side-by-side? (Debian stretch) >> >> Any gotchas to be aware of? >> >> >> -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/31cab058-b64d-45ec-90ab-6fe8a4f9295b%40googlegroups.com.
