Advanced Search

I can guarantee it's not bricked. I loaded the raspberry Pi OS onto it after that with no problem and was able to access it via SSH to download data from the Pi library. I tried 2.93 as well and got a similar result only this time there were some penguins at the top of the screen instead of skulls  

Just updated the bootloader and tried again. Got a similar result but now the ACT LED is flashing consistently instead of barely visible. 

I'm surprised nobody else is experiencing this. Am I the only 8G user to try these? Do I need to have some additional board attached for it to boot properly?

[Edit, after hearing it might be bricked, I tried the same card on a 4gig Pi4B that I've been using perfectly fine for years with the same result] 

It's often best to de-couple the linear axis when doing initial tests
so no harm is done with a runaway. (there's about a 50% chance of getting
the feedback reversed = runaway at first startup.

It's also important to have the drive enables working so a following
error will disable the drives.

rodw wrote:

Assuming you are using the linuxcnc rpi 4 image, on the command line, try typing menu-config and selecting the correct locale for your part of the world

once I learned how to set the local correctly it worked.  lol 

 

Got LinuxCNC installed along with MESA CT. Took me a bit to figure out the mesaflash version situation. Everything is talking now, so yay.

I am a bit leery of energizing the drives as analog control is a bit more unforgiving than step/dir.

Is there any reason why I should not set my analog limits far below ±10VDC? I was thinking as low as ±2VDC to start. Definitely going to just try X first as it has the most travel.

This is all a bit dangerous if the servo motors are still connected to the linear
axis.

That said, if the joint and axis maximum velocities are increased slowly
there will be point where the following error increases rapidly (because
the actual position can no longer track the commanded position)

This is one way to determine the maximum speed (at 10V)

Watching the following error/velocity/PID output with halscope will help to find this point
 

It would be interesting to see the latency values after switching to X. This can be done via the config utility for the Rpi, the actual binary name escapes me ATM.

Where in the gui shows axis rapid linear speed?
I see only position in GUI DRO.
I want to measure this without uncoupling
motor from ballscrew.
I have set correct encoder scale also i know
that linear rapid speed is about 5000mm/min
but am not sure how much is exactly.
If i set man speed to 10000mm/min
this will enforce 7i33 to outout 10V.
So in this case how can i measure actual
linear speed without decoupling servomotor from ballscrew?

Some things look odd with your gcode file:

The first N12760 should be commented out.
The second N12760 should have a J value of -89.450, not -89.500
N12770 should not be commented out.
The second N12800 should have a J value of 89.450, not -89.400

This comment at the top ";File converted successfully;" hints that a conversion was done somewhere, I don't think that it was successful.

This gcode loads:

 

Thanks for the heads up regarding wayland and axis.

If you're using a Rasp OS image you'll want to swap from wayland to X if you are looking to run axis, the "compatibility layer" is "not quite optimum".

Hi.
In linuxcnc we have g10 l2 px rx and rotation plane xy around z on px origin selected.

For plane g18 not have implementation for linuxcnc ?

Thanks

Kernel built whilst using Rod's imager, running over a ssh session.

Thank you for your response, but I forgot to include it in the .ngc file - I have tested it before and it does not help in my case.

You are welcomed, always.

gene_weber wrote:

I will probably create a separate thread about jitter optimization.

This is badly needed based on the reported latency which is unusable