Advanced Search

O M G. Wait, are you showing us that all what's missing to RIO to be fully functional is a fpga dev board and the toolchain installed? As in "screw Gowin IDE'??? If that's the case then that's a pretty serious game changer.

I have so much to learn about your solution, obviously. Excitement is getting outta control!!

it does deserve a reply.

Ok, I'll give it the benefit of the doubt.

So to start with some basics:
- your 'hal.ini' is not an '.ini' format but a '.hal' format.
- your 'config' would be called a 'hal component'

Whether PP is going to be fast enough will mostly depend on what kind of use you have in mind for the DAC.

Now before you make a PCB you may want to try and get that hal component of yours compiled and installed (prepend 'sudo' if you are on a package install):
halcompile --install <path/your_component.comp>

Once that hurdle is overcome you can then create a simulation config to test your custom component and your .hal file.
You can use the 'halscope' tool to check the output of your custom component:
linuxcnc.org/docs/devel/html/hal/tutoria...ec:tutorial-halscope

To get an idea of how a custom component file is structured see the components included in the source code:
github.com/LinuxCNC/linuxcnc/tree/master/src/hal/components

[edit]
Please keep in mind that presenting a ChatGPT spit out on a technical forum like this will most likely make you look like somebody who doesn't want to spend any time learning the basics. I know it may look like a good start to somebody who has no clue but to people who know just a little bit more it just simply looks like a serious lack of effort.

Just an example from a normal servo config, where x-pos-fb is just an arbitrary name and is wired to 3 other pins, or all 3 pins are wired together to the bus bar, and the bus bar is named x-pos-fb

Not sure I understand the question right but you can connect multiple hal inputs to the same signal:

net signal <= hal.pin-out => hal.pin-in1 => hal.pin-in2 ...

 I have been reading through the Manual looking for a way to turn one signal into multiple signals.
I know it's possible in Classic Ladder, but is it possible to do it in HAL? Like AND 2 but in reverse.
(1in 2out)? Basically I want to make a signal splitter.

Sorry to bother but is there an ETA on the 2.9.3? 
and will the game pad key mapping be included? ex: github.com/AntiMicroX/antimicrox?tab=readme-ov-file

Oh how cool is that. Yeah definitely wire them into the three surplus encoder inputs on the 7i97.

Would be very cool if you could connect that Heidenhain control panel into LinuxCNC as well. Do you have info about it? Is it a matrix keyboard?

A stuck output means a damaged driver chip.

Driver chips can be damaged by:

1. Excessive supply voltage (can the field voltage surge above 32V?)

2. Inductive loads > ~60 ma if they do no have a flyback diode
(flyback diodes are recommended in all cases)

The chip can be replaced by returning the 7I77 to Mesa

That looks like IRQ coalescing is not disabled.
You should get ping times about 1/2 your current values.
(the first ping can be ignored because it includes a ARP request)

what does

ip a

report?
 

Personally, i do not mind such questions at all, the OP has given us some info to chew on, so no matter what question, it does deserve a reply.
-
To answer the question from the tittle:
Yes, parallel port is fast enough for a lot of things/machines/whatever as long as you consider the requirements in regards to port limitations.
I have Plasma, Mill, engravers, Styrofoam cutters, all using parallel port for over 10 years without a single issue, ever.
And at one point in time i used a parallel port with LinuxCNC and the included scope as an Oscilloscope/Logic Analyzer, just mind the 5V input limit.

I'm sorry, I was a bit bored

 

riocore/configs/MecanixDev/config-test.json
riocore/boards/MecanixDev/board.json

Is the writing on that machine in Slovenian language?

Looks like you successfully loaded the config....
Where did you get that config file? It is for a different board.

Load the one from the repository the firmware was in, and in the future, dont use anything outside of this repo
github.com/scottalford75/Remora-RT1052-cpp/tree/main/LinuxCNC


You may have to do a full chip erase to remove the wrong one. I think there are some instructions on how to do a full chip erase somewhere in the thread.

So, if I got that right, It is not intended but with some coding and abstraction it could be done...

If a station only needs a single axis (eg a Z axis) then there might be a way to use the 'extra joints' feature, which are axes that are not linked to any of the nine possible axis letters (XYZABCUVW) but are managed independently by 'limit3' hal components. As soon as you need two axes to move in a coordinated manner you need to do this through the motion planner (ie GCODE). A single LinuxCNC installation can only run one coordinated motion at the same time. So for example on a lathe with two independent tool posts it is not possible to have one tool post follow a contour and the other tool post follow another contour at the same time. It would be possible to run one after the other has finished but that is usually not idea.

Multi-channel capability comes up sporadically in discussions, mostly in the context of lathes with front and back spindles. Looks like there have been tentative attempts here and there but whether that it will actually ever work is really anybody's guess.
Personally I certainly wouldn't count on it.

A comment from a hobby non-trades user that finds 'stacking' or 'queuing' of MDI commands useful.

The hobby aspect often is a one-off with testing of individual cutting paths.
A few sequential paths might then give the result.
Then, copy/pastes within the MDI history allow the job to continue, and complete.

Sort of half-way between manual and cnc.

I am currently assessing what I should do on discovery that my new upgrade to LC2.9.2 on a Raspberry Pi 4B with AXIS does not allow MDI command stacking.
Gmoccapy is on the review list.

John.