Advanced Search

Idont know if I mentioned the exact thing is happening on X andY but not Z and they have the same Servo's, encoders and drives. Plus the encoders are sealed in a casing inside the servo motor cap.
 

Peter's link also shows how to enable  by editing a text file. Note this file may be in a different folder.

Doesnt really loose position. I dont know to what accuracy but If It doesnt seem to do it when I put a battery on the drive velocity input. IT works fine until I get f-error. I jacked up the ferror in the ini so I can see it move through the transition.

It asumes you have the mesa bit file installed that ends in *pl.bit
This gives you 3 x encoder A's on the A,B and IDX terminals
The example assumes you will use encoder 1 which should be the ENC B terminals
Install the bit file, then review the pins in halshow to get the right pin names for your 7i96s

ok, Im guessing i will need to modify these files to reflect the 7i96s?

Also do these files specify where on the encoder the wires will be? I just glanced over them real quick.

I thought I noticed for the 7i96s the THCAD should go into a speciffic location? Believe it was the diagram for the Low Rider 3.

It would be best to follow up with Sheetcam as its really out of scope of linuxcnc.
It does give you the line number the error is on so I would have a look there.

pncconf does not support ohmic sensing with a thcad.
I have attached a later component and a stand alone hal file to set it up
You can add the hal file into your ini file
You will need to install the component with
sudo halcompile --install ohmic3.comp

You can use some generic USB pendants

Its also possible to use a generic parallel
pendent connected to P1:

forum.linuxcnc.org/39-pncconf/51733-7i96...etup-in-configurator


 

I currently use Onshape. I really like it! I hope to use the CAM studio when it is officially released. I only have a free account so I'm afraid the CAM portion will not be available to me just as simulation is not. I currently use the Kiri:Moto "plug-in" which seems to work pretty well. I'm brand new to CNC so, for now, it gives me everything I need....tool paths for basic parts for me to learn with. 

Mike

Thanx for answer! I am changing control system in my selective soldering machine Inertec ELS 3.0 Machine is not bad, but original control system is horrible, LinuxCNC and Mesa will move the machine to 21.century
Well, it doesn't matter where pktuart will be, but I think, 7i96s local port will be better.

I will definitely move away from that idea.
You are saying the 7i84 and 7i73 mesa cards are common for expanding on the serial port; is it so that there are not just "generic" bob's to be had all around, line there are for bob's for parallell ports? The reason I'm asking is that purchasing more boards from Mesa is so expensive with shipping and import duties etc. into Norway.

tic106 is more sensitive so maybe this is the reason for burning fuses because conducts more easily and shorts fuses.

Something odd popped up today, tried to create a new G-code for 2 small parts.  And I got an error from SheetCam when using the LinuxCNC plasmaC post processor, see attached screen shot.  I used it yesterday without a problem but today no go.  If I switch to LinuxCNC THC it will create a g-code fine.  From what I have been told when using QTPlasmaC you need to use PlasmaC.  I have reached out to SheetCam, no rely yet.
I am using version 7.1.35 development TNG,  I did try a install but nothing changed, it acted like they are using cloud storage as the reinstall is a direct copy of what was on my disc.  It pulled in the same .JOB file and error even after uninstalling SheetCam from my PC ????
Do not understand the "Operational round tool" comment in the error message, clearly a Plasma tool.
 
 

That may be quite a project, but I can add a PKTUart
to either the last channel of the 7I74 or the local port
on the 7I96S

During motion you would get a following error if the encoder stops counting
since at some point the commanded position would differ enough from the
feedback position to cause a following error.

If stopped, a bad encoder can cause a runaway. One way to address this
failure mode is to

1. Have some integral term so a small error will eventually saturate the system

2. check either pid.N.saturated (a bit) or pid.N.saturated-s (a float) to
check if the PID loop is saturated. A possible refinement here is to set
the PID maxoutput to a function of the commanded velocity.

2A. The previous check does require the error build up to full output before
the error is detected so a faster response would be to check pid.n.errorI
(by comparing it to a limit) Normally you would not expect the integral error to
build up to a large value if encoder feedback is working (note you need to
have "debug=1" on the PID loadrt line ti make the errorI parameters appear)