Advanced Search

In BIOS:
disable "secure boot"
enable CSM
try switching from Legacy to UEFI and vice versa.

Are you using VPN?
Try disabling it.
-
Forbidden errors are always from trying to access restricted parts of the web server, so something is wrong on users side.

I downloaded the 2.9.8 latest version from the first link in the download page
Burned this iso to a pen drive under windows using Rufus latest version
Live preview works fine
Graphic install consistently fails at the point of installing GRUB
         - this happened on numerous older PC typically inter dual core with 4GB to 8GB of RAM and installing to an SSD
As a trial I installed 2.7.4 which I had on a pen drive without issue

It should be noted the 2.9.8 installed perfectly onto a much newer NUC PC using the same pen drive

I have installed 2.9.7 without any issues and will (Debian 13) and will look to update to 2.9.8 tomorrow when time allows

Please advise if any more info is required
Regards,  Paul

Hello, with the update and after doing a sudo install mesaflash the board is found and its working...
Also mesaflash is now reporting 3.5.16...

So I guess I was too sloppy with my version I build and what I was actually using...

Sorry for bothering you with these basics... and thanks for the responsive help.
Saved me from swapping EEproms...


sudo mesaflash --device 7I90HD --addr 0x378 --epp --verbose

EPP device 7I90HD at 0x0378:0x0778
Communication:
  controlled by FPGA
Board info:
  Flash size: 16Mb (id: 0x14)
  Connectors count: 3
  Pins per connector: 24
  Connectors names: P1 P2 P3
  FPGA type: 6slx9tqg144
  Number of leds: 2

 

Mesa configurations do not use pin numbers but channel numbers for things like stepgens and pwmgens
As long as you have the correct firmware, the order of these channels typically matches the breakout

For GPIO, GPIO numbers are used (the connector pin == GPIO mapping is in the readhmid printout)

RotarySMP wrote:

Good weather for welding Nice progress.

Not on this side of the world where the the temp is hitting 40 deg c and beyond! We holidayed in Canada over Xmas so went from -20c to plus 40c which took a week to get back accustomed to!

The original component by dbraun was designed with home to index in mind but today many drives home to an external switch. The problem is that the drive moves while not being commanded  by linuxcnc which linuxcnc interprets as a following errors. The secret is to sync linuxcnc's commanded position and its feedback while its moving like this which the original cia402.comp does not do. some people have modified the component to support this.  I have been working on an enhanced cia402 component but it needs more work.

Thanks. I'll see if I can get that to work. I keep thinking it's time to put together a new computer and move up to 2.9 but when it's working it's working.

(Slowly gathering parts for a cnc router running 2.9.x so maybe it's time to get them both at the same "level"

Thanks again
M

No,
4x FN 2090-4-06

I have loops set to 10 and timeout to 3.

/homeI am not a dense person. I have read A LOT on configuring. I have set up a couple other machines with StepConf. 
Why does this:

look absolutely nothing like this:

when trying to configure this: 

I want to install Probe_Basic. I already had Trixie installed but i couldn't get Probe_Basic to work. Than i got the hint from a community member that Probe_Basic needs Debian Bookworm as the homepage mentions.

Phone - 401 Unauthorized

Try from a phone or tablet, or another PC.

Hi everyone,

I’ve just released version 1.1.0 of the io_decoder driver. This update focuses on architectural stability and addressing initial feedback from the community.

What's new in v1.1.0:

Asynchronous Threading: I have moved the keyboard emulation logic (uinput) out of the Real-Time HAL thread and into a dedicated user-space thread. This ensures that any system-level delay in processing keystrokes will never interfere with the real-time performance of the CNC HAL components.

Config File Optimization (Credits to COFHAL): Following COFHAL's feedback regarding parsing errors with comments and blank lines, I have refined the io_decoder-keymap.cfg structure. I've implemented a stricter formatting requirement to keep the driver lightweight and added clear instructions within the config file to prevent GUI warnings.

Full English Translation: The source code and all comments have been fully translated to English for better accessibility.

Clean Exit: Improved the cleanup routine to ensure proper thread termination and resource release upon hal_exit.

You can find the updated source code, documentation, and the new pre-packaged ZIP on GitHub and the project landing page:

GitHub Repository: github.com/bobwolfrst/io_decoder-linuxCNC Project Page & Downloads: bobwolfrst.github.io/io_decoder-linuxCNC/

A big thanks to COFHAL for the valuable feedback. I’m looking forward to hearing from more testers about how the new threading model performs on different hardware setups!

Happy milling!