Advanced Search

Hi andy

Yes i change the stuff from rev-dc 100 to -100... it works.
Still struggle with issues. Possible i can get help from u?
Today i look to the 3 signals from the proximity sensors.. found out that there are some spikes.. but the spikes are only a noise on the signal.. not in the area that they toggle the gpio.

I think my ngc is the issue.
Later i add some debug lines to see where it stops working.

I am xonfused about the strobe pin.. and dont understand the usage.

I use sense0 as index for homing and sense1 for the slot sensor on the slottee disc.
Some time ago you wrote i must use the strobe for the slot disc. But dont understand it correct. Can you please explain a little more please?

Thanks

Hi all,

I decided to build my ideal plasma cutter CAM program over the summer after being dissatisfied with our options for generating QtPlasmaC gcode. 
I've got it to the point where it is useful, so I'm opening it up for previews. 

Please have a look at metalheadcam.alan-gibson.workers.dev. Give it a try and post bug reports and feature requests in this thread.

The basic workflow is:
- Click the hamburger menu and then Tools so you can add your tool parameters
- Import a DXF file on the Import stage
- Skip the Edit stage for now as it doesn't do much yet
- Click the Apply All button on the Prepare stage
- Add operations to parts and shape chains on the Program stage
- Simulate the program on the Simulate stage or just skip it
- Download gcode on the Export stage

Thanks and I look forward to your feedback.
 

LinuxCNC 2.10 can do tandem axis, i do not know if 2.9.4 can.
You need this for the axis with 2 motors, and this way you can change direction of those motors separately, and this does require home switches for each joint that you already have, so all good.

Thanks MaHa,

The bracket syntax worked great, however, I'm still not able to access the INI vars after adding the INI_VARS = 1 to the ini file. Is there another setting that I'm missing?

Here i am again.. this shows us the original circuit of the original controller . the proximity sensor switching gnd. Its a npn normaly open proximity sensor without shielded cables.
Sensor is powered with 24v.

my now setup is:

the output cable from the sensor goes direct to my mesa 7i92t. i see the gpio toggles if i bring the sensor to some metal. it works. the mesa 7i92t is jumpered to pullup.


if i use this circuit i must set the jumper to pulldown. correct?
 

thanks for your help

incase others find this..
there was an error in my probe_panel.xml file as i added an aditional tab. once removed. the error was gone

Hi all. I am installing Easyprobe today on my CNCLinux instalation. 

can someone help explain what this error is telling me and how i can fix it? 

 

I'm controlling them with external offsets. Would that be the reason?

I make a drawing in few hours.
Its 5v i measured but later with the drawing it would be better to understand

I've replaced the standard kinematic file with your modified version, added extra joints and changed the config to inches to test in the simulation but I cannot reproduce your jogging issue in TWP mode.
I'm afraid I'm a bit at a loss as to how to troubleshoot this further.

Cheers Andy,

I'll get hold of 2.9.5 and try it out on the sim!

J'ai installé les interrupteurs de fin de course, un pour chaque moteur.
Je veux synchroniser les moteurs de manière logicielle pour qu'ils puissent se calibrer séparément et se déplacer de manière synchrone.

L'inversion des câbles est une bonne solution, mais cette machine appartient à mon employeur qui préfère ne pas toucher au matériel (et garder la compatibilité avec l'autre pc avec Mach3)

Dois-je modifier les fichiers .hal et .ini ou est-ce possible avec StepConf ?

---

I've installed limit switches, one for each motor.
I want to synchronize the motors in software so they can calibrate separately and move synchronously.

Reversing the cables is a good solution, but this machine belongs to my employer, who prefers not to touch the hardware (and maintain compatibility with the other PC with Mach3).

Do I need to modify the .hal and .ini files, or is this possible with StepConf?

Hello Aciera, regarding your “patch,” I would like to know if it is functional? Have you had any feedback? It is indeed a matter of correcting the defect concerning the tapping after the execution of the caxis component.

Ok- so the first thing you suggest to try would be single ended.  Is just setting the jumper DOWN really all I need to do in this case and the axis should (ideally) behave like before? Or will there be more to it?
Well, I will simply try to jumper it to TTL and see if I can run the axis single ended properly or not.

Years ago I remember such "differential converters" on Uhu´s (DC-drives) - these where small and pretty inexpensive parts. But I just knew them for converting A+B channels to A/A* and B/B* , did not need the index in this times....
If I could use such converters to get a differential Index signal out of a single one and so solve the issue I would be fine with it.
Unfortunately I can not simply exchange the encoders as these Fanuc encoders seem to be part of the servo motor and the rear end bearing of the motor.

So I will first try to run the axis with the 7i33 jumpered to TTL, see how it behaves with the single A/B signals and if I can use the index signal then.

Thank you
Sigi

 

Maybe we can combine them?