Advanced Search

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.

What is the model of your servo driver?

Looks really really good.
Coffee & Beer ?

G0 & G1 ?

    I'm about to order this control board that I will mount to the belt cover of my knee mill. The two black buttons (bottom right) are looking for a feature. So please chime in with "you really need a button for ....."  whatever you think I have overlooked.The display (WIP) is capacitive touch-screen and will have several modes Manual, MDI, calculator, etc. with displayed values and additional mode appropriate buttons. 

As I mentioned in my original message, anything larger than coffee maker i.e., machines that can cause harm requires an estop; a small 3d printers would fall in the coffee maker category, the only harm a 3d printer can cause is burn to your pinky.Since you are from Germany before selling or letting some else use the machine you refurbished double check your country machine wiring regulation.

Many years ago, I was assigned the design of the electrical controls of a machine for export to Germany. My hair went white trying to decipher the German DIN Electrical standard. DIN is the most rigid standard in the world, it even tells you if toilet paper hung under or over) . 

In your case a simple Estop/reset might not be sufficient, you might need a CE certified safety relay, if bought new it will cost you more than 7i92+7i77.

Don’t let those macho cowboys tell you otherwise, liability can ruin you all the way to your grave. In law, ignorantia juris non excusat which means "Ignorance of the Law excuses not" is a legal term holding that  a person who is unaware of a law may not escape liability.

Hello, I have recently gotten another 7i96s board and I am trying to put the same MPG firmware on there I got from PCW a few months ago. It worked fine on my other 7i96s board but not this new one. I am getting an error during the verification. I'm just wondering if there is something that has changed in the past few months that could have caused this, and if possible, how to fix the firmware so it reads correctly.

Verify Firmware
Returned: Failed
Checking file... OK
  File type: Efinix bin file
Verifying FLASH memory sectors starting from 0x100000...
  |
Error at 0x10004C expected: 0x16 but read: 0xA

Attached the firmware in question. Here is my previous post regarding this firmware.

here is the wiring for speed mode

 

cakeslob wrote:

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

Nothing bad at all, it's a great module overhaul. The downside of floating state pins is randomness, therefore not a persistent issue.

Fwiw the PMODE select pins have internal/weak resistors. Meaning; if the environment the system is operating in is an ideal one then most likely the internal weak resistors will be sufficient. However, (in my case), if there is quite a bit of noise/emi/gamma rays/bitflips/coffee/radiation/traffic/manyothers... you may experience strange 10mbps half-duplex startups and/or strange network negotiation. The workaround/fix to that is to harden the PMODE pins' state with pullups (4K7) - see source schematic (pardon my crayon!).