Advanced Search

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.

blazini36 wrote:

Kind of a bummer about the bold text thing
 

What bold text thing?

JT

Hi All,

I realise this is a very old thread - but I have a maho 400p too that is dead, as well and am looking to update the control (mine was a  Heidenhain TNC 135).  I don't hold much hope in getting the EPROM programs even if I did find a new heidenhain controller, so was thinking of a very similar approach to you stormpetrel.

I have no experience in CNC  refitting whatsoever but I hope to dust off some experience in PID controllers and power electronics from a very very long time ago, so I think I can manage the learning curve and I plan to take a lot of time to work out what to do with my machine.

I don't want to convert to three axis cnc or to replace trapezoidal with ballscrews, I want to get the machine back to a manual mill with a 'smart DRO', intact EMO chain and hydraulic functions etc, and hopefully keep the point -to point control function as it used to have, so I am thinking of one axis cnc and selecting each axis at atime in code.

So, to my question :  (I hope someone reads this given the original thread was 15 years ago!)
- the 5i20 and DAC approach was the way you suggested PCW back in 2010,  but given the time elapsed between now and then, what would you recommend now?
-stormpetrel, how did your project go, did you find it worked out, and where would you do things differently?
- as a starting point, and to see the complexity of all this would it be possible for you to send me  the design that you settled on back then?

I'm new to this forum and it was not apparent how private messages are sent. if this post doesn't find any replies I might repost it as a separate thread with reference to this one.

Thanks in advance,

Pat

fully_defined wrote:

The maximum acceleration I calculated as 49800 mm/sec^2 is WORLDS away from the default 750, and pncconf doesn't allow more than 10000.

Unless that is a very small 3D printer, 49800 mm/sec^2 is way, way, way to high.

Sometime this happens if your gcode is written to use absolute IJK coordinates on arcs but you are using relative coordinates or vice versa.

Looking good!

JT

Allan, I have not quite got to 6.12 on my installer but I did  merge ther upstream to my master branch to get 6.12 support
github.com/rodw-au/rpi-img-builder-lcnc
This runs on a normal PC and cross compiles.
The main branch did compile 6.12
It would need cloning my 2.9.3 branch to a new branch and merging the master branch into it
Then a bit of massaging to remove the existing RT patch and configuring a few config files in the top level folder.

I remember seeing someone here saying you needed to set a few more config settings that used to be set in the patch. They also included a script to set it up. Perhaps that is your issue.

Lol yeah, I noticed them in the docs and started adding them before updating the debs.....

Kinda tedious but it's getting there...

 

Kind of a bummer about the bold text thing

That is a valid error. Why you are getting it is impossible to say without at least seeing the gcode program.

blazini36 wrote:

I also noticed there's no good binary indicators in qt5's standard set of widgets, like LEDs or even a button that changes appearance on input. The only thing I've found is hal labels, but even then I think they are only actually good for displaying numeric values. If set to "bit" type input, they just display true or false. I don't see any way to make a text string appear or disappear at least. Looking for something that can just indicate a fault.

If something like this is already there just point it out, I'm good at missing things.
 

You didn't miss anything unless you looked in the last few minutes lol. I just added that feature.

gnipsel.com/linuxcnc/flexgui/hal.html#bool-label

 

JT