Did you know this cape https://www.necitec.de/index.php/en/cnc-cape ? It is not parport but should be able to drive a g540.
Am Montag, 26. März 2018 16:52:48 UTC+2 schrieb mrarmyant: > > Do you have your config files for this or pinout information? I have a > g540 and bbb I want to get running but no one makes off the shelf paraport > capes anymore so I'm diving head first into my first linuxcnc/corexy > project lol! > > On Wednesday, November 1, 2017 at 12:09:24 AM UTC-5, Jerry Trantow wrote: >> >> It seems like there is a missing step for configuring the cape??? >> >> http://www.machinekit.io/docs/getting-started/getting-started-platform/ >> show a choice of installing Images, Packages, or a Development Platform. I >> have a home built gantry router/G540 that I originally controlled using >> LinuxCNC from an old Laptop and recently controlled with BBB MachineKit >> using the Comet Metric configuration using Images upto and including: >> 2017-10-02 - Debian 8 (Jessie) - MonthlyBBW/BBB (All Revs) >> MachinekitmicroSD/Standalone: >> (machinekit) Based on Debian Jessie with 3.8.x kernel >> >> I have been using Axis running on the BBB and thought it was about time >> to try some of the other GUIs. Before I took this leap, I figured I would >> update to a newer Jessie version. I thought there would be little risk in >> updating to one of the image snapshots, but I have been stuck for the last >> several nights trying to get the following image to work. >> microSD/Standalone: (machinekit) Based on Debian Jessie with 4.13.x >> kernel with U-Boot Overlays >> >> I have my BBB GPIO directly connected to the G540 parallel port cable, so >> I don't have any external cape. I thought everything would be ok as the >> cape-universal should load by default? But running machinekit straight from >> the latest Image this is not the case. >> >> In the terminal window, I see >> MACHINEKIT - 0.1 >> Machine configuration directory is >> '/home/machinekit/machinekit/configs/ARM.BeagleBone.Probotix' >> Machine configuration file is 'Comet_Metric.ini' >> Starting Machinekit... >> io started >> Unrecognized line skipped: POC FMS LEN DIAM COMMENT >> halcmd loadusr io started >> grep: /sys/devices/bone_capemgr.*/slots: No such file or directory >> Loading cape-universal overlay >> bash: /sys/devices/bone_capemgr.*/slots: No such file or directory >> *Error loading device tree overlay file: cape-universal* >> Comet.hal:5: program './setup.sh' failed, returned 1 >> Shutting down and cleaning up Machinekit.. >> >> It seems like there is a step in the install directions missing for the >> latest kernels? >> >> The directions at >> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Loading_custom_capes >> didn't make sense to me. >> First, I tried adding each of the following line to /etc/default/capemgr >> with no success. >> CAPE=cape-universal >> CAPE=cape-universal-00A0 >> CAPE=cape-universal:00A0 >> >> Then I looked up and tried to follow some device tree tutorials but I >> don't even see bone_capemgr in cd /sys/devices/bone_capemgr.* >> Some tutorials mention /mtn/boot/uEnv.txt >> >> In /boot/uEnv.txt, I verified enable_uboot_cape_universal=1 and tried >> adding cape_enable/cape-universal >> ##Example v4.1.x >> #cape_disable=bone_capemgr.disable_partno= >> *cape_enable=bone_capemgr.enable_partno=cape-universal* >> >> But, I am still stick with "Error loading device tree overlay file: >> cape-universal". Shouldn't this just work with the machinekit image? What >> do I need to do to setup the cape-universal device tree overlay. Any help >> would be appreciated. (and should probably be added to the >> www.machinekit.io/docs/getting-started. >> >> -- 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]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
