Anyone who is interested in this project, here is a link to a video up the UI making some cuts https://youtu.be/qyyjcHG_G4M
On Monday, September 24, 2018 at 1:41:45 PM UTC-4, Travis Gillin wrote: > > Hi Chris, > > This is not a special version of Machinekit. This is merely a GUI like > Axis, Touchy, Gmoccappy, etc. None of the currently available UI can run > without X to my knowledge except for some Text based UI's. This makes > running machinekit and controlling it on RPi or Beagle Bone without a > remote display tough. Until now, as far as I know, it is most popular to > run machinekit on embedded hardware as you explained via an > HTTP server/client setup which requires another device for the display. You > can run axis. gmoccapy, etc from inside X (even over the network via ssh) > but it is awfully slow and very impractical for commercial applications. My > goal is to solve this issue, we want to use the onboard video > capabilities of an embedded platform as the display interface by making the > best use as possible of the hardware it has. By cutting X out of the way, > we get rid of a whole lot of bloat and have direct control over how we > render to the display. > > > On Monday, September 24, 2018 at 1:23:28 PM UTC-4, Chris Albertson wrote: >> >> One question about a GUI that draws to the frame buffer: How do you >> share the screen with other software? Here is a scenario. You boot the >> machine and I guess you get to the command like X11 is not started, Next >> you run the special version of MK that has the buffer writing GUI and you >> see the program start and then write to the screen. But now you want to >> copy a G-Code file over the network. How do you start a terminal window? >> I assume you'd need a second computer or an iPad and login in via ssh. >> >> I've had the same problem, you have a tiny micro controller, smaller even >> then a Raspberry Pi and you want to put up a display but the computer lacks >> hardware. In those casesI like to use HTTP. Basically I build a tiny >> micro-size web server in to the device. Most WiFi routers do this and >> many ink jet or laser printers too. The user sets them up using a web >> browser. >> >> On Sat, Sep 22, 2018 at 11:10 PM schoo...@gmail.com <schoo...@gmail.com> >> wrote: >> >>> HI Travis, >>> >>> I will be interested to have a look at this later. >>> >>> The includes you want should be in the flavor package >>> >>> >>> https://github.com/machinekit/machinekit/blob/master/debian/machinekit-rt-preempt.install.in#L4 >>> >>> We don't have a -dev package and each kernel has a specific sub package >>> which also contains the includes etc. >>> >>> I suspect you may have just installed machinekit, whereas you need 'apt >>> install machinekit machinekit rt-preempt' for instance. >>> >>> I will check the package contents later, but see no reason why those >>> would be missing. >>> >>> regards >>> >>> On 9/22/2018 8:07 PM, Travis Gillin wrote: >>> >>> I'm working on a GUI that's meant for embedded applications with fairly >>> low resources. It's C and C++ based and runs entirely without X, deals >>> directly with the framebuffer and evdev for mouse & keyboard. (Touchscreen >>> also supported) >>> >>> I have a post here about it >>> https://forum.linuxcnc.org/41-guis/35225-new-gui-for-embedded-systems. >>> I posted here to figure out how to talk to LinuxCNC via C (libNML) and this >>> has all been figured out most part. My trouble now is when I try to build >>> against machinekit, there is no /usr/include/linuxcnc. (or >>> /usr/include/machinekit either) Specifically I need "<linuxcnc/emc.hh>" & >>> "<linuxcnc/emc_nml.hh>" equivalents for MachineKit. I know this project was >>> forked a while ago but I believe the NML interface is the same. Could >>> someone here point me in the right direction? >>> >>> Right now the GUI runs on LinuxCNC on a regular Intel-based PC just fine >>> and the only hang-up in migrating to our ARM platform is this little >>> difference between LinuxCNC and Machinekit. >>> >>> I think this GUI will be a great addition to this project because it >>> will allow people to use HDMI or virtually any type of display from Beagle >>> Bone, Rasp Pi, or other embedded devices that Machinekit has been ported >>> too and not have the "click and wait" lag. >>> >>> Thanks, >>> Travis >>> -- >>> 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 machinekit+...@googlegroups.com. >>> Visit this group at https://groups.google.com/group/machinekit. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> 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 machinekit+...@googlegroups.com. >>> Visit this group at https://groups.google.com/group/machinekit. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> >> Chris Albertson >> Redondo Beach, California >> > -- 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 machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
