Advanced Search

Good point.. I've set all of the axes to 9.5 but it didn't resolve my issue.

 

You should not need series resistors.
Just make sure that the ground return
of the switches goes only to the 7I96S
ground.

sorry for this silly questions.
in the comp it is written as 'stat_switched_on' but in hal it becomes 'stat-switched-on'.
I did not know this yet. the same with spaces:
net z-brake cia402.0.stat-switched-on =>lcec.0.4.dout-2 #lcnc freaks out because there is not space after '=>'

Tomorrow i will try to connect the brake to the driver instead of LCNC. as i will get following error when the brake is a bit late. I could maybe fix this with comps however i think the driver should handle this.

Also i need to find a way to reset this driver error through lcnc when it happens.
I hope i will be able to show you a video next week of the ethercat bridgeport

Is it  possible you have lost the link? (maybe 7I96S 5V power issue)

What does:

sudo chrt 99 ping -i .001 -q -c 10000 10.10.10.10

report?

(will run 10 seconds and report ping statistics)

Thank you for the quick reply. I will try to figure out how to flash the modified firmware.

As for the wiring (first question): do i need any resistors to limit the current or can i pull the pins directly to ground (common)?

Try running this script to see if it helps:

 

first chmod +x pinirq.txt

then

 sudo ./pinirq.txt enp0s25

(from wherever you browser downloads stuff, probably ~/Downloads)

(this is temporary and will get reset by rebooting)


The best current PC I have for network latency is a HP 8300 USDT
(AMT needs to be turned off in the BIOS) It will run for weeks at a 3 KHz
servo thread rate while doing normal PC web/compiling/etc stuff

Might be a stab in the dark, but i would change the 5V and 24V power supplies first.

I would use 7i96sd_mpgp1.bin firmware as that was designed for this use.
You can use a software MPG encoder but since the inputs are sampled
at the (relatively slow) servo thread rate it will not work very well.

Take a look at this thread:

forum.linuxcnc.org/39-pncconf/51733-7i96...-configurator#295487



 

My problem just got worse. Now the error has returned even while using "sudo ethtool -C enp0s25 rx-usecs 0". Its just like before popping up every 5-10 minutes and stopping my cut in the middle of the process forcing me to recover the cuts and it is very difficult. Any ideas of what can be causing this error? and also can you guys maybe recommend working pc models so I could maybe swap the computer for one that works how it is supposed to.

Hi everyone,

This is my first post in this forum, so first of all i want to say that i am really impressed by this community. You have been a great help in my cnc building journey. So Thanks you 

I upgraded my controller setup from an old PC with parallel port interface to a Mesa 7i96s card connected to a newer PC. Now i am working on my pendant/mpg and have modified it to be directly plugged into the P1 expansion port. 

Since i am new to the mesa hardware i want to make sure that my setup does not have a fatal flaw. I basically have two questions

1- my pendant has 6 push buttons and two rotary switches (for axis and jog speed selection). Each button is wired this way, for example Pin 3 and Button 3:

Pin3 (P1) -> button 3 -> ground. 

So the pin gets pulled to ground when the button is pushed (active low). I read it should be done this way since the P1 pins have pullup resistors and are always high when the board is powered up. Is this wiring ok? Do i need extra resistors to limit the current? Many buttons can be pushed at the same time.

2- concerning the mpg/rotary encoder. i have read several posts talking about custom bit files to add encoder "functions" to some pins. Is this step really needed? My former setup had the a and b channels of the encoder connected to normal pins, the signal management was done in the hal. I want to avoid flashing new bitfiles if possible at this stage because i am still not very comportable with this new (to me) hardware.

Thanks !!

Yes, the maximum steprate for Mesa FPGA cards is only dependent
on the hardware. It is independent of the host controller.

This is because the steprate is set by a digital oscillator.

The host does determine the update rate of the steprate,
so even though you could have a 10 MHz steprate at a 1 Hz
update rate it would not work at any reasonable acceleration rate.
 

At first glance:

Change  step times from 500 to 4000

The charge pump needs to be done with stepgen 4
(the software charge pump will not work)

Recent versions of pncconf know how to setup a stepgen as a charge pump
 

I'm not aware of an XML import.
It is possible to use an external database for tool management:
linuxcnc.org/docs/devel/html/tooldatabase/tooldatabase.html

As an alternative it might be possible to convert the xml tool data to ordinary list data used in linuxcnc (eg by a custom python script):
linuxcnc.org/docs/devel/html/gcode/tool-....html#sec:tool-table

Homing defines your absolute zero position (ie G53), whenever you actually cut a part you will be using a work coordinate system (ie G54 ... G59) that is set to a corner of your machine vise or the part to be machined.

Okay, thats why they were opposite, homing vs traveling direction, as I believe, I guess I'm missing some very basic concepts here.

I`m trying to understand how my machine should be set for home.
The travels are X 1000 mm, Y 450 mm and Z 400 mm.

How should I set the homing to be as trivial and safe as possible?
I thought as my first post:
I'm setting my home positions and to order to:
1st: Z all the way down, nearest to the floor at value 0.0
2nd: X all the way to the left, nearest the lathe at value 0.0
3rd: Y all the way back, nearest to the wall at value 0.0

Should I set 0 values for all axes? This would make my machine runs on negative coordinates all the time, right? What would be typical for a machine like this?

I really appreciate your help, guys.