Advanced Search

my journey with linuxcnc started here with the first cnc mill i retrofitted

forum.linuxcnc.org/show-your-stuff/39021...d-thread-nz?start=50

this machine has been going well and doing lots of work since then

hey guys just thought i would try give back to the linuxcnc community a bit and hopefully document my machine shop and machines that run linuxcnc

i have 4 working machines currently running linuxcnc and am retrofitting my latest cnc mill currently

this is a mazak fh6800 horizontal cnc mill with a pallet changer and a 5th axis on top of the built in 4th axis

pretty cool machine and weighs 22 tons.

i am using dimitry's sscnet card to control the servos and just a few mesa cards for all the rest of the IO

i will add a bunch of photos in the next post

tommylight wrote:

VNC should not be included with official releases, it is a huge security risk.

It won't be 

What version are you using?

I try to build linuxcnc master (2.10 pre0)
and build goes to infinite loop with these messages repeated continuously

I have a Mesa 7c81 card that would like to use in the servo mode. I have not been able to get the LinuxCNC Pncconf to complete its configuration to complete. It gets stuck with a python error. I edited the python code to fix some of the errors. I would also prefer to use the raspberry 5 and the 7c81 needs the spi to use the 7c81. For some reason the pi 5 only uses 1 screen. If it’s helpful I have time to test running your updates to provide feedback if you don’t have a full HW test bed to help test the code fixes.

Whilst I agree with tommy in theory, it can depend on the implementation. Turn wifi off on the Rpi and have a direct direction from one machine (that doesn't have another ethernet deivce connected to an outisde network) and it will be fine.

So far I haven't seen any reports of a Linuxcnc installation being hacked via VNC, nor via ssh.

And honestly a RPi in a commercial setting is just bad, due to it not being certified for industrial use.

If a user wants it and is ready to accept the risks it can be installed after installation, forcing upon users who don't want it or an unaware that it is there is not the right decision.

VNC should not be included with official releases, it is a huge security risk.

I  only had a few minutes to contort myself into position to take a few pics of this CNC mill.
If the wiring diagram is a match it appears to use 10V analog control for the DC brushed servo motor drives.
Can anyone confirm from the pics attached before I have a chance to go back with a scope and move a machine out of the way to investigate the control cabinet innards further.

I've migrated the Remora for RP2040 to now use the Remora-eth-3.0 component. 

Download the latest firmware

github.com/scottalford75/Remora-RP2040-W5500/tree/main/firmware

Upload the remora-rp2040-2.0.0.uf2 file to your pico.

To configure the linuxcnc hal module and configs use the files here:

Hal Files (run halcompile on these)
github.com/scottalford75/Remora-RT1052-c...omponents/Remora-eth

and the configs:
github.com/scottalford75/Remora-RP2040-W...onfigs/remora-rp2040

The rcpwmgen should be much easier to setup
as it does not require adding external components
to set the offset. It addition it has higher resolution
 

 I reverted back to using PWMgen vs RCpwmgem, I just found more examples to reference.In my rservo_2.hal I commented the last line out as it kept posting an error.I'm close but I think I missing HAL pin assignments in the Main.HAL for the BOB PWM channel.  Or is it more than that?As always any guidance is appreciated. 

Ok, some more investigation. Using the publish uf2 file and your config I confirm the issue. I've recompiled my master branch which had some unpublished clean-ups (debug info) from the ping-pong buffer implementation, and your config happily loads and runs.

I've also added a firmware folder to the repo to make finding the uf2 file easier.

github.com/scottalford75/Remora-RP2040-W...ora-rp2040-1.0.1.uf2

I'm working on making the RP2040 version compatible with the latest LinuxCNC Remora ethernet component, but currently this version still uses the legacy remora-nv component.

PCW wrote:

1. step_length+step_space = step_period
Maximum frequency = 1/ step_period
(so 500 KHz for 1000 ns step_length+1000 ns step_space)

2. They suggest 50% duty cycle. With the mesa hardware this would be true
only at the highest step rate, though this is probably not important.

3. Looks correct

4. Max linear velocity is after all reductions and ballscrew conversion to linear motion.

5. The shortest step_length on a 7I95T is 10 ns but you are limited to 1000 ns minimum by the drives
Note that it is better to leave some margin and not use the minimums.

6. If the speed was limited by the step timings, yes, 250 mm/S would be your maximum linear velocity.
at those microstep settings.
Practically, the maximum velocity will be much lower, as it will be limited by the step motors maximum
RPM which will be closer to 1500 RPM (= 50 mm/S) than the 7500 RPM that 250 mm/S requires.
This should allow you to increase the step_length and step_space to say 2000 ns so you have plenty of margin.

7. Really depends on the motor shaft/ballscrew/axis mass. A good guess to start is 5x the linear velocity.
If that is 50 mm/S, an accel of 250 mm/S^2 would be a good start. Too high will cause stalls, too low
will limit speed on curves.

 

Thank you for the help PCW  

That's already there, but you'll need to write the image to your nvme drive.
Disable EEE on boot, will need to be setup as a service, I'll see if I can find the info I found the other day. I'll also check if the driver has a switch to do that as well.
I'm beginning to think the RPi5 is a bit of a lemon for Linuxcnc is some cases.
Honestly at its price point a mini x86 system is a better choice.
The basic Odroid H4 runs in at $99 USD, a little bigger front print.
The only advantage the RPi4 had over an x86 system in terms of use was the ability to use the SPI interface. With the RPi5 that's not an option. And using the GPIOs is more or less on par with using a Parallel port.
In saying that I'll still try and assist rod as much as possible .