Advanced Search

PCW wrote:

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

Stepgen has two connections. To Spidnle and Axis. That's why it has both feedbacks: velocity-fb and position-fb.
 

Hey guys I have been going through some install hell so I have decided to start a new thread on the topic, so we don't clog up this thread with silly questions.
I'm going to copy ColdTurkey's example on the Remora thread using the live install version of LinuxCNC Debian, so anybody following will have the same starting point.
I am guessing anybody familiar with setting this up will overcome simple hurdles without thinking, but those of us that aren't really computer guys will struggle.
My only question I'll ask here though is should I do this for LinuxCNC-RIO or Riocore ?
Cheers.
Russell.

i thought the question was whether an estop via software is generally permitted.

Apparently yes,
e.g. the Amann Girrbach milling machines, which are much bigger than a coffee machine, cost several tens of thousands of euros, come from Germany and don't have one.
I think they have thought this through well enough.

And as I said, not all machines can simply be de-energised without creating even greater risks, a controlled shutdown is necessary there

Custom firmware should be flashed with mesaflash in a terminal.

JT

There have been reports of 3D printers catching fire.

This problem is related to the computer. I have disabled all the features that I can disable in the BIOS and now the problem is not visible.

So the configuration doesn't need modifying? 
Then it probably is not a configuration problem. Is there a way I can confirm I get an index-pulse with the halscope? I am not sure what signals I can watch which can confirm a successful index pulse? Unfortunately I don't have an oscilloscope.
Or are there more potential problems that can cause problems. 
When the machine reaches the g33 it just stops. spindle keeps spinning and I goes into pause. Is there a way I can check a log or something why the command isn't continuing?
Thanks for your help.

Hello everyone

First, thank you all for the work put into getting these drives running with linuxcnc. This is amazing!

I have a setup with 3x 1 kW motors and 23bit absolute encoders which works perfect.

Did some of you also notice this high pitch whining noise originating from the drivers when they are online? Maybe coilwhine? Are there means to eliminate this? EMI filter needed?

Mr_rookie wrote:

I tried ...

everything is working now.
i download linuxcnc_2.9.3_amd64.deb for raspberry pi 4 and they are working. thanks!!

AMD64 and Raspberry Pi 4??

everything is working now ....

I really think it's a miracle!!!

COFHAL wrote:

What is the model of your servo driver?in the attachment 

in the attachment

Thanks

Todd,
Thank you very much for your reply. I was able to take your logic and modify it to get what I needed. I really appreciate your assistance!
Thanks,
Dave

If you use Qtvcp to render the vismach panel, you can embed it with a command such as this:

[DISPLAY]
# Embed tabs
EMBED_TAB_NAME= qtscreen
EMBED_TAB_COMMAND= halcmd loadusr -Wn qtvcp_embed qtvcp -d -c qtvcp_embed -x {XID} vismach_mill_xyz


linuxcnc.org/docs/stable/html/gui/qtvcp-vismach.html

May be a mesact issue

I would just flash it by hand using mesaflash on the command line

(just tried with the zip file here and it works as expected)

Just for completeness what actual file did you edit to enable the spi interfaces ?

Was it:

/boot/firmware/config.txt <-This should not exist on the Linuxcnc image, neither directory or file. Unless the user creates it.
or
/boot/broadcom/config.txt <--This should be the file

I'd try reflashing, may have been a "glitch" when downloading.