Re: [Emc-developers] ncam_for_2.7 branch (formerly features_preview_3)
Hi Dewey Glad to hear from you Can you remind me how to clone that repo ? I guess my last year ssh key will still be good Last post is not included I have a couple changes submitted by Norbert to publish I have a plane to catch this Wednesday and will be back home only in November, however I think I will be able to answer questions posted in the forum. I think everyone will love this release I am very proud of and they will want it asap. Should I ask them to manifest themselves ? Best regards, Fernand Le 2016-10-09 à 20:15, Dewey Garrett a écrit : > Fern's recent updates and renaming of 'features' to > 'NativeCAM' (short name ncam) has been greeted with much > enthusiasm by users who have waited a long time for > this excellent conversational/CAM interface. > > Fern has a github repository for the code. Using the code > requires that a user download a zip file (or do a git > checkout from his repository) and then run scripts to > install (or uninstall) into system directories using > superuser (root) privileges. Additional steps are needed to > run with a RIP (Run-In-Place) build. > > About a year ago, a test branch (first named > bringin_features then features_preview_3) was added to the > LinuxCNC git repository so I have updated it with a new > branch named ncam_for_2.7. The updates were made by first > rebasing to the current 2.7 branch and then copying/renaming > ncam-specific files based on commit bf8d6fc (2016-10-09) > from Fern's NativeCAM repository on github. > > I have lightly tested this branch both as a RIP and from a > locally built deb on debian/jessie/uspace/64bit > and it seems to start ok for me (i have not used it > much but the example projects for the axis gui opened ok). > > This branch is available immediately for users making a RIP > build or (soon, see note) from a scratch deb obtained from > the buildbot per instructions at buildbot.linuxcnc.org > > I believe that this branch can be merged to 2.7 if users > want it and if Fern is willing to make git updates to this > new Linuxcnc branch (ncam_for_2.7). Help with git is > available from experienced LinuxCNC developers. > > Note that the 2.7 branch is appropriate because: >1) Code and supporting files are added only for ncam > functionality and no changes are made to other code > or scripts in the linuxcnc git tree. >2) Infrastructure changes are minor and readily assessed for risk: > a) new: lib/python/gladevcp/ncam.py > include NCam in: lib/python/gladevccp/hal_pythonplugin.py > b) most ncam files are localized to a new directory: > share/lib/ncam/ > c) src/Makefile -- provides an ncam executable and > the new directories in share/lib/ncam/... > b) debian/linuxcnc.in -- populates /usr/share/ncam/ > > Ongoing forum discussions at: > > > https://forum.linuxcnc.org/forum/40-subroutines-and-ngcgui/31659-nativecam-is-features-renamed > > indicate positive results with NativeCAM although there are > complications due to the use of custom install scripts and > the assumptions in provided sim configs that are based on the > development branch (master not 2.7). > > I believe that NativeCAM incorporation can be expedited by > using and updating this ncam_for_2.7 test branch with a goal > of a merge to 2.7 for the next 2.7 release. > > Note: > The buildbot has failed with an armhf slave-lost exception > so buildbot debs for ncam_for_2.7 will not be available > until there is a restart. The more common architectures ran > successfully for this new branch. > -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
[Emc-developers] Spindle control setup
Hi, I want to control spindle speed with lcnc and I am a little confused about how to do it and hope someone can put me on track. My BOB is this one : http://www.omc-stepperonline.com/5-axis-cnc-breakout-board-interface-for-stepper-motor-driver-stv2-p-197.html My VFD manual is here : http://www.hclub.ee/download/varia/KOC100%20Series%20User%20Manual--20150119%28V1.1%29.pdf lcnc gives the options of : analog signal OR pwm. B-O-B supposedly can do either : pwm through pin 1 or any output pin and 0-10v through output connect inverter but says nothing about how to address this output connect inverter VFD has analog input for 0-10V and if I am right, it says to connect a pulse to an analog pin. Example at http://linuxcnc.org/docs/html/examples/spindle.html say to use : net spindle-speed-DAC scale.0.out => I have no idea what I should replace with I could maybe connect pwm to VFD to an analog pin but it seems strange to me, usually I connect pwm to digital input Any suggestions ? Fernand -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140 ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] help for Fernand (features_preview)
Hi Dewey Trying to start linuxcnc with features from the wizard results in this with axis : Machine configuration directory is '/home/fernand/linuxcnc/configs/sim.axis' Machine configuration file is 'axis-features.ini' and this with gmoccapy : Machine configuration directory is '/home/fernand/linuxcnc/configs/sim.gmoccapy' Machine configuration file is 'gmoccapy-features.ini' Those files do no exist and the paths are not right in features_preview Though I can start it any way, can testers do it easily ? Or maybe this is how it will be when released ? Regards Fernand -- ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] help for Fernand (features_preview)
Hello Dewey Thanks for the usefull information on working with git and linuxcnc-git I made some changes and tried pushing to linuxcnc.git I had some problems because I was not aware I had to make a pull before When I saw it would not work I continued editing and made more changes. When I found why it would not and tried to do it I forgot to edit the Merge Msg. I prepared this while I was editing : features_preview: catch-up with current development by Fernand Veilleux Improve multi-units functions Improve menu look Removed some obsolete/unused/irrelevant code topfeatures_toolbar is true history tb Dropped DnD project Dropped widget_box in favor of treeview Modified search_path function to display message Dropped status bar Set default editor to gedit Many minor fixes Files changed lib/python/gladevcp/features.py share/features/features.glade share/features/catalogs/mill/defaults.ngc configs/sim/gmoccapy/features_demo/gmoccapy.ini --- Can it still be edited ? How ? Best Regards Fernand Veilleux -- ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
[Emc-developers] Setting up rip-environment
Hello How do I set-up rip-environment ? Typing ./rip-environment or ./rip-environment.in in a terminal result in either No file of this type or Permission not allowed How do I run this ? Fernand Veilleux -- ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] features_preview (update)
There are a few changes and bugfixes you missed that should be made in features.py uncomment line 2733 : #tree_path = model.get_path(itr) uncomment line 2810 : #tree_path = None replace lines 2835 and 2836 : if not self.sub_hdrs_in_tv1 : self.treeview.expand_all() with : if tree_path is not None and not self.sub_hdrs_in_tv1 : self.treeview.expand_row(tree_path, False) It will be much better replace line 1965 : self.topfeatures[src][3] += 1 with : self.topfeatures[src][3] = time.time() replace line 1919 : self.topfeatures_dict[s[0]] = [int(s[1]), 0] with : self.topfeatures_dict[s[0]] = [int(s[1]), float(s[2])] SUPER_TOP_FEATURES_COUNT could be reduced to 3 or even 0 It will make a true history toolbar but this toolbar will be really usefull when we have all the right icons. There are functions that are obsolete and not used. In version 2.02 I removed the 'widget box'. The treeview with VKB is much better specially with touch screen There is also a bug that should be fixed ASAP in lib/fv_entry-arc.ngc replace line 20 : o if [# EQ 2] (no compensation) with : o if [[# EQ 2] OR [#5410 EQ 0]] (no compensation) replace line 29 : # = [[#5410 + 0.01] / 2] (tool radius used to calc pre-entry point) with : # = [#5410 * 0.501] (tool radius used to calc pre-entry point) It will work with tools larger then 15mm in diameter now Fix also the same in lib/fv_entry-angle.ngc replace line 17 : o if [# EQ 2] (no compensation) with : o if [[# EQ 2] OR [#5410 EQ 0]] (no compensation) replace line 36 : # = [[#5410 + .01] / 2] with : # = [#5410 * 0.501] I thought 'Features' was not ready to include in LCNC. My wife said that it was me that was not ready. I took it when it was a baby and helped it grow in it's infancy. In the last 15 months I spent most of my leisure time at this task. She said I felt like her when our sons left home. I am happy it is in your hands now and you will bring it to maturity. I will still contribute as much as I can. Fernand -- ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] features_preview (update)
>> There are a few changes and bugfixes you missed that should be made > These were not available at the FernV (commit dfd2b7b v2.01) where > the 'features_preview' branch starts (so were not included). > > Could you make a patch for the 'features_preview' branch? > > Some instructions: >http://www.linuxcnc.org/docs/html/code/contributing-to-linuxcnc.html > > Plus: Seb has offered access: > > > http://www.mail-archive.com/emc-developers@lists.sourceforge.net/msg15305.html > > Plus: developers on this list and irc are alays helpful with git. Where do I register as a developer ? > There are some items that probably need attention before the > 'features_preview' > branch is merged to 2.7. My notes are at: > http://www.panix.com/~dgarrett/stuff/features_preview.txt > > Summary: >1) The script 'engrave-feature' would need a license revision in > order to be incorporated into LinuxCNC. The author(s) > would have to do this. (I am sure that Seb or other developers > can provide guidance) >3) If engrave-feature is incorporated, a method to provide .cxf > fonts needs to be implemented. (they could be included in > a new directory share/features/ if the licenses are appropriate) >3) The modified truetype-tracer (tt-tracer in 'features') needs > attention. It could be provided separately as a deb or > incorporated into the LinuxCNC build process with src/ and > src/Makefile additions. > Chris Radek may wish to comment. >4) There is some indication that using the python module > 'webbrowser' for opening a file editor may not work on all > platforms supported by LinuxCNC. > Alternatives for opening files for editing could be considered. > ([DISPLAY]EDITOR for instance). >5) Versioning the 'features' app within LinuxCNC is somewhat > unconventional (ref: features.py: update_check_all()). Right, this is not relevant anymore Is the information on https://www.kernel.org/pub/software/scm/git/docs/gittutorial.html the same as available at http://git-scm.com/book/fr/v2/ ? Fernand -- ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] linuxcnc-features in linuxcnc?
Le 2015-10-26 13:09, Sebastian Kuzminsky a écrit : > Hello Nick and Fernand, I'm a developer on the LinuxCNC project and > we've been talking about getting linuxcnc-features into the next > stable release of linuxcnc. > > Is this something you'd be interested in, willing to help with? > > We noticed that there are two linuxcnc-features repos on github, what > is the relationship between them? > > Hello Sebastian, I must admit you took me by surprise when you wrote you wanted to include features in next stable release. I knew it would be interesting but I though that it needed some more refinements before. I have a tight schedule currently and cannot spend much time to rush the project. It seems that you deleted bringing_features and I do not blame you. I hope you still think that it is a very good add-on to linuxcnc, nothing else comes close. Since I wrote more than 90% of the code I am the one that knows it best and I will help you. But you should not work with version 2.0 it is outdated, having been released about 4 months ago. Version 2.01 released last month is much better. They both have much code and files to delete. Those releases were the first I made and it was some kind of market test to find the interest. I believe version 2.02 will be ready to include in stable linuxcnc and I am proposing you what I know will work. Please correct me on what does not fit your view. Features depend on a good directory structure and links to those directories. APP_PATH : /usr/features files in this dir : features.py features.glade features.ui CHANGES README.md sub-dirs : catalogs lathe mill examples graphics images ini lathe mill lib support Working dir : $HOME/linuxcnc/features link to APP_PATH/features.ui links to APP_PATH/... catalogs examples graphics ini lib support USER_DATA : $HOME/linuxcnc/features/user (not $USER, full access) (preferences file will be saved there, no need to create) sub-dirs : catalogs lathe (files that will be saved here : default template and history) mill(user will save his modified menu.xml) graphics ini lib scripts (or the name you think is best, this is where resulting file 'features.ngc' will be saved) xml No files need to be created. This is where the user puts his modified files. Features will first search files in USER_DATA and use it if found, else it uses APP_PATH Links needed : /usr/local/bin/features to APP_PATH/features.py (stand alone from anywhere, no need for args, everything from defaults or preferences file) /usr/share/pyshared/gladevcp/features.glade -> APP_PATH/features.glade /usr/lib/pymodules/python2.7/gladevcp/features.glade -> APP_PATH/features.glade /usr/share/pyshared/gladevcp/features.py -> APP_PATH/features.py /usr/lib/pymodules/python2.7/gladevcp/features.py -> APP_PATH/features.py optional : /usr/share/pyshared/gladevcp/features_user -> USER_DATA Files to edit : /usr/share/pyshared/gladevcp/hal_pythonplugin.py /usr/share/glade3/catalogs/hal_python.xml Linuxcnc ini files axis-features.ini, axis_mm-features.ini and axis_lathe-features.ini could be added in sim.axis without any other files OR sim.axis.features dir could be created with the needed files Similar option for gmoccapy This is what I am preparing for release 2.02 I hope to have it ready in less than one month. Some new features I am adding are very difficult to implement, gcode is terrible IMHO. Regards Fernand -- ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
