Da es für die 7i92 mit dem Benezanbitfile schon was passendes gibt, wäre ich auch am schauen nach einer 7i92, da sollten ja die originales Bitfiles draufpassen. Die hier würde mir vorschieben..  de.aliexpress.com/item/1005010725599295....%7C_p_origin_prod%3A
 

Hallo! Wenn du dir die Mühe machen würdest eine Anleitung für das Bitfile zu schreiben wäre das Mega! Da muss ich mir überlegen was i h dir für einen Stein in den Garten werfen kann! Bild der Karte dauert leider etwas, ich hatte gedacht ein Bild angehängt zu haben, und aktuell gab ich keinen Zugriff auf die Bilder oder die Karte.. Der Link ist folgender : " pan.baidu.com/s/1e8-TJ5BXo_-pZYBvHPJc9Q?pwd=g7jh " .. Ich kann da nichts direkt runterladen, ich soll immer eine Software installieren, das hab ich auf einem alten Smartphone gemacht (ich bin da etwas paranoid), konnte aber nichts erreichen. Selbst mit zweitem Smartphone und Fotoübersetzer hats nicht geklappt..  Vielleicht bin ich einfach zu doof... Danke dir im voraus.. Gruß Thomas 

I used eCAM 5 and I'm happy with it, now I got the new 6 for a small CNC. I don't use it much, it's not my job, but the lathe part, according to a friend who uses it on a CNC lathe that we retrofitted together, is excellent.

StepperOnline wrote:

Thanks for the interest with StepperOnline's A6 servo system. At present, the StepperOnline A6 servo does not support torque-based homing functionality.

If not, why is torque-based homing in the user manual as an option? (i.e. homing modes -1 & -2, pages 74 & 75)

Are there any other features/options which are documented but not available?  That is, what features were removed from the JSS715N servos for the A6 version?

Fr3nzy wrote:

Would you suggest a hardware that is guaranteed to work with the latest repositories and EtherCAT?
 

Some second hand computer after leasing.
I use for ethercat HP 705 G3 AMD Radeon R7 A10-8770.
It is not newest, but small and powerfull.
In my opinion, you can buy very good computer for LinuxCNC for 50-100 USD.

Thanks for the interest with StepperOnline's A6 servo system. At present, the StepperOnline A6 servo does not support torque-based homing functionality.

tuxcnc wrote:

Fr3nzy wrote:

My motherboard is very old and doesn't support UEFI. Maybe I should use one that will support it.

You have the right to have a computer museum, but do not require anyone to help you maintain it.




 

Would you suggest a hardware that is guaranteed to work with the latest repositories and EtherCAT?

tuxcnc wrote:

The "EFI variables are not supported on this system" has nothing to do with BIOS setup.
This is common kernels RT problem (efivars disabled in config).
The solution is to add "efi=runtime" to the kernel parameters (once at boot or to /etc/default/grub).
 

"efi=runtime" is added and the same "EFI variables are not supported on this system" error appears.

So, I got it working, one line in the manual saying set speed is 201h (513d). Totally missed it. And the pyvcp value had to have a F after the label


[TRANSACTION_02]
FIRST_ELEMENT=513
NELEMENTS=1
MB_TX_CODE=fnct_06_write_single_register
MB_RESPONSE_TIMEOUT_MS=500
MB_BYTE_TIMEOUT_MS=500
HAL_TX_NAME=spindle-set-speed
MAX_UPDATE_RATE=0.0
DEBUG=1


## connect the PyVCP run speed slider to mb2hal input pin
net spindle-set-speed mb2hal.spindle-set-speed.01.float <= pyvcp.spindle-set-speed-F

Hello everybody. I don´t know much about electronic systems so I am looking for some guidance. Me and some friends are converting a Sherline benchtop lathe to CNC. We plan to use a RPi with a CNC breakout board. So far we have been able to control the steppers but not the spindle. Originally, the spindle is controlled manually by a KBIC-240D DC motor speed controller. This board controls the spindle by means of a manual potentiometer and a lever switch. We are replacing the manual potentiometer with a digital one, especifically a MCP4131. However, this
potentiometer is controlled only by SPI communication protocol and as I understand it the default HAL file only sends PWM signal through the designated pin. 

How can I configure the HAL file so that the RPi can establish SPI communication with the potentiometer?

transactions 00 and 01 load and work fine. if you use nelements, pin names are not required. And no, spindle-set-speed is not being created. 00 is spindle-speed and 01 is spindle-at-speed. These are being created, and work fine via axis

Hi All, 

Ive done a search and found a couple threads on this but it honestly goes over my head a little. Has anyone made a complete press brake control with GUI interface from LinuxCNC? Im currently looking at building a DIY press brake to suit my needs and would ideally like to have some control over it. Even a basic NC control that can save programs as I do repeat parts would be great. I know almost nothing when it comes to software and have been attempting to have AI write it for me (which is probably not going to work). I come from a mechanic/fabrication background so building the press for me is the easy part and the software part is where I will seriously struggle. Was hoping someone would have something that might suit? 
Currently on the fence between a torsion bar style press with a single Y1 on a glass scale or if it can be done I would rather run Y1, Y2 and a pair of scales to control it independantly. X axis backstop would also be needed. Other axis controls would be nice but really not needed for my application. Ideally tooling library, bend tables etc would be great to have stored inside software but is that  LinuxCNC thing or something seperate i need to make?
The threads ive seen on here seem to taper off with no conclusive result on them. If anyone has any input would be very much appreciated as I am a complete newbie to this type of thing. 

Thanks
Brad

Fr3nzy wrote:

My motherboard is very old and doesn't support UEFI. Maybe I should use one that will support it.

You have the right to have a computer museum, but do not require anyone to help you maintain it.

Thanks! I knew it was some dumb mistake on my part

The "EFI variables are not supported on this system" has nothing to do with BIOS setup.
This is common kernels RT problem (efivars disabled in config).
The solution is to add "efi=runtime" to the kernel parameters (once at boot or to /etc/default/grub).