Advanced Search

Aciera wrote:

I have not used the anglejog component other than playing around with the sim config. As I understand it the 'scale' factor is used to avoid stair stepping in the tool path. Maybe the original discussion can give you some more clues:
forum.linuxcnc.org/38-general-linuxcnc-q...mode?start=10#253252

[edit]
I would tend to use the default values used in the sim config and adjust the
'max_vel',  'max_accel' pins (and possibly 'accel_fraction_in' for fine tuning) 

Thanks for your help. I should play with the sim config, I'm not sure how to do that?

That's a bug with the 7i76eu I/O section. I'll fix that.

JT

Is there any logging behind the scenes to know that really happened? As this was working reliably in the past, I was not 100% focused on watching it. It would be good to know when it was tripped and what the feed rate and direction were.

Thanks

Machine is going great and now its time to start adding more.

So firstly - ohmic sensing with the 7i96 board?? i'm sure i have see how this connects, but for the life of me cant work it out. Hookup is simple enough, configuration is what's got me.

Secondly - Air scribe. Hardware is all together. just need to get the post to work for it in sheetcam.

Links to help if you have them please.

& Video's for when you are bored.

www.youtube.com/shorts/XuxqHAO2k5w

I see, but for cutting aluminium (i.e. my machine runs at 4000mm/min with a 8mm tool) and high speed machining applications, I'd say this probably starts to play a much bigger role?

here are my files  .hal and .ini

Thanks

@mBender
you can use all pins freely and the 1.8v pins are well suited as inputs as they are 3.3v tollerant.

@Cam
Max 10 works, but not the onboard Ethernet, you need to use W5500 or SPI

Cheers,
Olli

Hi,

I have a Terasic DECA Max 10 (10M50DAF484C6GES) fpga dev board that i'm thinking about using as my LinuxCNC hardware step generator. If anyone has any thoughts on why this won't work that would be amazing before I jump into trying to get this to work.

Board details are here:
www.terasic.com.tw/cgi-bin/page/archive....yNo=&No=944&PartNo=1

Cheers,
Cam

This looks great. Thanks for your work!

I will probably use it for IO and rotary encoder counting for my control panel (servos are ethercat).
Rotary encoders for MPG / feed override / spindle override.

ok great.

I don't see any smoking gun.
Can you test the simulated auto tool config to see if it does the same thing?
You simulate the probe with the on screen button (when the label says probe)

Sounds like you have some electrical noise or maybe need to add some debounce. Remove slow feed by changing to 0.0 and just try using fast feed rate. If you move to slow probes can sometimes double trigger which cause issue. It's best to use a bit more speed. As long as you calibrate at the speed you probe at, you should retain consistent repeatable results

good afternoon!
today I played around with MesaCT for the first time, and I saw that the generated configuration (for my 7i76eu) has a different naming / nomenclature for my outputs than pncconf...

pncconf outputs lines like this:
net dust-removal-out motion.digital-out-03 => hm2_7i76e.0.7i76.0.0.output-03

while mesact creates these lines:
net flood-output iocontrol.0.coolant-flood => hm2_7i76e.0.gpio.031.out

where does this "gpio" come from? is this redundant or did I do something wrong in the tool?

regards!

I have had probing working for a bit and its been solid.  But today I had a strange event happen, not sure if it was me or something else.  I don't believe the settings are different than before.  Not sure what to even check.

I was probing Z only, and things started fine, the probe was going at the slower rate, tripped, then instead of backing off (Z+) it continued at the fast feed rate (Z-).  Another ruby tip smashed.

I tried again, and it did the same thing.  For a third test, I jogged x-y away from the part, and also jog z+, and tried on a "test" part (just a flat pen held off), and it worked fine, and now it seems to work fine.

What would cause a probe cycle to continue vs backing off?  Or did I make some mistake.  Either way, I want to avoid this again... probe tips are expensive.

Thanks! I should have been able to figure that out. I went deep into a deep dark hole. Sorry, I missed the obvious. Again Thanks!

Probe z in the fixture, then mount your part, select probe position only, probe corner, then zero x and y.

Probe only proves and finds the corner without setting a new work offset. But will be positioned over the corner.