Advanced Search

What is "buildroot" ?
-
If you mean building from sources (on github) :
linuxcnc.org/docs/html/code/building-linuxcnc.html

If you mean buildbot:
buildbot.linuxcnc.org/

Cncninja wrote:

Has anyone worked with them on this? 
 

Not that i am aware of, nor has it been mentioned here on the forum.
But i do not think i am ordering any, no ethernet.
also, i avoid using "all in one" for production machines as much as humanly possible, but i do use their boards on 3D printers.

Hi Scott,First, I want to thank you for your incredible work on the Remora firmware!Two weeks ago, I received my NVEM V5 board and started working on flashing it. Unfortunately, I couldn't find my STLink dongle (seems like I lost it), and I couldn't wait for a replacement. So, I decided to get creative and used what I had available. I flashed an STM32F103C8T6 using a Raspberry Pi Zero W with the "CMSIS-DAP" firmware you mentioned in one of your YouTube videos, using OpenOCD.As you described in the video, I then uploaded the "stm32f103xb_mimxrt1060_qspi_if.bin" to the mass storage device of the STM32F103C8T6, and it seemed to program itself as expected. I then connected it to my NVEM V5 board and dropped the firmware file onto it, but unfortunately, it didn't work.I spent the next three days troubleshooting but eventually gave up and purchased an STM32-Link, along with two CMSIS-DAP Probes (USB-A and USB-C). I received both of these items recently and tried again, but I’m still having issues.The CMSIS-DAP probes aren’t detected at all, neither by MCUxpresso IDE nor PyOCD. The STM32-Link is recognized by PyOCD, but I still can't get it to work as intended.Do you have any suggestions on where I should focus my efforts next? Any guidance would be greatly appreciated.Thanks again for all your help!

Have not seen you on youtube lately, but i fear that is the dreaded "algorithm", glad you are OK and still kicking.

Looks like a hardware error.

Do you have a motherboard parallel port or is it a a plug-in card?
 

i will try to maintain a changelog in the future

github.com/multigcs/riocore/blob/dev/CHANGELOG.md

Nevermind

I'll test this later this afternoon.

Thank you so kindly for assisting.

Hello,I can no longer launch Qtplasma, I have the following error message, thank you in advance for your help

I am running into similar problem but maybe I found root cause. Need to do some more testing but please check below and share the result.

Can you please do the following:

• M6 overwrite routine macro - On the tool change remove all the G43 command except one at the end after tool measurement., in my case it was m6 g43 on semi manual change
• start linuxcnc
• go to tool table and set in column Z =0 for probe and two random tools which you later test on example T1 and T2.
• load probe m6 t99
• go to object and measure it.
• change to t1: m6 t1 with tool measurement
• check if offset is correct if so try another tool t2
• if T2 is ok now check other tools (one which has Z <>0 value in the tool table)

I have rack change for tools 1-5 and rest I am changing manually in the position. And I notice that the tools changed manually i was lading with M6 G43 in the tool_change macro. This causes error as I was changing G54 Z offset after loading tool. I need to make more test .

cheers
Michal

I assume that this procedure does not work when starting with a clean version of LMDE6? I tried on several systems, but I get long lists with missing python modules and the grub menu does not work.

Regards, Rob

Hi fully_defined,In reviewing your drawing, we have a few suggestions and clarifications:

• For the HLFB output: As long as the circuit has sufficient voltage (24VDC will work) and current, HLFB can be daisy chained as shown in our photo below. You’ll need to configure each motor to use the HLFB mode “Servo On”. In this configuration, if any individual motor has its HLFB go low, the “fault input” at the controller would also go low.
• For the Enable input: All of the motors can be enabled together as shown. Note that with this configuration, you won’t be able to individually enable or disable any of the axes.
• For ground lines: As it’s not stated in the schematic, note that you’d want to run all of the ground lines back to the controller and connect them together at the controller (you wouldn’t connect the grounds together at the motors or elsewhere in the cable run).

- Aaron B. Teknic Servo Systems Engineer