Advanced Search

Have a look at the foam simulation config 'configs/sim/axis/foam/axis_foam.ini'.

 

Basically it produces two separate previews, one for XY and one for UV

[edit]
Note that the Z,W height comes from the gcode lines (there are no actual Z or W axes)
(AXIS,XY_Z_POS,5)
(AXIS,UV_Z_POS,30)

[edit2]
The idea is that the two cones represent the end of a hot wire cutting through styrofoam
 
 

Yes, that is the goal.

One thing that is still 100% unclear for me is foam cutter visualization. There is some magic code in Gremlin for this. I never worked with such kind of machines. Is there any LinuxCNC documentation regarding foam cutter setup? Or may be one can explain in short?

Please read the error report caefully.

This is the cause:

CANNOT FIND FILE FOR:try7_mill.hal

Ha - now that you pointed it out, it's obvious !
I'll look into it.

I have attached error.report file below

Getting POSIX realtime error and not able to launch the linuxcnc software.

ip a is ok, showing 10.10.10.100. Ping 10.10.10.10 is also ok, getting response from the board. Using Debian GNU/Linux 12 (bookworm), linuxcnc 2.9.2 with kernal version '6.1.0-21-rt-amd64'.

Is this kernal version is ok or need to install another kernal?
 

Hey guys has anyone on here used an AC servo spindle motor with just a parport break out board? My finger is hovering over the buy now button but just want to see if anyone has tried before I become the lab rat

(I have a two parport bob set up if that helps)

thanks guys

Got the 400w version, machine is a bar feeder. Not finished yet so no report on longevity but it was easy enough to setup and get running

The connections between the PID outputs and PWM values are missing.
In addition, the PWM enables are missing.

For example, this is whats missing for joint 0:

net joint.0.output => [MESA](BOARD).0.pwmgen.00.value
net joint-0-enable => [MESA](BOARD).0.pwmgen.00.enable

MAKE VERY SURE you have the drive enables working so you
disable the drives if you get a runaway and following error.

There does not seem to be a 7I97T output dedicated to drive enable
so this MUST be fixed before adding the missing PWM connections.

Edit: The PWM enables shown above will work for controlling the drive
enable pins on the 7I97Ts TB3 connector.


 

If you have a VFD, modbus (which I used with ethercat), or PWM from Rtelligent IO module, 

@GuiHue, EL7041 is also an option but it includes an input for 48 Volt power for stepper motors.

If it can count a single signal then it can work.

If the low level encoder code does not provide a velocity pin,
you could calculate frequency using the ddt component,
but that will introduce noise proportional the servo thread jitter
relative to the servo thread period.

You could tradeoff bandwidth for noise by running the ddt thread
at a multiple of the servo thread period or low-pass filtering 
the result of the ddt.

The Mesa encoder velocity estimation works well for this as it
calculates velocity as counts/time_between_those_counts
The time between counts measured by timestamping
every count, so basically measures frequency based
on a crystal clock.

I've got the equipment & ability to do that sort of work, based in Sydney myself, used to work as a tech for one of the larger EFTPOS companies doing smd board level repairs. I could even just look at it for you you.

But fully understand if you want to go through Mesa.

PCW, thanks for that.

Gave the contacts a good wash with isopropyl alcohol and preliminary results seemed better, but stats show about 50 % lost packets.

I will try again tomorrow.

Regardless of solution, I need to purchase a replacement board, if only as a spare for future.
Are there any agents in Australia (I am in Sydney) ?

John.

You might try cleaning the 7I96 RJ45 socket in case it's contaminated/corroded.
Worst case, you can return it to Mesa for repair/replacement

My 3-axis mill operated for over a year with LC 2.8.4 on a RPi 4B 4GB.
Then I tried to get the WiFi working. failed the SD card, so started to install LC 2.9.2 with a new SD card.

Problems from the start resulted in me changing to a RPi 4B 8GB, propped up outside the cubicle.

Now, when pinging, I get serious packet loss.
All addresses etc correct as I have had Axis opening on occasion.
The original installed ethernet cable is 250 mm long, and I have a general-purpose spare 10 m long on a spool.

With either cable connected, either way around, finger stressing the connection at the 7i96 socket interrupts packets.
The same stressing at the RPi socket is reliable.
Sometimes, with a bit of stressing, the monitor LED on the 7i96 socket extinguishes.
Sometimes packets will start on the ping, but other times not, with a bit of stressing then starting the packets.

It would appear the Socket on the 7i96 is the problem.

Any suggestions ?

John.