Advanced Search

Here are the pktuart.0 and mb25ioc32.so files that work on my system:

 

Replacing your files (one at a time) may help debug this issue.

forum.linuxcnc.org/10-advanced-configura...to-example-mesa-7i77

Just needs appropriate configuration (hal and ini) files for each machine

Yes.

That was it! I tried 8" for max travel instead of my 16" and it probed down......I should have done that last night, but it was time to stop for the evening. So, I added 60 thousandths to my previous measurement, as you mentioned, and it measured and inputed the tool length.

Thanks for the link....that is what I was already following, along with the directions on the various PB screens.

I also saw info on the various offsets in your directions, so that should answer one of my previous questions in this thread. I'll make my way through all the directions on your page and I need to check out your videos to see what else I can learn.

Hi Friends, 

The goal is a tangential knife setup with a pizza type cutter blade. To achieve this i have a servo driving a pulley that drives an output shaft with the  blade on it. my goal right now is to get it to jog without errors. 

In Axis, when i jog the A axis its slow and jittery. I increased the speed to about 500 deg/min and it moves faster but just as jittery. Anything over 600 i get a following error, I also get random following errors throughout normal jogging. I checked all the connections and they seem fine. Which leaves makes me think it might be the servo tuning. 

I tried to follow this guide to tune it (gnipsel.com/linuxcnc-old/tuning/servo.html) however, i cannot find the signal in hal scope. The tutorial calls out 'axis.x.f-error' i can only find 'joint.x.f-error' and get no change when i trigger it with a movement. what is the difference between these two and am I on the right track?

Any advice is greatly appreciated. 






 

LinuxCNC will only come out of eStop when the SPI comms works, ie the remora-spi component receives a valid response from the board.

This is where using the serial output from the board is handy to ensure the board boots all the way to idle state where it will wait for SPI commands.

OK  thinking about this, it's probably just a difference between a RIP installation and
a binary installation, where the normal user does not have write access to LinuxCNC's
system files.

Still does not explain the issue, and why it works as expected using  2.9.4 built from source.
Maybe a problem with the binary image.

 

I changed the permissions of the modules directory. Now only a 'touch' error. Doesn't say me something...

corne@linuxcnc:~/CNC/Mesa/mod$ modcompile mb25ioc32.mod
/tmp/tmp40_g_2ol/mesa_modbus.c
touch: cannot touch 'mesa_modbus.c': Permission denied
Compiling realtime mesa_modbus.c
Linking mb25ioc32.so
cp mb25ioc32.so /usr/lib/linuxcnc/modules/

yeah so before I tried also to get CubeProgrammer to reinstall the bootloader but it failed, and now wonderfully it succeeded.
also:
firmware.bin => firmware.cur
my further drilling the setup led to understanding that the estop is tied to:

net user-enable-out <= iocontrol.0.user-enable-out => remora.SPI-enable
net user-request-enable <= iocontrol.0.user-request-enable => remora.SPI-reset
net remora-status <= remora.SPI-status => iocontrol.0.emc-enable-in

I do not fully understand, but remora.spi-enable is TRUE, status is FALSE and reset = FALSE, they are connected to a signal which is probably a physical signal on the octopus, but I dont know where. I accidentally made a short by connecting 3.3v to GND on DIAG0....

Anyway getting closer

p.s. I believe nothing was damaged!

With a fress install (from image) - without sudo i get this;

corne@linuxcnc:~/CNC/Mesa/mod$ modcompile mb25ioc32.mod
/tmp/tmpqf_2s56r/mesa_modbus.c
touch: cannot touch 'mesa_modbus.c': Permission denied
Compiling realtime mesa_modbus.c
Linking mb25ioc32.so
cp mb25ioc32.so /usr/lib/linuxcnc/modules/
cp: cannot create regular file '/usr/lib/linuxcnc/modules/mb25ioc32.so': Permission denied
make: *** [/usr/share/linuxcnc/Makefile.modinc:107: install] Error 1

I will try to do this: "Unless you have setup sshd to listen on port 5007 that is the the expected behavior."

it should be:

modcompile xxxx.mod

not

sudo modcompile xxxx.mod

at least that's what I have always done

 

sudo modcompile works, but again the same error.

Thanks you both. Yes I know that the security of the WAN is the most important security thing I must take care, but SSH, will at least secure part of the system. But anyway it is a very good advise. Thanks a lot.