Advanced Search

in the line above 'dout-01' is a signal name
'hm2_7i96s.0.ssr.00.out-01' is a pin name

hence you get an error using the 'setp' command on the signal name
Try using (note sets instead of setp)

Danke für den Hinweis. leider ohne Erfolg

Hi all,

I’m quite new here and still have a lot to learn, thanks all for your patience. I have been trying my best to get good print results with an Ender3 with a 100mm round build plate on two rotational axes. I wrote a blender addon that does ‘indexed’ 5 axis printing.
My setup with the pi 5 and gpio was not a suitable solution. I am hoping to get my octopus v1.1 working with remora. 

1) I successfully flashed the mcu
2) my wiring is correct
3) I get no read response from spi connection
4) when I start Linux cnc with my config, it says that joint.5.scale is not found ( extruder)

I will attach my hal and ini files in a bit. 

Thanks again, im reading away. Also I did know that RPI needs the parallel hat by byte to bot. When looking at the hal file form them it doesn't show the GPIO code in it like yours does thanks again.

I think if you look into remora code. They are also sending hex codes payoad via spi such as estop is 0x65737470.

If you would integrate that into remora then it would be more useful.

I have downloaded the image, edited the files on the image and are able to remote into the pi.

SPI has been enabled from console.

Currently waiting on time to do the hardware modification of desoldering the male header and soldering on a female header on the bottom of the Pi 4

Hey Everyone,

I am working on getting a cnc mill to autoload the next part.
The general idea is a motor will turn a vise until it senses it opened. Then the spindle will use a vacuum sucker on a pneumatic cylinder (connected to the spindle head so it can move (router style)) to remove the old part, drop it off, then grab the next part, close the vise, probe the new stock and resume machining. 

I can code most of the movements in a gcode subroutine but am struggling with the logic for the vise (air powered) motor and pneumatics. 

hal file
# Vise Outputs
net dout-01    => hm2_7i96s.0.ssr.00.out-01
net dout-02    => hm2_7i96s.0.ssr.00.out-02
#vise sensor
net din-01     <=  hm2_7i96s.0.inm.00.input-09-not

made the custom mcode that can control the output but only with the signal not the pin
#!/bin/bash
halcmd sets dout-01 True
exit 0

if i try (using the hal command in the "halshow" to test) 
setp dout-01 True
or
getp din-01 

I get an error that that pin doesnt exist, and with no way to read the signal that i can see in halcmd that leaves me with pins only. linuxcnc.org/docs/html/man/man1/halcmd.1.html

to my understanding "pin" is the software component, ui button, hardware IO, etc. Signal is the wirename that connects pins together. Looking at halshow it seems like din and douts are signals not pins themselves. 

So how would I create a pin? Now that i look at it again after typing all this...... seems like I could just use the pins "hm2_7i96s.0.ssr.00.out-01" directly and not rely on signals at all. Might get messy trying to remember what input/output is what without a signal. 

Any help would be great. I'm open to other ways of doing this as well 
 

I do not know a solution to do what you are asking for.
The question for me is, why the code stops?

If you just press pause, the program will continue after you pressed resume.

also recording the line might not help, as the interpreter reads ahead and so machining line 1000 interpreter may have already passed Line 1250

I imagine using python and code an own control might work.

Norbert

Da fehlt ein ganze "paragraf ???" oben die Joint 0

[AXIS_X]
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 30.0
MIN_LIMIT = -0.001
MAX_LIMIT = 24.0

Hi Grotius,

where are you stuck with equation 40? the thetas you already have from the prev equation (39) and the tilded x" y" z" are the transformed derivatives of the starting and end points. If we connect with lines they are all 0 eq. (26). With arcs they are given by eq. (30) + transformation.

bring your remora related discussion into this thread

www.forum.linuxcnc.org/18-computer/42276...rocontroller-via-spi

and upload your hal/ini files using the forums attachments please

Guten Abend, ich habe die INI, HAL und XML configrutaion in meine neue maschine kopiert, ist momentan nur ein Motor angeschlossen um diese zu testen. Leider bekomme ich folgende Fehlermeldung. Welche eintsellung muss ich zusätzlich an den Endstufen vornhemen ?
Gruß Tom

I spent some hours..

1) flashed the octopus MCU with dfu-util
2) draft version of HAL and INI files done
3) wiring pi5 correctly to the octopus
4) pi5 is running remora flexi os

The error is from linux cnc when it loads my config: joint.5.scale pin doesnt exist. If I do a show pin with halcmd it shows a bunch of joints unit joint.4.

HAL file
INI file

@Fabian,

Most of the math of Frego is already inside the 2d clothoid library.
There it solves the clothoid G2 problem using 3 connected clothoids.
As later on discussed on github, adding the z component to the xy was proposed by using the Frego 3d paper.

The new paper is for me more understandable.

I have noticed in the new paper, that the 2 gcode segments are transformed to a null plane first.

This same approach i used before when we construct a clothoid when 2 gcode segments share same plane.

Then the 2 gcode segments in 3d space are transformed to xy plane, clothoid is build in xy plane, clothoid + gcode segments are
transformed back to original 3d space position. This worked flawless.

So this part of the paper, we can almost skip. As we know the mathematics for it.

Attached a few files where i tried to implement paper equatations. They may contain wrong approaches.

For now i am stuck at eq.40.

@Collins,
Maybe this is the same as starting with a bspline from segment a to segment b. Then manipulate the spline trajectory
to get a G2 result and apply a clothoid property like
"a curve whose curvature changes linearly with its curve length"

I cannot say anything about your analog predicion machine, as i can't imagine how to appy it to our work.

 

I went with
net x-fault => joint.0.amp-fault-in <= hm2_7i96s.0.inm.00.input-04
so I get an error on x for all my axis. Because I wired all alarms in parallel. Which is absolutly fine. As long as the machine stops on any error