Advanced Search

Did a little tweaking on the themes




JT

 Hello everyone. This is my first time posting here.
 I have a question about M6 Remap and Carousel on Lathe. System work Ok. In .ini file i have REMAP= M6  modalgroup=6  prolog=change_prolog ngc=toolchange epilog=change_epilog.
  If i want add ignore m6 (Remap=M6 python=ignore M6), i get an error that it Remap=M6 is already in use.
  If I want Remap=T (REMAP=T python=index_lathe_tool_with_wear), I have error "M6: no tool prepared" (message from stdglue.py file)
I can use these functions if the tool change is work on the ladder. But the carousel is a more convenient tool.
 Maybe someone knows how this works?

Using Fusion to generate the g code. LinuxCNC post processor.

1. yes, older Mesa cards
2. No
3. 7i96S does not need flashing, except when other non standard features are required, and does not need to load firmware from HDD, it has it's own memory for it, twice i think as there is a fallback in case of mishaps on almost all new-ish Mesa boards.
4. and 5. i am not sure, so i'll shut up!

Left everything on overnight and came back to it this morning. Thought maybe I did a pause rather than stop so fiddled a bit with the step, run, and stop buttons thinking stop might clear out things when pause would not. Not sure exactly what happened but it now doesn't give the error. Would be good to know why it happened and what to do to avoid the error or reset things if it happens again.

Hi,
i have answered your email. Checked both things listed above and had no success flashing new firmware

You can also try your luck with the somewhat dated 'bridgemill'
configs/sim/axis/vismach/5axis/bridgemill

Have a look at
configs/sim/axis/vismach/5axis/table-rotary_spindle-rotary-nutating

Set the nutation angle to 90° and ignore the table rotary.

 

Hello,
How should I add RTCP feature to a 5-axis machine with the same joints as the machine in the video?

Apparently you can buy Raspberry Pi 5 kits that don't offer access to the SD card...

I'm aiming to build from released sources and load it up.

%lost interest: If you think I should switch to another thread for questions please just let me know where/how.

Thanks,
Tom

anyone was find solution?

Building and flashing the firmware

You don't have to solder in the H-Bridge or any other connectors (expect the Power connectors P3 and P6) to flash the firmware.

Install prerequisites (I used a minimal debain install, so you might have some of them already installed):
Clone the github repository (I used the repo from freak, since it has the latest updates, even though they link to rene's repo in their documentation):
Build the firmware:
Flash the HV controller: Connect a USB cable to the USB port on the HV side (this is the only time you should connect a USB cable to the HV side). Short the Boot jumper near the STM32F3 with a small screwdriver and provide 24V DC to P6. The controller should show up in lsusb:If the controller does not show up, make sure you have contact with the boot jumper. Also try to flip the USB cable.
Flash the firmware with
Flash the LV controller: Repeat the steps above on the LV side (connect USB cable, short boot pins on LV side near the STM32F4, provide 24V DC to P3, check for the controller using lsusb)
Flash the firmware with
The LV controller should reconnect and show up as

Hi all,
Just one question: On buildbot2.highlab the bookworm/master-uspace/binary-amd64 has not been updated since 2024 October 24th.
The source is now version 2.10.0-pre0-3979-gbc86e90f8b from  January 7th. 2025
LinuxCNC can so not more be updated via synaptic or apt install.
Is there a chance that the binary-amd64 will be updated soon ?
Thanks a lot for help
Regards
PW  

Update 2025.01.09:
This morning the binary-amd64 was updated. Thanks a lot to all contributors.
PW

 

Google search led me to this "Driver Boards" section of the forum, I had no idea it existed I was posting related question under General etc, apologies for my past transgressions.

My understanding is that some Mesa boards load their FPGA firmware every time they power up and others are non-volatile.So I guess:
1) If you have the former, you can just provide a different file in the correct location and change the boards functionality?
2) if you have the latter you need to re-flash the FPGA?
3) I'm using a 7196S for my lathe (WIP), so is the 7i96S volatile or non-volatile?
4) I have a quadrature encoding glass scale on my Z-axis connected to isolated inputs 0&1 (TB3-1&2), and this works fine unless I move quickly, apparently the inm's (I'm assuming this means input mux) scan rate can be increased. Not sure where the scan rate is changed, is that a HAL type parameter or do I need to reprogram the FPGA?  And how do I increase the scan rate?
5) If after maximizing the mux scan rate I find it's still too slow for fast moves and I instead connect the scales to the P1 expansion port, do I need to re-flash the FPGA, or is it already configured for quadrature encoder inputs? In total I will need to connect two scales and one MPG. Not counting the spindle encoder connections to TB2. Where do I find documentation on the expansion port and mapping of quadrature inputs to those P1 pins?

your help is much appreciated.

 

Godt the first pack of IO Boards today and waiting for the rest plus the controller.