Advanced Search

sadly so yes, although i cannot help but think there must be a simpler way to do this with mux, just somehow switch between position and velocity modes depending on an input

its fairly complex...

You might take a look at this, using the orient component.

forum.linuxcnc.org/10-advanced-configura...is-from-inside-gcode


 

I'll have this information for you tomorrow.

Thanks for the help.

if you can run

and attach the lspci.txt file (photos are difficult to work with if you want a proper answer) and I can give some answers.

Just gone 3pm here in Sydney.

No something interesting.

I worked on a little project using an FPGA dev board to run MESA's hostmot2 firmware. First attempt was based on the 7c81 using either SPI (raspberry pi) or EPP (best on motherboard based parallel ports). The issue with the board I used is that the EEPROM need to be changed and the headers were already soldered on.
That same hardware can also be used with the LinuxcncRIO project.

Another project I had a go at was modding the 7i90 Smart serial firmware to support 4 encoders to run on a dev board.

For my latest I've grabbed a different dev board (eeprom is correct size & bought with the headers unslodered, but this time I'll be trying a Ethernet interface, chip is same as use on the Mesa products, so no having to rewrite a driver, which requires a couple of steps, first being working out the instructions of the softcore, working how the driver talks to the chip and then how it integrates with the rest.

Some pics, 2x17 ports from breakout boards (mesa 25 pin daughter boards can be used as well) and 4 extra pins for 2 smart serial ports or extra I\O.

First off is the FPGA from aliexpress:
 

The Ethernet board, this is experiment only, the FPGA board sits on top, disregard the type of 2x25 headers they can be changed to suit. Should have the boards in a couple of weeks.
 

One of the daughter boards from the orignal project.
 

My worry was that I was missing something that led other (more knowledgeable people) to mark this chipset as not working with LinuxCNC, but as you said if it works, it works.

Hopefully this post helps someone in my same situation in the future.

Thanks a lot for your answer.

forum.linuxcnc.org/10-advanced-configura...to-example-mesa-7i77
The same procedure and tuning is valid for 7i97T.
Especially mind the wiring of e-stop and drive enable, those can not be skipped.
-
First you have to get the drives running correctly, with no Mesa and no LinuxCNC. This i can not help with, the rest is quite easy, just follow the above and post here whenever you bump into something strange.

At a guess
4PM in Australia
12AM or 1AM in Brazil
?
6AM here...

OK.

The Linux Kernel loads drivers based on the PCI ID, there's nothing special about it. If it sees a particular PCI ID it loads the driver that matches.
So the reason lInux will load the parport_serial is because that's what the card is reporting.

For Tommy, I replied with what might be the issue directly under your post. But without the PCI ID, end manufactures can change this usually via an eeprom or maybe some other method, there's not enough info to go on.

Hello, I would like to see if anyone can help me with the Linux CNC configuration of a 7i97t Mesa board and a 7i75 board with Chinese T3D servo drivers. I would like to recruit an advisor who could help me and teach me with the configuration. Payment method to be agreed upon.

If it works, do not change it.
Any card has a chance of randomly stopping working, things break/die/release the magic smoke, etc, but that is not a reason for changing a perfectly working card.

hmm, interesting finding.

Why does it use parport_serial if it is only a single parallel port with no serial ports? Or it has nothing to do?

What do you suggest as next step? Update linuxcnc to 2.9 or just the kernel?

(By the way, I am not an Aussie, I am Brazilian... Just 180 degrees apart xD)

unknown wrote:

Just as I thought it's a kernel version thing.
PCI ID 1fd4-1999 is only supported from 5.4 up

forum.linuxcnc.org/10-advanced-configura...uing?start=30#324501

Thanks for your reply.
Can you explain in more detail, as I understand I should:
1. Creating an O-code for a subroutine that contains these 3 commands
2. Remap a new G-code that will call the O-code above
Is this what you mean or is there a more straightforward way?

Just as I thought it's a kernel version thing.
PCI ID 1fd4-1999 is only supported from 5.4 up
The driver is acually parport_serial.
Good info here, linux-hardware.org/?id=pci:1fd4-1999-1fd4-0100

That's why the PCI ID the most important bit of info.

You an Aussie as well ?