[Machinekit] Machinekit extruder problem

[Ömür Ceran]

Hi there,
I try to make a corexy printer but there are a few problem.
When ı upload a sketch and run machine, motor does not work as a 3d printer but 
when ı upload normal cnc .ngc file, it is working. Also ı had another problem 
about velocity extrusion enable. I use configuration which belongs to charles 
stein corexy. Can you help me about that? How can ı configure it for corexy and 
solve spindle to extruder?
https://github.com/cdsteinkuehler/machine-configs/tree/master/configs/CoreXZ

Thank you
Ömür Ceran

-- 
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.

Re: [Machinekit] Re: Updated install of machinekit -- new errors

[Bas de Bruijn]

> On 26 Feb 2019, at 06:32, mugginsac  wrote:
> 
> Found the culprits. Three more calls to rtapi_print() affected by the change 
> from RTAPI_MSG_ERR to RTAPI_MSG_ALL.
> But I have seemingly created a bug in my config in the process of cleaning 
> them up.
> The axis screen appears for a fraction of a second and then disappears.

Did you “export DEBUG=5” before the /var/log/linuxcnc.log?

-- 
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.

[Machinekit] Re: Updated install of machinekit -- new errors

[mugginsac]

Found the culprits. Three more calls to rtapi_print() affected by the 
change from RTAPI_MSG_ERR to RTAPI_MSG_ALL.
But I have seemingly created a bug in my config in the process of cleaning 
them up.
The axis screen appears for a fraction of a second and then disappears.

-- 
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.

[Machinekit] Updated install of machinekit -- new errors

[mugginsac]

I did sudo apt-get install machinekit. Now I get a bunch of new messages.
I am trying to figure out if I somehow screwed up my configs in the process 
of updating machinekit. Here is a link to my .ini file 
. Here is a link to my .hal file 
.
I have also attached a screen capture of the error/warning message that 
appeared on the axis screen.

cat /var/log/linuxcnc.log gives:
Feb 26 01:18:01 beaglebone msgd:0: startup pid=2670 flavor=rt-preempt 
rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 6.3.0 20170516  
version=v0.1~-~01fe624
Feb 26 01:18:01 beaglebone msgd:0: ØMQ=4.2.1 czmq=4.0.2 protobuf=3.0.0 
atomics=gcc intrinsicslibwebsockets=2.0.3
Feb 26 01:18:01 beaglebone msgd:0: configured: sha=01fe624
Feb 26 01:18:01 beaglebone msgd:0: built:  Feb 25 2019 07:42:47 
sha=01fe624
Feb 26 01:18:01 beaglebone msgd:0: register_stuff: actual hostname as 
announced by avahi='beaglebone.local'
Feb 26 01:18:01 beaglebone msgd:0: zeroconf: registering: 'Log service on 
beaglebone.local pid 2670'
Feb 26 01:18:02 beaglebone msgd:0: zeroconf: registered 'Log service on 
beaglebone.local pid 2670' _machinekit._tcp 0 TXT 
"uuid=471405b7-f524-4f2a-9697-6061a9855992" 
"instance=5c216bac-3964-11e9-9408-7c669d58a259" "service=log" 
"dsn=ipc:///tmp/0.log.471405b7-f524-4f2a-9697-6061a9855992"
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt memmapped gpio port 2 to 
0xb6fb1000, oe: 0xb6fb1134, set: 0xb6fb1194, clr: 0xb6fb1190
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt pin 9 maps to pin 2-5, 
mode 85
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt pin 10 maps to pin 2-4, 
mode 85
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt memmapped gpio port 0 to 
0xb6faf000, oe: 0xb6faf134, set: 0xb6faf194, clr: 0xb6faf190
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt pin 14 maps to pin 0-26, 
mode 85
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt pin 18 maps to pin 2-1, 
mode 85
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt memmapped gpio port 1 to 
0xb6fad000, oe: 0xb6fad134, set: 0xb6fad194, clr: 0xb6fad190
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt hpg_stepgen_init
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone msgd:0: rtapi_app exit detected - scheduled 
shutdown
Feb 26 01:18:11 beaglebone msgd:0: msgd shutting down
Feb 26 01:18:11 beaglebone msgd:0: zeroconf: unregistering 'Log service on 
beaglebone.local pid 2670'
Feb 26 01:18:11 beaglebone msgd:0: log buffer hwm: 0% (8 msgs, 699 bytes 
out of 524288)
Feb 26 01:18:11 beaglebone msgd:0: normal shutdown - global segment detached

machinekit@beaglebone:~$ cat linuxcnc_debug.txt
2648
  PID TTY  STAT   TIME COMMAND
Stopping realtime threads
Unloading hal components

machinekit@beaglebone:~$ cat linuxcnc_print.txt
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=/usr/libexec/linuxcnc/inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
INIFILE=/home/machinekit/machinekit/configs/ARM.BeagleBone.Xylotex/Xylotex.ini
PARAMETER_FILE=pru-stepper.var
TASK=milltask
HALUI=halui
DISPLAY=axis
Starting Machinekit server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting Machinekit IO program: io
Starting HAL User Interface program: halui
Killing task linuxcncsvr, PID=2648
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

-- 
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.

Re: Message privé sur le sujet suivant : [Machinekit] PRU development helper scripts/tools for Machinekit?

[Charles Steinkuehler]

On 2/25/2019 9:17 AM, Damien Dando wrote:
> Hi Charles, thanks!
> 
> Note: I tried to post this answer in the public google group but for some 
> unknown reason google keep deleting my answer right after I post. I also 
> tried to leave Machinekit group to re-join hoping it would reset something 
> but no luck.. fuck google! If you happen to known how to solve that let me 
> know.
> 
> In the end I did recompile the all Machinekit on BBB, took a while but it 
> eventually worked and I got the dev. env. working now.
> 
> You may also want to look at the timer/capture modules, both in the 
>> ARM system (with Linux drivers) and there's one module within the PRU 
>> domain.  You can use these to time pulses and you will get several 
>> orders of magnitude better accuracy (~10 nS) vs. trying to monitor the 
>> signal with PRU software (~1-10 uS), but that may or may not be 
>> important depending on the PWM frequency range.
> 
> 10uS is already overkill for my needs ;)
> I'm reading feedback signal from ClearPath motors 
> 
>  and 
> the PWM frequency is only 50Hz. Also I'm using regular GPIO inputs because 
> there is too much constraint with dedicated PRU inputs pinout.
> Since I saw quite few video with people using those same ClearPath motors 
>  on 
> their CNC, I'm sure many would benefit from having this feature in 
> Machinekit.
> 
> Also I would be happy to contribute to Machinekit project so I was 
> wondering what are requirements/process to add a feature/push request to 
> Machinekit official source code.

Just fork the repo on Github, make your changes, and submit a PR.

> In order to integrate it at best into Machinekit source code, that would be 
> great to have feedback on some question:
> @Charles: As it seem you have done a lot of work in the hal_pru_generic 
> driver, your feedback would be valuable :)
> 
> Since I'm not using dedicated PRU inputs, reading a regular GPIO input pin 
> takes ~170ns (~190ns for GPIO bank 0). For this reason, I aim to read GPIO 
> bank(s) not more that once per pru period and only if needed.
> 
> I see 2ways of doing that:
> 
>1. read GPIO inputs "globally" (in similar way as it is done for GPIO 
>outputs in pru_wait.p 
>
> ).
>  
>This requires to add some code in pru_wait.p 
>
> 
> and/or pru_generic.p 
>
> 
>  and 
>therefore extends a bit the overall pru period. The major advantage is 
> that 
>it would allow any others hal pru "modules" to use any GPIO inputs (the 
> hal 
>pru encoder could then be updated to work also with regular GPIO inputs).
>2. read GPIO inputs "locally" in the PWM reader pru task I'm 
>implementing. The drawback we will need to re-read GPIO input bank in 
> every 
>hal pru "module" that use them and therefore wasting PRU period time.
> 
> I see the first solution as the best one.
> Looking further, I saw that there is no much unused/free space in PRU 
> register (r0-32), there are pretty much all used for something. 

There are quite a few unused registers.  See the scratch/reserved
registers (used to talk to the hardware multiplier):

https://github.com/machinekit/machinekit/blob/master/src/hal/drivers/hal_pru_generic/pru_generic.p#L81-L85

You could also use the per-task registers (R4-11) and a chunk of the
scratchpad registers.

> However, I 
> thought about this solution (using GPIOn_Clr and GPIOn_Set):
> 
>- every time a PRU module/task want to read a GPIO pin, it set the 
>corresponding bit both GPIOn_Clr and GPIOn_Set registers. (I believe pru 
>module/task using GPIO as output never set both GPIOn_Clr and GPIOn_Set 
> for 
>the same pin at the same time since that would be a non sense).
>- somewhere around pru_wait.p 
>
> 
>  check 
>if the result of logical AND (GPIOn_Clr + GPIOn_Set) differs from 0. If 
>it is then, perform a "long" (~170ns) reading on GPIOn and store the 
> result 
>in GPIOn_Set. To avoid conflict with other GPIO outputs, only store 
>bits/pins where a read was requested. Then the PRU module/task that 
>requested the reading can read the pin state in GPIOn_Set on the next 
>pru period.
> 
> or maybe there is some easier solution allocating/using PRU RAM instead of 
> direct PRU register r0-32 (GPIOn_Clr / 

[Machinekit] Re: Rotary CNC + Bamboo + BBB + CRAMPS?

[Oleg Gavavka]

Keep eye on Revolve ( https://www.thing-printer.com/revolve/)
when it will be released you could use same system but with better price, 
estimated at 100$-120$ range



пятница, 22 февраля 2019 г., 5:31:53 UTC+2 пользователь jonas hauptman 
написал:
>
> Hi,
>
> We are new to your group and to machine kit but hoping the community might 
> have some feedback for us.  We are trying to develop a Rotary 4 axis CNC 
> router to machine bamboo poles into precise joints.  We believe this 
> will require six motors and also a scanning function as bamboo poles are 
> highly irregular in size, shape, and straightness.  Our project goal is to 
> democratize CNC rotary machining with a low-cost high-performance machine 
> for bamboo.   A material that has a huge environmental and 
> mechanical upside for both the developed and developing world.  
> Presently it is difficult to use it in a high precision fashion and we hope 
> to change that.  Initially, we planned to use a 3d printer Arduino boards 
> and Marlin to control the machine but eventually realized we would have 
> trouble independently controlling six motors and true 4 axis machining.  We 
> have a little experience with LinuxCNC, I built a CNC Router Parts kit and 
> outfitted it with a custom electronics bundle that Len from Probotix was 
> kind enough to create for me around there standard control system (Unity). 
> I am a huge fan of the Probotix machines and controls but we are trying to 
> develop a machine that in total costs around $500 to build 
> including computer, scanning camera, touch display, completely mechanical, 
> electrical and CNC system.  Our earlier prototypes used some open 
> source components designs and still share some common strategies with 
> the Sienci Mill One Kit V3.  Realizing that the cost of a full computer and 
> control system even on Linux was too expensive and that Arduino with GRBL 
> lack the horsepower and software features we need we are trying to develop 
> our strategy and prototypes around the Beaglebone with a Cramps Cape.
>
> I am posting hoping to begin to build a community around our project and 
> looking for insights of any kind especially around our need of a control 
> system for 4 axis and that can support our scanning needs.  I have 
> attached a series of schematic and photographic summaries of our progress 
> and look forward to input from the community.  
>
> Best regards,
>
> Jonas Hauptman
>
>
>
>
>
>
>
>
>
>
>
>

-- 
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.