Activity for retnev
-
retnev posted a comment on discussion Open Discussion
I followed the source compile instructions for the most recent Pycam release and got the error. "Unable to locate package python-gtk2" It is seemingly uninstallable in Debian/MX21 Anyone has an idea how to get pycam working on Debian ? OS: NAME="MX" VERSION="21.3 (Wildflower)" ID="mx" VERSION_ID="21.3" PRETTY_NAME="MX 21.3 (Wildflower)" ANSI_COLOR="0;34" HOME_URL="https://mxlinux.org" BUG_REPORT_URL="https://mxlinux.org" PRETTY_NAME="MX 21.3 Wildflower" DISTRIB_ID=MX DISTRIB_RELEASE=21.3 DISTRIB_CODENAME="Wildflower"...
-
I followed the source compile instructions for the most recent Pycam release and got the error. "Unable to locate package python-gtk2" It is seemingly uninstallable in Debian/MX21 Anyone has an idea how to get pycam working on Debian ? OS: NAME="MX" VERSION="21.3 (Wildflower)" ID="mx" VERSION_ID="21.3" PRETTY_NAME="MX 21.3 (Wildflower)" ANSI_COLOR="0;34" HOME_URL="https://mxlinux.org" BUG_REPORT_URL="https://mxlinux.org" PRETTY_NAME="MX 21.3 Wildflower" DISTRIB_ID=MX DISTRIB_RELEASE=21.3 DISTRIB_CODENAME="Wildflower"...
-
No response ?
-
Title of original post should be CDEMU, unfortunately I cannot edit my mistake. Some additional info I forgot to add above and there is no way to edit my post it seems: # cat /proc/version Linux version 5.15.0-12.2-liquorix-amd64 (stevep@mxlinux.org) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 ZEN SMP PREEMPT liquorix 5.15-15~mx21+1 (2022-01-03) # /usr/bin/cdemu --version cdemu 3.2.5 - (C) 2006-2023 Rok Mandeljc However # cdemu status ERROR: Failed to connect...
-
Some additional info I forgot to add above and there is no way to edit my post it seems: # cat /proc/version Linux version 5.15.0-12.2-liquorix-amd64 (stevep@mxlinux.org) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 ZEN SMP PREEMPT liquorix 5.15-15~mx21+1 (2022-01-03) # /usr/bin/cdemu --version cdemu 3.2.5 - (C) 2006-2023 Rok Mandeljc However # cdemu status ERROR: Failed to connect to CDEmu daemon: g-io-error-quark: The connection is closed (18) But, vhba seems...
-
Cemu vs Kernel Versions
-
bashdbg probably mislinked on github & fail to compile.
-
-
-
Using MX21 Linux version 5.15.0-12.2-liquorix-amd64 (stevep@mxlinux.org) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 ZEN SMP PREEMPT liquorix 5.15-15~mx21+1 (2022-01-03) I am trying to install bash debugger from source. I read all the readme's and cannot figure out the correct compilation procedure. I did ./configure make make install but the below error about "PIE" keeps creeping up. I tried passing --pie to make but it didnt work either. Searching on the...
-
Using MX21 Linux version 5.15.0-12.2-liquorix-amd64 (stevep@mxlinux.org) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 ZEN SMP PREEMPT liquorix 5.15-15~mx21+1 (2022-01-03) I am trying to install bash debugger from source. I read all the readme's and cannot figure out the correct compilation procedure. I did ./configure make make install but the below error about "PIE" keeps creeping up. I tried passing --pie to make but it didnt work either. Searching on the...
-
Using MX21 Linux version 5.15.0-12.2-liquorix-amd64 (stevep@mxlinux.org) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 ZEN SMP PREEMPT liquorix 5.15-15~mx21+1 (2022-01-03) I am trying to install bash debugger from source. I read all the readme's and cannot figure out the correct compilation procedure. I did ./configure make make install but the below error about "PIE" keeps creeping up. I tried passing --pie to make but it didnt work either. Searching on the...
-
Using MX21 Linux version 5.15.0-12.2-liquorix-amd64 (stevep@mxlinux.org) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 ZEN SMP PREEMPT liquorix 5.15-15~mx21+1 (2022-01-03) I am trying to install bash debugger from source. I read all the readme's and cannot figure out the correct compilation procedure. I did ./configure make make install but the below error about "PIE" keeps creeping up. I tried passing --pie to make but it didnt work either. Searching on the...
-
Anyway thanks for all the help. Cdemu is one of the greatest Linux applications and I appreciate it very much.
-
Nope the path trick didnt work. I now have several broken applications. Python to me is irresponsible software. No backward compatibility between versions and if no backward compatibility, the user is not informed that that would be the case. I really dont like the snake. I honestly dont know how the new version got onto my system. as all automatic updates were switched off and I didnt install anything before this problem started happening. Anyway I know this is off topic, but if you know of an easy...
-
I managed to get 5.3 the default again by just changing the PATH order of /usr/bin and /usr/local/bin # python3 Python 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516] on linux Dont know if that will work in the end, but it is a quick way to get rid of the dreaded 3.6.
-
-
Although the problem is solved it would be kind if you could tell me how to make python 3.5.3 the default python again as you suggested. I need to do that as ALSA also have sudden trouble (SPDIF stopped working) and it must be the mystery Python upgrade and alsa seemingly dependent on the previous version 3.5.3 of python. Basically, how do I uninstall python 3.6.3 ? From my web searches it looks really involved and entails python specific commands and not normal sysadmin commands. Python is just...
-
Although the problem is solved it would be kind if you could tell me how to make python 3.5.3 the default python again as you suggested. I need to do that as ALSA also have sudden trouble (SPDIF stopped working) and it must be the mystery Python upgrade and alsa seemingly dependent on the previous version 3.5.3 of python. Basically, how do I uninstall python 3.6.3 ? From my web searches it looks really involved and entails python specific commands and not normal sysadmin commands.
-
Although the problem is solved it would be kind if you could tell me how to make python 3.5.3 the default python again as you suggested. I need to do that as ALSA also have sudden trouble (SPDIF stopped working) and it must be the mystery Python upgrade and alsa seemingly dependent on the previous version 3.5.3 of python.
-
Thanks a lot. I changed the shebang and now it works. Regarding Python: I have only two problems on Linux as syadmin. They are Python and systemD. Python must be heaven for a developer but it is truly hell for a user to maintain. I have no idea why gi suddenly moved from python3 to python 3.5 which is clearly what the problem was. Since this happened without any of my direct doing. No python installs or any cdemu installation. The system is basically hard locked as it is mission critical. The question...
-
Thanks a lot. I changed the shebang and now it works. Regarding Python: I have only two problems on Linux as syadmin. They are Python and systemD. Python must be heaven for a developer but it is truly hell for a user to maintain. I have no idea why gi suddenly moved from python3 to python 3.5 which is clearly what the problem was. Since this happened without any of my direct doing. No python installs or any cdemu installation. The system is basically hard locked as it is mission critical. The question...
-
First Question # dpkg -s python3 Package: python3 Status: install ok installed Priority: optional Section: python Installed-Size: 67 Maintainer: Matthias Klose <doko@debian.org> Architecture: amd64 Multi-Arch: allowed Source: python3-defaults Version: 3.5.3-1 Replaces: python3-minimal (<< 3.1.2-2) Provides: python3-profiler Depends: python3.5 (>= 3.5.3-1~), libpython3-stdlib (= 3.5.3-1), dh-python Pre-Depends: python3-minimal (= 3.5.3-1) Suggests: python3-doc (>= 3.5.3-1), python3-tk (>= 3.5.3-1~),...
-
It is installed for Python3 $apt install python3-gi Reading package lists... Done Building dependency tree Reading state information... Done python3-gi is already the newest version (3.22.0-2).
-
It is installed for Python3 $apt install python3-gi Reading package lists... Done Building dependency tree Reading state information... Done python3-gi is already the newest version (3.22.0-2).
-
It has been working for about 2 years now. How? well cdemu cant be installed through apt in debian so it was installed from sourceforge download pages. Cdemu cdemu-daemon-3.2.2.tar.bz2 vhba-module-20190410.tar.bz2 libmirage-3.2.2.tar.bz2 Kernel $ cat /proc/version Linux version 5.2.0-17.2-liquorix-amd64 (stevep@mxlinux.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 ZEN SMP PREEMPT liquorix 5.2-26~mx17+1 (2019-09-24) Distro $cat /etc/lease NAME="MX" VERSION="18 (Continuum)" ID="mx"...
-
Unresolvable cdemu & gi issue
-
Ok, Yet again crickets. this group is dead. If anyone lands at this alsa dead door and have the same problem with these interfaces, search for my thread in Ardour UG where I managed to solve the problem the hard way and step over a lot of obvious alsa bugs which never get sorted out. Cheers.
-
I also want to know why this happens suddenly. Also happens to my Motu gear
-
Alsa works great with my UMC1820 interface. Absolute BLISS !! I recently bought the ADA8200 ADAT extension to get 8 more inputs. It is all connected correctly as I get all inputs and outputs and pass sound on all inputs in Windows as a test. However on Linux, alsa only sees 8 inputs on the UMC1820 and only two out of eight inputs on the ADA8200, namely inputs 7&8 works. Inputs 1-6 does not work. Since the UMC1820 makes you select between SPDIF (technically channels 9&10) and the ADAT extension (8...
-
I also want to know why this happens suddenly.
-
MX18 Linux version 4.19.0-1-amd64 (stevep@mxlinux.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.19.5-2~mx17+1 (2018-12-12) NAME="MX" VERSION="18 (Continuum)" ID="mx" VERSION_ID="18" PRETTY_NAME="MX 18 (Continuum)" ANSI_COLOR="0;34" HOME_URL="https://mxlinux.org" BUG_REPORT_URL="https://mxlinux.org" PRETTY_NAME="MX 18.3 Continuum" DISTRIB_ID=MX DISTRIB_RELEASE=18.3 DISTRIB_CODENAME=Continuum DISTRIB_DESCRIPTION="MX 18.3 Continuum" PRETTY_NAME="Debian GNU/Linux 9 (stretch)"...
-
Dont you maybe have a deb available for veejay ? It is short from impossible to install from sources. I ended uop with a long script but there were too many things that went wrong that is unresolveable.
-
This is not really a straight forward user question and thereby I post it in the developer forum. My Problem: I use Alsa/Jack/Pulseaudio to run quite an extensive audio interface to DAW with involved Jack routings of both Audio and Midi. The system runs like greased lightning and I can do things on Linux that I could never do on windows period. The problem is that there exist applicatio9ns that is not ALSA/JACK Midi friendly. One such Application is Bitwig for Linux 1) Bitwig absolutely requires...
-
I guess alsa isnt actively developed anymore ?
-
I have the same question. Does it work with Lazarus.
-
I am trying to get Alsa to route spdif from an 1818VSl. The alsamixer says Clock sour for spdif. I can use windows and use spdif, so it is not connection problems or hardware problems, it is definately the interaction between 1818vsl and alsa that is the problem. I tried both internal clock and spdif clock in the 1818vsl, but nothing seems to remove the clock-sour message in alsa to get spdif to work in linux. Any ideas what i can still try.
-
I guess this group is dead.
-
I have no problem with alsa routing to and from all 8 inputs and 18 outputs on my 1818vsl. However spdif which is usually on inputs 9&10 doesnt work. The spdif setup works as with the windows software all works, but in linux with alsa there is no signal reported on channels 9&10 which alsa does provide for the 1818vsl. Are there special consideration regarding alsa with spdif I am not aware of, Does it need clock timings if so, hwere is the clock timing that alsa get from the 1818vsl. I see no such...
-
I have no problem with alsa routing to and from all 8 inputs and 18 outputs on my 1818vsl. However spdif which is usually on inputs 9&10 doesnt work. The spdif setup works as with the windows software all works, but in linux with alsa there is no signal reported on challes 9&10 which alsa does provide for the 1818vsl. Are there special consideration regarding alsa with spdif I am not aware of, Does it need clock timings if so, hwere is the clock timing that alsa get from the 1818vsl. I see no such...
-
I have two issues setting up Pycam. 1) The tool doesnt return to original position (where it started from after completion of a routine. I can enter this in GCODE manually, but just wonder why this was left out as it is obvious that you dont want to start from a new position and what the tool to return to exactly where it started. 2) I always place the tool on the workpiece and whe the program executes it lifts by a certain prescribed amount and then does the milling and return to that same place...
-
I have two issues setting up Pycam. 1) The tool doesnt return to original position (where it started from after completion of a routine. I can enter tis in GCODE manually, but just wonder why this was left out as it is obvious that you dont want to start from a new position and what the tool to return to exactly where it started. 2) I always place the tool on the workpiece and whe the program executes it lifts by a certain prescribed amount and then does the milling and return to that same place...
-
Installing on a new machine I got rid of the python xy toolpath route issue, so that problem is gone now. I made a video where I am now. Only difference I chose a ball end tool. As you will see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface as it should.
-
I just done exactly the steps you did and this time I get orange tootlpaths, which is great. Last time I got black toolpaths.... this could only be due to the corrupt python stuff. However the toolpaths are still such that it machines dead on the x-y plane @z=0. !!! ? Basically destroying the workpiece and the machine, by plunging down through the workpiece to the xy plane and machining the bottom flat taking all the material with it in one shot. This should not be allowed by the constraints if the...
-
Installing on a new machine I got rid of the python xy toolpath route issue, so that problem is gone now. I made a videeo where I am now. Only difference I chose a ball end tool. As you will see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface as it should.
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black toolpaths.... this could only be due to the corrupt python stuff. However the toolpaths are still such that it machines dead on the x-y plane @z=0. !!! ? Go figure! Basically destroying the workpiece and the machine, by plunging down through the workpiece to the xy plane and machining the bottom flat taking all the material with it in one shot. This should not be allowed by the constraints if the toolpaths...
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black toolpaths.... this could only be due to the corrupt python stuff. However the toolpaths are still such that it machines dead on the x-y plane @z=0. !!! ? Go figure! Basically destroying the workpiece and the machine, by plunging down through the workpiece to the xy plane and machining the bottom flat taking all the material with it in one shot. Sheesh ! This should not be allowed by the constraints...
-
Lars, hope you could open the screencapture. I did it n MP4. I open it with mpv on linux. Let me know if you need it in ogv
-
Lars, hope you could open the screencapture. I did it n MP4. Let me know if you need it in ogv
-
No it is a dreaded Python problem as usual. I uninstalled all the python with dpkg. Basically everything mentioning py or python. Then reinstalled all python again, then it worked. Back to pycam. I have it running again after I tamed the snake so it has nothing to do with pycam. I will record a session for you to see what I do wrong. I really apprecaite your kind help.
-
Installing on a new machine I got rid of the python xy toolpath route issue. Here is a video what it does now. Only difference I chose a ball end tool. As you will see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface.
-
Installing on a new machine got rid of the python xy toolpath route. Here is a video. Only difference I chose a ball end tool. As you will see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface.
-
Installing on a new machine got rid of the python xy toolpath route. Here is a video. Only difference I chose a ball end tool. As you wiull see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface.
-
Installing on a new machine got rid of the python xy toolpath route. Here is a video. Only difference I chose a ball end tool. As you wiull see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simuulations in the wrong order to show the fact that the toolath doesnt follow the curved surface.
-
Installing on a new machine got rid of the python xy toolpath route. Here is a video. Only difference I choses a ball end tool. As you wiull see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simuulations in the wrong order to show the fact that the toolath doesnt follow the curved surface.
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black toolpaths.... this could only be due to the corrupt python stuff. However the toolpaths are still such that it machines dead on the x-y plane @z=0. !!! ? Go figure! Basically destroying the workpiece and the machine, by plunging down through the workpiece to the xy plane and machining the bottom flat taking all the material with it in one shot. Sheesh ! This should not be allowed by the constraints...
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black toolpaths.... this could only be due to the corrupt python stuff. However the toolpaths are still such that it machines dead on the x-y plane @z=0. !!! ? Go figure! Basically destroying the workpiece and the machine, by plunging down through the workpiece to the xy plane and machining the bottom flat taking all the material with it in one shot. Sheesh ! This should not be allowed by the constraints...
-
No it is a dreaded Python problem as usual. I uninstalled all the python with dpkg. Basically everything mentioning py or python. Then reinstalled all python again, then it worked. I have never encountered such a reckless programming language as python, nothing against you or pycam it is directed to the snake & its developers. Whenever I have a problem, Python sure will be the culprit behind it. I know it is great for developers to write software, but it is an absolute mess for perpetual installation...
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black tootlpaths.... this could only be due to the corrupt python stuff. However the toolpaths are still such that it machines dead on the x-y plane @z=0. !!! ? Go figure! Basically destroying the workpiece and the machine, by plunging down through the workpiece to the xy plane and machining the bottom flat taking all the material with it in one shot. Sheesh ! This should not be allowed by the constraints...
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black tpootlpaths.... this could only be the corrupt python stuff. However the toolpaths are still such that it machines dead on the x-y plane @z=0. !!! ? Basically destroying the workpiece and the machine, by plunging down through the workpiece to the xy plane. This should not be allowed by the constraints. I will make a screen recording.
-
No it is a dreaded Python problem as usual. I uninstalled all the python with dpkg. Basically everything mentioning py or python. Then reinstalled all python again, then it worked. I have never encountered such a reckless programming language as python, nothing against you or pycam it is directed to the snake & its developers. Whenever I have a problem, Python sure will be the culprit behind it. I know it is great for developers to write software, but it is an absolute mess for perpetual installation...
-
No it is a dreaded Python problem as usual. I uninstalled all the python with dpkg. Basically everything mentioning py or python. Then reinstalled all python again, then it worked. I have never encountered such a reckless programming language as python, nothing against you or pycam it is directed to the snake & its developers. Whenever I have a problem, Python sure will be the culprit behind it. I know it is great for developers to write software, but it is an absolute mess for perpetual installation...
-
I will have to install an order version again. The newest version is too buggy.
-
Attached the entire output during install
-
Reinstalling the newest version creates a spectacular crash. There are no errors during compile. I installed it using the same installation script I initially installed it when it worked afterwards. Now I get $ pycam Traceback (most recent call last): File "/usr/local/bin/pycam", line 4, in <module> import('pkg_resources').run_script('pycam==0.6.3', 'pycam') File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 739, in run_script self.require(requires)[0].run_script(script_name, ns)...
-
Newest version of Pycam, out of the blue just started crashing. Nothing changed that could cause this. I will have to reinstall again and then I will record my steps as you asked. $ pycam Enabled 4 parallel local processes Segmentation fault $
-
AFAIK this is the forum for OCL./Opencam Trying to Install python-ocl but get snagged on a dependency that is seemingly a malconfiguration as python 2 is installed. This is what I use to build a deb for python-ocl git clone https://github.com/aewallin/opencamlib.git cd opencamlib bzr branch lp:~neomilium/opencamlib/packaging debian dpkg-buildpackage -b -us -uc cd .. sudo dpkg -i python-ocl*.deb However the dplkg-buil.... exits with the following error. make[1]: Leaving directory '/backup1/temp/opencamlib/obj-x86_64-linux-gnu'...
-
I installed exactly the version of pycam you used, Used exactly the settings you used on exactly the same file. I end up with different paths and a hollow box. The Paths indicated are black lines not orange as yours (just as a side note) and the top curved surface is ignored as the box is seen as a hollow container not a solid !?. It then machines the sides and the bottom flat part of the object completely ignoring the curved surface. Now I am stumped. The only difference between what I did and you...
-
I installed exactly the version of pycam you used, Used exactly the settings you used on exactly the same file. I end up with different paths and a hollow box. The Paths indicated are black lines not orange as yours (just as a side note) and the top curved surface is ignored as the box is seen as a hollow container not a solid !?. It then machines the sides and the bottom flat part of the object completely ignoring the curved surface. Now I am stumped. The only difference between what I did and you...
-
I installed exactly the version of pycam you used, Used exactly the settings you used on exactly the same file. I end up with different paths and a hollow box. The Paths indicated are black lines not orange as yours (just as a side note, and the top curved surface is ignored as the box is sseen as a hollow container not a solid. It then machines the sides and the bottom flat part of the object completely ignoring the curved surface. Now I am stumped. The only difference between what I did and you...
-
I installed exactly the version of pycam you used, Used exactly the settings you used on exactly the same file. I end up with different paths and a hollow box. The Paths indicated are black lines not orange as yours (just as a side note, and the top curved surface is ignored as the box is sseen as a hollow container not a solid. It then machines the sides and the bottom flat part of the object completely ignoring the curved surface. Now I am stumped. The only difference between what I did and you...
-
I did not notice the little small font 0.6.3 at the top. I guess no-one will find that easily, but it is probably still an unstable version. The font fo 0.6.3 is about 20x smaller than the 0.6.2 and other versions so I never took notice of it till you pointed it out. Thanks P.S. Please consider updating the tar.gz file INSTALL.TXT to contain the instructions what command to run for installation e.g. $] python setup.py install as non-python programmers or general users wont know how to install pycam...
-
I did not notice the little small font 0.6.3 at the top. I guess no-one will find that easily, but it is probably still an unstable version. The font fo 0.6.3 is about 20x smaller than the 0.6.2 and other versions so I never took notice of it till you pointed it out. Thanks
-
Your example About page mentions Pycam 0.6.3 . There is nowhere I can find that version. Where is the download page for 0.6.3 ?
-
That is what has been driving me nuts for more than 6 months! Wish I knew about the bug. This is really helpful thank you very much. I will post back once the newest pycam runs.
-
That is what has been driving me nuts for more than 6 months! Wish I knew about the bug. This is really helpful thank you very much.
-
That really looks great ! Wish I could get to that stage, been trying for months. I will go over your video carefully. Was it issue#136 that caused it to create only a single cut along the surface ? I will install same version pycam as you used to repeat your steps. Thank you very much Lars!
-
OK, I transfered the attachment to the new post. Thanks
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt.
-
No problem, I since movedon to dxf2gcode which worked great so I did not have to deal with pycam config problems. So the above issue was resolved using dxf2gcode. I have STL files I need to CNC and that I need pycam for, so I will post it in another topic.
-
That figures, maybe they should call it something different rather than just adding ++. No way for a user to know. Thanks that solves it.
-
I checked sourceforge and latest Pycam is pycam++-0.1.0.tgz. However my installed Pycam version in Help/About is Pycam 0.5.1 !! Howcome my installed version is 5 generations newer than the newest onsourceforge ?
-
I checked sourceforge and latest Pycam is pycam++-0.1.0.tgz. However my installed Pycam version About is Pycam 0.5.1 !! Howcome my installed version is 5 generations newer than the newest onsourceforge ?
-
Anyone know where I can find a converter for Pycam .ngc to Techno Isel .ncd gcode ? Thanks
-
Wineasio installer for 64-bit fails. Below the details root@BLA:/temp/wineasio# ./prepare_64bit_asio ./prepare_64bit_asio: 2: ./prepare_64bit_asio: Syntax error: redirection unexpected
-
I need to add that this happens on Debian Stretch
-
dxf2gcode Crash Repeatable Method
-
Latest source compilation fails to recognize PYQT5
-
I cannot seem to get Tool Compensation to work. Can anyone tell me how I can have Pycam compensate for tool Diameter ? At the moment whatever I do the tool is always symmetric around the path where it should be at the outside edge. Thanks
-
I cannot seem to get Tool Compensation to work. Can anyone tell me how I can have Pycak compensate for tool Diameter ? At the moment whatever I do the tool is always symmetric around the path where it should be at the outside edge. Thanks
-
...
-
Make Fail
-
Followed the Installations on the following page tot the T, but it fails on make. https://brlcad.org/wiki/Compiling System PRETTY_NAME="Debian GNU/Linux 8 (jessie)" NAME="Debian GNU/Linux" VERSION_ID="8" (8.10) VERSION="8 (jessie)" Attached build.log
-
1) I cannot figure out how I would set the plunge depth to cnc route a 2 dimensional object. the Pycam interface is a bit confusing in that it only accepts gravure for 2 dimensional routing. That said, I figured out after a long time how to get almost perfect Gcode I can convert to my Fanuc, but I have a real problem setting plunge depth in Pycam. Under processes I cselect maximum Step down to say 4mm, but the G-code does not contain any plunges in the Z-direction of 4mm anywhere. At the moment I...
-
1) I cannot figure out how I would set the plunge depth to cnc route a 2 dimensional object. the Pycam interface is a bit confusing in that it only accepts gravure for 2 dimensional routing. That said, I figured out after a long time how to get almost perfect Gcode I can convert to my Fanuc, but I have a real problem setting plunge depth in Pycam. Under processes I cselect maximum Step down to say 4mm, but the G-code does not contain any plunges in the Z-direction of 4mm anywhere. At the moment I...
1 >