Advanced Search

Thank you very much, HALSHOW has now appeared in the window. The green LED on the 7i77 lit up with OK status

tommylight post=301794 userid=17274Do you mean mesaflash ?
MesaCT can flash the firmware from the GUI.

Yes MesaCT (Mesa Configuration Tool).  I have the *.pin, *.bin, and *.vhd files for the7i96s_5abobrcd firmware.

So after flashing the 7i96S and connecting the BOB.  Will MesaCT recognize the BOB being connected?  Do I then need to assign the BOB to the P1 connector?

 

I assume you mean qtplasmac?

Go to parameters and increase your (can't remember exact term) void anti dive. This should help but if not try decreasing (or increasing) your p term in your pid.

My guess is it's a pid issue (or you are cutting too slow)

Takes a bit to get it tuned perfect but when it is.....it's sweet. I can cut for hours on a 8x4ft sheet and never touch the torch to the table

I am having a very odd problem, I am running QTPlasma and using the built in THC. I can cut parts and sometimes the torch takes a dive at the very end of cutting. The attached images show what I get, if it were not for the break away torch mount I may have broke my torch. 
 
 
 
 

Hi Andrew,

Will look tomorrow if i can fix the scurvy.
The clothoid lib compiles in qt. However loaded into the lcnc project. It has problems with c23.
So i can make first shared lib of the clothoid lib and then just link it.
 

I think there's a disconnect between your main hal and the vista hal.  The vista has a spindle.is-on signal, but your halshow was spindle-is-on signal.

My guess is that the vista hal file hasn't been updated (by vista) since the multi-spindle changes in LCNC, so spindle pins are usually spindle.0.something.

You'll probably need to add an or2.component to permit the spindle to be started via the GUI, physical button (if present), and the vista pendant.

Can you post your main hal file(s)?

The 7I77 will not appear in halshow until you:

1. Have the 7I77 connected to the 7I96S P1 connector with the proper cable

2. Have 5V power applied properly to the 7I77 (and the 7I96S P1 power option matches the 7I77 5V option)

3. Have field power applied to the 7I77 (and 7I77 W1 Left)

I don't think pncconf knows how to make a 7I96S+7I77 configuration so you may need to merge
a plain 7I96S configuration with say a 7I92+7I77 configuration (for the analog/encoder/7I77 I/O setup)

below the update carried out successfully! but without recognition of the 7i77 board even after restarting the system and electricity

cnc@cnc:~/Documentos/7i96s/configs/hostmot2$ sudo mesaflash --device 7i96s --addr 10.10.10.10 --write 7i96s_7i77d.bin --reload
Checking file... OK
  File type: Efinix bin file
FLASH memory sectors to write: 11, max sectors in area: 16
Erasing FLASH memory sectors starting from 0x100000...
  |EEEEEEEEEEE
Programming FLASH memory sectors starting from 0x100000...
  |WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
Board configuration updated successfully.
Checking file... OK
  File type: Efinix bin file
Verifying FLASH memory sectors starting from 0x100000...
  |VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
Board FLASH memory verified successfully.
cnc@cnc:~/Documentos/7i96s/configs/hostmot2$ 

Thank you very much. When upgrading the system from LinuxCNC 2.8.4 to LinuxCNC 2.9.2, I got the newest version of the MesaFlash software which was 3.4.0 and now it is 3.4.9 on this new system. With this I was able to update the firmware successfully. But unfortunately I have not yet been successful in recognizing the 7i77 board in the LinuxCNC system. I'm using the LinuxCNC Pncconf Wizard, and the ports on the 7i77 board don't appear in place of the P1 connector, they don't appear in the configuration settings, please, is there any other procedure for the board to be recognized?Pncconf does not appear 7i77

Halshow does not appear 7i77

I think the only c++23 feature I used besides std::println is std::expected, you should only need to change a couple lines to just return the value directly. It's in scurvy::solve in scurvy.h. I don't really need them, they're just convinient to use to do fast work. On systems with old gcc versions I usually just compile the latest version of gcc and install to /opt.

I just added a Line class to the clothoid project and pushed to github. This is technically right, but its also wrong. Hopefully I just overlooked something. 

@Andrew,

The biclothoid lib runs now. Will try to get visual output in opencascade from your main file example.

@Andrew,

Amazing work so far !.

I cloned the scurvy lib today. It is to be compiled c++ 23.
I use up to c20. For some reason i could not resolve to
get it c23 compiled. Looking for updating the compiler, but was newest version.

Then i could convert the println functions to printf. But there where also other c23 function that where more
complicated to convert.

Is it possible to convert to c20 or lower? This should be perfect.

Now going to look at the clothoid lib. Maybe i have questions later on. Thanks so far.

Evaluating the derivative at only 5 points is giving an integral with an error of around 1e-11 to 1e-17.
This is perfect. < 1e-6 is acceptable.

Another question.
I tested 2 nurb libs today. One of them was only 2d and very slow.
The other was OpenNurbs , this one is also very fast. And did a good job for 3d.

So i could create the 7 controlpoint example in opencascade. This works ok.

The question is, if i want to make a nurb with 100 waypoints for example. I don't know how the knot
vector should look like. Maybe i have to look further to understand how to build a nurb going over all the
gcode lines.

I was able to dynamicly load the points, load the knot vector. But the result was not ok.
Maybe you have experience with it?

The current mill in use is a Tormach 1100 series 3, when it comes to using the arrow keys on the keyboard it becomes stuck and tends to over jog. I have found a temporary solution, where if you are to ssh into the same computer the issue is then fixed.
Is there any way to get rid of the jog without having to ssh.

# 0---vc-p4s Control Pendant
loadusr -W vc-p4s

loadrt and2 names=and2.vc
addf and2.vc servo-thread

# 1---LCD reletive Coordinates
net axis.0.pos-relative halui.axis.x.pos-relative => vc-p4s.axis.0.pos-relative
net axis.1.pos-relative halui.axis.y.pos-relative => vc-p4s.axis.1.pos-relative
net axis.2.pos-relative halui.axis.z.pos-relative => vc-p4s.axis.2.pos-relative

# 2---JOG
net axis.0.jog-en vc-p4s.axis.0.jog-enable => axis.x.jog-enable joint.0.jog-enable
net axis.1.jog-en vc-p4s.axis.1.jog-enable => axis.y.jog-enable joint.1.jog-enable
net axis.2.jog-en vc-p4s.axis.2.jog-enable => axis.z.jog-enable joint.2.jog-enable
net jog-scale vc-p4s.jog-scale => joint.0.jog-scale axis.x.jog-scale
net jog-scale vc-p4s.jog-scale => joint.1.jog-scale axis.y.jog-scale
net jog-scale vc-p4s.jog-scale => joint.2.jog-scale axis.z.jog-scale
net jog-counts vc-p4s.jog-counts => joint.0.jog-counts  axis.x.jog-counts
net jog-counts vc-p4s.jog-counts => joint.1.jog-counts  axis.y.jog-counts
net jog-counts vc-p4s.jog-counts => joint.2.jog-counts  axis.z.jog-counts
net jog.0.cont-plus  vc-p4s.jog.0.plus  => halui.axis.x.plus halui.joint.0.plus
net jog.0.cont-minus vc-p4s.jog.0.minus => halui.axis.x.minus halui.joint.0.minus
net jog.1.cont-plus  vc-p4s.jog.1.plus  => halui.axis.y.plus  halui.joint.1.plus
net jog.1.cont-minus vc-p4s.jog.1.minus => halui.axis.y.minus halui.joint.1.minus
net jog.2.cont-plus  vc-p4s.jog.2.plus  => halui.axis.z.plus halui.joint.2.plus
net jog.2.cont-mimus vc-p4s.jog.2.minus => halui.axis.z.minus halui.joint.2.minus
net jog-speed vc-p4s.jog.velocity => halui.axis.jog-speed halui.joint.jog-speed
net motion-in-position motion.in-position => vc-p4s.is-moving
setp axis_0_max_velocity [JOINT_0]MAX_VELOCITY
setp axis_1_max_velocity [JOINT_1]MAX_VELOCITY
setp axis_2_max_velocity [JOINT_2]MAX_VELOCITY

# 3---FOR 4TH AXIS, REMOVE # FROM THE FOLLOWING LINES
#net axis.3.pos-relative halui.axis.a.pos-relative => vc-p4s.axis.3.pos-relative
#net axis.3.jog-en vc-p4s.axis.3.jog-enable => axis.a.jog-enable joint.3.jog-enable
#net jog-scale vc-p4s.jog-scale => joint.3.jog-scale axis.a.jog-scale
#net jog-counts vc-p4s.jog-counts => joint.3.jog-counts axis.a.jog-counts
#net jog.3.cont-plus  vc-p4s.jog.3.plus  => halui.axis.a.plus halui.joint.3.plus
#net jog.3.cont-mimus vc-p4s.jog.3.minus => halui.axis.a.minus halui.joint.3.minus
#setp axis_3_max_velocity [JOINT_3]MAX_VELOCITY

# 4---FOR 5TH AXIS, REMOVE # FROM THE FOLLOWING LINES
#net axis.4.pos-relative halui.axis.b.pos-relative => vc-p4s.axis.4.pos-relative
#net axis.4.jog-en vc-p4s.axis.4.jog-enable => axis.b.jog-enable joint.4.jog-enable
#net jog-scale vc-p4s.jog-scale => joint.4.jog-scale axis.b.jog-scale
#net jog-counts vc-p4s.jog-counts => joint.4.jog-counts axis.b.jog-counts
#net jog.4.cont-plus  vc-p4s.jog.4.plus  => halui.axis.b.plus halui.joint.4.plus
#net jog.4.cont-mimus vc-p4s.jog.4.minus => halui.axis.b.minus halui.joint.4.minus
#setp axis_4_max_velocity [JOINT_4]MAX_VELOCITY

# 5--FOR 6TH AXIS, REMOVE # FROM THE FOLLOWING LINES
#net axis.5.pos-relative halui.axis.c.pos-relative => vc-p4s.axis.5.pos-relative
#net axis.5.jog-en vc-p4s.axis.5.jog-enable => axis.c.jog-enable joint.5.jog-enable
#net jog-scale vc-p4s.jog-scale => joint.5.jog-scale axis.c.jog-scale
#net jog-counts vc-p4s.jog-counts => joint.5.jog-counts axis.c.jog-counts
#net jog.5.cont-plus  vc-p4s.jog.5.plus  => halui.axis.c.plus halui.joint.5.plus
#net jog.5.cont-mimus vc-p4s.jog.5.minus => halui.axis.c.minus halui.joint.5.minus
#setp axis_5_max_velocity [JOINT_5]MAX_VELOCITY

# 6---FEED OVERRIDE
setp halui.feed-override.scale 0.001
net feed-enable vc-p4s.feed-override.count.enable => halui.feed-override.count-enable
net feedrate-counts vc-p4s.feedrate-counts => halui.feed-override.counts
net feed.value halui.feed-override.value => vc-p4s.feed-override.value

# 7---RAPID OVERRIDE
setp halui.rapid-override.scale 0.001
net rapid-enable vc-p4s.rapid-override.count.enable => halui.rapid-override.count-enable
net rapid-counts vc-p4s.rapid-counts => halui.rapid-override.counts
net rapid.value halui.rapid-override.value => vc-p4s.rapid-override.value

# 8---MAX VELOCITY
setp halui.max-velocity.scale 0.001
net max-enable vc-p4s.max-velocity.count.enable => halui.max-velocity.count-enable
net max-counts vc-p4s.max-counts => halui.max-velocity.counts
net max.value halui.max-velocity.value => vc-p4s.max-velocity.value

# 9---SPINDLE OVERRIDE
setp halui.spindle.0.override.scale 0.001
net spindle-enable vc-p4s.spindle-override.count.enable => halui.spindle.0.override.count-enable
net spindle-counts vc-p4s.spindle-counts => halui.spindle.0.override.counts
net spindle.value halui.spindle.0.override.value => vc-p4s.spindle-override.value

# 10---PROGRAM
net program.is-idle    halui.program.is-idle    =>  vc-p4s.program.is-idle
net program.is-paused  halui.program.is-paused  =>  vc-p4s.program.is-paused
net program.is-running halui.program.is-running =>  vc-p4s.program.is-running

net program-start-btn halui.mode.auto and2.vc.in0 <=  vc-p4s.program.run  
net program-run-ok and2.vc.in1 <= halui.mode.is-auto
net remote-program-run halui.program.run <= and2.vc.out

net program.pause  vc-p4s.program.pause  => halui.program.pause
net program.resume vc-p4s.program.resume => halui.program.resume
net program.stop   vc-p4s.program.stop   => halui.program.stop

# 11---ZERO
net zero-x vc-p4s.zero-x => halui.mdi-command-05
net zero-y vc-p4s.zero-y => halui.mdi-command-06
net zero-z vc-p4s.zero-z => halui.mdi-command-07
net x-go-to-zero vc-p4s.x-go-to-zero  => halui.mdi-command-08
net y-go-to-zero vc-p4s.y-go-to-zero  => halui.mdi-command-09
net z-go-to-zero vc-p4s.z-go-to-zero  => halui.mdi-command-10

# 12---SPINDLE
net spindle.is-on halui.spindle.0.is-on =>  vc-p4s.spindle.is-on
net spindle.start  vc-p4s.spindle.start  => halui.spindle.0.start
net spindle.stop  vc-p4s.spindle.stop  => halui.spindle.0.stop

# 13---E-STOP
net estop vc-p4s.estop.activate => halui.estop.activate
net reset vc-p4s.estop.reset => halui.estop.reset
net estop-is-activated halui.estop.is-activated => vc-p4s.estop.is-activated

# 14---MACHINE
net machine-on  vc-p4s.machine.on  => halui.machine.on
net machine-off vc-p4s.machine.off => halui.machine.off
net machine-ison halui.machine.is-on => vc-p4s.machine.ison

##### P4-S PENDANT SETTINGS #####

# 15---STEP SIZE, SET 0 TO SKIP
setp stepsize-1     0.0001

# DEFAULT
setp stepsize-2     0.001

setp stepsize-3     0.01
setp stepsize-4     0.1
setp stepsize-5     1
setp stepsize-6     0
setp stepsize-7     0
setp stepsize-8     0
setp stepsize-9     0





 

Pressing the spindle start sequence on the pendant causes spindle.start to illuminate momentarily, and then illuminates spindle-is-on. The spindle stop sequence on the pendant causes spindle.stop to illuminate momentarily, and turns spindle-is-on back to its normal state.