Advanced Search

I run AXIS front end. You hit the start button as normal to run, hit the pause key (two to the right) to stop program, then use the arrow button (between the start and pause) to advance one block.

I must be lacking the right simulator. How do you run it block by block?

I don't think it is a machine problem. Running it in sim and going block by block, Z is not reaching end point and ramping across the cut. I did not find a change of M code in the area of code. It could be a DeskProto CAM problem, but this is just a guess.

What happens when you run the finish pass along the y direction?
Have you run the code with a tighter g64 like .005" or .001"?

I'm not sure I understand, the stepgen position feedback
should not be connected to anything when in spindle mode.

@Grotius,

how is everything going?  got quiet in here all of a sudden,  hope everything is alright with you!  drop a line and let us know!

Best Regards,

Chris

PCW wrote:

Then a change to velocity mode is trivial. To maintain
position reference when changing back to C mode, you likely
need to home the C axis to index. Does the spindle have an encoder?

That's correct. And I'm asking if is it possible not to take any action and just enable Spindle.
Example: spindle mode -> axis mode -> rotate to 300 degrees -> enable spindle with MDI command
How it works now: spindle mode -> axis mode -> rotate to 300 degrees ->rotate back to 0.0 -> enable spindle with MDI command

For the first mode change Spindle to Axis I'm, disabling (stepgen.position-reset = true). It mean that nothing happen with stepgen.position-fb (it be 0.0 instead of rotation count). So when I'm enabling Axis with joint.pos-fb == 0.0 everything is fine. But I can't do it twice OR I need somehow set stepgen.position-fb to zero with joint.pos-fb before enable Spindle mode.

 

Summary: For test purposes (for this problem), I'm cutting two ramps, one up, one down, in a 2" square. A lot of the resulting ramps are smoothly surfaced, but there are places where the z level is incorrect, leaving a raised area. I'm thinking it isn't hardware because the same error pattern repeats: ramp up/ramp down, moving the test pattern in Y, moving it in X, and changing the Z level (using thinner stock). The pattern repeats across all these conditions. I am at a loss. Software sounds likely, but there is no sign of the errors in simulation.

My machine: home built, open loop steppers, Gecko 540 drivers at 48V. Ball screws XY, Z is currently a fast lead screw. LinuxCNC/Axis, DeskProto CAM. I use a Bosch 1617evs router, it is cutting with a tapered ball nose bit, end diameter 1/8".

This very likely is not a LinuxCNC problem, but in my experience, this forum has some very sharp and responsive people on it. I've been working on this for a month.

Thanks,
Steve

Hallo,die Änderung hat die ersten Ergebnisse gebracht.Das kalibrieren wird ausgeführt. mit g54 gespeichert undist auch in der Werkzeugtabelle sichtbar.Ein werkzeug in z antasten, wenn man ca 2mm bis zur fläche fährt, geht auch.danke für deine unterstützung...

Hallo,beim mittelpunkt finden, wird nicht der richtige Durchmesser ausgegeben. dm 14 statt dm 17.
In der werkzeugtabelle ist der mess-durchmesser mit 6mm angegeben. Hat jemand eine lösung?
karlhe 

problem solved, custom_config.yml was outdated. thanks anyway!

Mecanix wrote:

Word of caution on the Wiz Lite Module though. In a hostile environment it switches from full/half duplex 10 to 100mbps all on its own. This is because the 3 PMODE pins are left floating. If you can, jump-wire those UP on a 4k7 and that'll sort it. 
 

give me more details please ,experience or in theory? would everything stop working or would it cause persistent issues? Ive been running these for about 8 months now and havent seen anything too bad, so i am curious

qaywsxedc wrote:

Hello,
Thx for the great work to all contributers. I read this huge threat and hopefully i did not miss my problem. i flashed an old nvem V2 with ethernet with Version 1.0.0
And it worked like a charme. Ping Test fine and even linuxcnc on first try thanks to the videos...
Now my problem... I just have the basic config with 3 Axis as default. The config upload fails...it prints out all Infos, but the upload fails with timeout. I try to solve IT but didn't find the problem. Maybe i can't write on the nvem.
I read it between threats but didn' t find an answer. With full config i do not need to change the config? How do i flash with full config?

Thanks for your Help
Btw. I tried the rt version... Flashing works but i can't ping it. If i get it right, my nvem is too old?
Regards

If your board is the RT1052, the only firmware you should be loading is this one

github.com/scottalford75/Remora-RT1052-c...ora-rt1052-3.1.3.bin, try this one and report back

In hal I have pin 10 connected to estop-exp. 


I don't know how I should connect the alarm cables.... I have right now connected alm+ to input 10 of the bob and alm- on the ground. 

If I create a fault in the driver so that the alarm goes off and linuxcnc stops but the driver does not emit a red light or any warning. 

If I create the fault without connecting the cables, the red LED flashes.

i knew you were working on something modular but you exceeded all my expectations, respect !

WOW !!!!!

fest wrote:

I finally finished designing my modular design idea: github.com/festlv/rioctrl-hw

Still have to actually build & test it- I'm fairly sure that there will be f-ups, just hope that nothing too major
 

Hi festl,
had somehow overlooked your post, something is wrong with my email notification

very nice !!!

will take a closer look and am looking forward to the first tests