2.6 Live+Install image
There are no translations available.

Announcing a new Live+Install DVD image for installing LinuxCNC 2.6 on Debian Wheezy. Instructions here.

LinuxCNC 2.6.5 is released
There are no translations available.

This release has a couple of bug fixes and some documentation improvements.  All users of 2.6 are encouraged to upgrade.  Full changelog here.

LinuxCNC 2.6.4 is released!
There are no translations available.

A couple of important UI bugs fixed, all users of 2.6 are encouraged to upgrade.  Full changelog here.


Сообщения об ошибках

Комманда EMC использует трэкеры SourceForge для отслеживания ошибок и запросов, и для направления усилия разработчиков. Эта страница содержит ссылки на трэкеры, а также объясняет, как их использовать.

Сообщения об ошибках

Чтобы посмотреть текущий список ошибок, нажмите здесь.

Наиболее полезные сообщения об ошибках (и с большей вероятностью быстро исправленные) это те, которые описывают с наибольшими подробностями что происходит и при каких условиях. Вам следует включить информацию о вашей системе, типе используемой RTOS, и так далее. Опишите условия, которые приводят к ошибке, что сделала программа, и что, по вашему мнению, она должна была сделать. Ошибки в документации следует заявлять так же - опишите, что говорит документация, и что, по вышему мнению, она должна говорить. Пометьте, является ли она просто неясной или не соответствует поведению программы.

Если возможно, вам следует зарегистрироваться в SourceForge и войти до того как заполнить заявку. Это поможет нам держать вас в курсе хода решения проблемы, или связаться с вами для дополнительной информации. Для регистрации нажмите здесь. Если это невозможно или неудобно для вас, вы все равно можете сделать заявку, однако анонимные заявки получают более низкий приоритет и с ними труднее работать.

Для размещения заявки нажмите здесь.  

Feature Requests

To see the list of existing requests, click here.

The Enhanced Machine Controller design process is open to ensure a system that reflects the needs of the user community. Listening to the needs of users and developers ensures that valuable suggestions for improvement can flow into project. As you consider submitting a feature request, toss it about a bit with others on the EMC lists so that your request comes to the Board ready for them to set priority and assign people.

You must register with SourceForge and log in before submitting a feature request. That will allow us to keep you informed about the progress of your request, and contact you if we need more information. To register, click here.

To submit a feature request, click here.


Priorities are assigned to each tracker item by the EMC board of directors. The priority of an item indicates how important it is to the overall project, and each developer should ideally work on the highest priority item that they feel capable of handling. (Although there is nothing wrong with fixing some low priority items if you don't have the time or energy to tackle something big.)

  • Level 9 - Urgent safety critical issues - All developers should concentrate on fixing level 9 reports as quickly as possible.
  • Level 8 - Fatal bugs - those that completely prevent EMC from operating. Build failures, crashes, kernel oopses, segfaults, and the like.
  • Level 7 - High priority bugs - those prevent EMC from operating correctly. High priority feature requests that would greatly enhance EMC.
  • Level 6 - Medium priority bugs - those that affect only certain G-code programs, or certain drivers, or some other small subset of the user base. Medium priority feature requests that are either critical to a small subset of the user base, or widely useful but non-critical.
  • Level 5 - Low priority bugs - those with known workarounds, but which should still be fixed properly. Low priority feature requests that are only minor improvements, or which benefit a very small number of users.
  • Level 4 - Nuisance level bugs and minor improvements that can be done as time and manpower permits.
  • Level 3 - Cleanup issues like misspelled error messages or prompts, coding style violations, minor documentation revisions. Feature requests that will have no real effect on how the program actually works, but will make the code or documentation more readable, or have other benefits.
  • Level 2 - Features that would be nice, but aren't currently practical for various reasons. (Or bugs that simply can't be fixed without work that is out of proportion to the benefits gained.) They are good things to think about, and if you have ideas toward implementing/fixing them, feel free to post comments to the tracker item. In some cases, a level 2 item will result in other items being submitted, as steps needed to make the original item possible. When it becomes practical, the priority will be raised.
  • Level 1 - Newly submitted items to which the board has not yet assigned a priority


Trackers use catagories to group related items together. Tracker items can be sorted by catagory, to allow developers to quickly find items they can work on. When submitting an item, pick the catagory that you think best fits it. If you're not sure, just leave the catagory as "none", and the board will assign a catagory.

The following list is a combination of the existing catagories and some proposals. (Currently there is only one catagory for all EMC1 items.) This list is subject to change.

  • EMC2 related catagories
  • Build System
  • Documentation
  • G-Code Interpreter
  • GUI - AXIS
  • GUI - TkEMC, Mini, etc
  • Motion Controller
  • Task Controller
  • HAL
  • Stepconf
  • website

  • EMC1 bugs
    (Note: EMC1 bug reports are no longer being processed. Please try to reproduce the bug in emc2, and if you can, report it there).

Обновлено 19.03.2008 15:49  
© 2014
Joomla! is Free Software released under the GNU General Public License.