Advanced Search

If I remember it correctly that component doesn't work, you might want to try:
github.com/scottalford75/Remora/tree/mai...omponents/Remora-eth
and change in your hal settings to "loadrt remora-eth-3.0"

This should be close:

 

 

How close are the schematics to the CNC Bridgeport lathe posted up top?

thank you very much, I did it, I inserted this config as well as halcompile with remora-nv.c, now there are no problems with starting, however, as before, it issues a latency error, and after a very small jog, it loses communication with the network and the only thing possible is to turn it off and turn the power supply on again and that's how it gets the network. The conclusion is that it's very unstable, so I'll try to do the same with my version1 nvem card that I have from before and compare the error, if it's still the same, it's probably the problem is in linux itself. mesa 7i96s works on it without error.

Indeed Twopass was on. I switched it off. This lead to the following behavior:

The machine started classic Ladder. CL worked as intended. The Axis Gui of the CNC did not load. When I closed CL, the axis gui loaded. I thought I could go into the Ladder Editor and simply start it again, but once I was in ladder editor, the Modbus Maser pages in the config where not there. Like it was just loading a blank program.

I have not tried to put the CL part in the postgui hal file. Will try that.

Hello. Just tried to update to this version from older linux mint - i am not able to set up isolcpus. Tried editing grub file in etc/default, creating new file in grub.d - still no luck. And run update-grub of course. How to add it and test before reboot ?

Or this one is wrong version for parport ?

Having hope here ,
+ fun refreshing my linuxcnc 2.9 pre stable test a few years ago.
Using roya rt preempt kernel on orange pi 5 on trixie .
Thanks all for linuxcnc ,+++.

I'm probably the single user of the puppy linux/rtpreempt userspace + the 7years old DebianDog-Jwm-3.4-9-rtai ....
and still using them..

I call it combo , it's the pdf name , look like it's a PC-2-Route All In One Model M2 OEM

PCW wrote:

Thats a fairly odd pinout.
I can try making a matching bitfile some time this week
That was the usual Soundlogic pinout, M2 & Combo , for most of them .
Odd but they were well build bob .
 I plan to reuse a combo + an encoder from the same guy, + 7i92h , 
a bit file would sure help...
or i 'll use 5Abobx2.bit and , hmmm , and swap cables , because , you do got all my respect , you FPGA and ARM coders, 
or C coders ,python , well , all of you , i bow  to you.
  Could it help other having those olds bob , pdf for them here;
encoder

combo

Hello, I have been doing some research and I want to understand better the difference on these systems, for instance these setups in the videos use Raspberry pi 4 and Ethercat so he can directly talk to the servos and no mesa card is needed, I understand Ethercat makes wiring much more simple and the cabinet has less parts,also on some servos is possible to do homing directly, some cons seem that is  harder to implement because there is less info out there and hardware is possibly more expensive usually, but my question is to know if it is as powerful as a mesa card setup on the max step rate side of things? any other toughts I may be missing?

 


Thanks!
 

i do not understand what is a reset mode. and where to call it/place it and in which file.

Now it's time for the portal beam. I milled seats for the rails (the profile itself was bent by about 0.2mm) and drilled all the holes. 



I also decided to fill this profile with polymer granite.
Remembering not very successful variant with tabs in the base this time I decided to try a different way. I cut all the threads directly into the profile and then screwed the screws in. Then I poured the polymer granite and after a few hours, when the mixture began to harden, I carefully unscrewed it all. It was much quicker and easier than with tabs.

There will be a motor on one side, so the fill will not be full volume. I also decided to put the wires from the motor through the profile, so I used a cardboard tube for this. On one side it is held by an aluminum plate. When pouring the polymer granite to have support inside, I made a piece of thin MDF.

 
 
 

I would guess so, (dangerous half knowledge)

If you use y code instead of a, you can move

G01 x right_end y distance_1st F what_works
G01 x 0 y distance_1st_layer + distance_2nd F what_works
G01 x right_end y distance_1st + distance_2nd + distance_3rd F what_works
etc.

The y distance per layer will become shorter and shorter, as the motor needs to do less revolutions when the spool gets bigger, at the same time the x feed will become faster.

Hope that helps.

p.s. the described way should result in a constant material speed.

On the other hand when you keep the material under tension and move in a Thread-pitch fashion (lathe in threading mode) it should work just as fine. The pitch will be one material diameter per revolution and the material speed will increase when the spool becomes larger.
The speed increase can be counteracted by slowing the spindle speed down.
 

Updated the system today, including ProbeBasic from version 0.5.4 to version 0.6. The error is still there, but the error message is different.
Is the lathe version tested by anyone before release? If so, on what configuration?

is it doable with G-code though?