Advanced Search

hi there,

I think you have to check if drivers is running at FHPP or Cia402 protocol shape .. It is configurable and it should be hidden pain...

then you have to setup the SDOs and then PDOs  for Cia402 

If you are familiar with twincat 3 I can recommend it for you to jog motor from scratch... if it will jog over them just swap yout master to lcec

regards 

 

ok, i used your file, added your tools to the tool library, ran PB, homed, loaded your file, moved to a spot and set G54 using G10 L2 P1 X Y Z, then did the same for G55 and G56 and no error here,, im not near my machine with the actual probe to set things that way so can you test by the method above and see if you get the same backplot error that way? if not i will have to test next im at the shop near the machine.

Is QEI working ?
I have a RPI 4 SPI connected to a BLACK_407VE and an encoder with index connected to PE9, PE11, PE13. All works well except QEI, remora.PV.2 never changes, always = 0. Am I missing something ?
config txt :
    {
    "Thread": "Servo",
    "Type": "QEI",
            "Comment":                      "Spindle encoder",
            "PV":                        2,
            "Data Bit":                     7,
            "Enable Index":                 "True"
    }
Debug output:
Servo thread object                                                             
Spindle encoder                                                                 
Creating QEI, hardware quadrature encoder interface                             
  Encoder has index                                                             
                                                                                
Creating a std module                                                           
  Initialising hardware QEI module     

im not probing but i can set 54 55 56 work offsets with mdi in the same command in the probe routine and am getting no error in the develop version, let me go back through your post and read the triggering description again to see if i missed something.

did you try fixing the missing parenthesis and retesting?

In the upper bar where the dimensions are, set it to whatever you are using, mm or inch, before working on the drawing.
You can open a new empty file, set the mm or inch, and save that as a template, so you open that file first then paste whatever you are working on.
Reminds me of another tip you wont find on the net, when opening any other file type, like PDF, CDR, DXF, HPGL etc, always, always select the drawing with select all (CTRL+A) and open a new Inkscape (CTRL+N) then paste on the new instance with (CTRL+V).
Most of those file types do not contain dimensional info, so makes a mess when exporting them to gcode, the above will save you a lot of headache.

Ethercat explanation.
www.ethercat.org/default.htm

Obviously parameters will be machine\ethercat hardware dependant. The question is quite expansive.

There is quite a good thread getting into setting Ethercat on Linuxcnc.

Good luck with your assignment.

BipinBabu wrote:

Is there any readymade package with LinuxOS+RTKernel+Ethercat Master prebuilt.?
 

No, but the LinuxCNC ISO should already have everything needed for installing EtherCAT, see on of the pinned topic on this section.
EtherCAT can not be distributed in any ISO due to licensing issues, as far as i know.

I have to ask one last question. I have been working with Inkscape to develop g codes from and svg drawing. Works great and would like to use for this however I can't get the g code size to match the size in the page. I have looked all over and don't seem to get a clear answer that really works. About ready to give this up, shouldn't be this hard. Must be missing something.
Any comments greatly appreciated.

So I did have that pulled up at one point. If I remember correctly it would turn on when I hit the home button but then would stay on until after it estopped and I relatched the machine it would turn off

To check homing to index, you need to halscope the index-enable signal.
The actual index signal is often too short for halscope to see.

LinuxCNC sets index-enable once is has detected the limit switch and the hardware
clears index-enable when the index is detected.

thanks

langdons wrote:

What exactly is BuildBot?

It is a PC/server that checks and builds the debs for various version of Linux architectures, after getting stuff from github, as far as i can gather.

We should say this more often:
Awesome work and a magnificent machine.

But there is a link to 2.9.5 on the downloads page!
linuxcnc.org/downloads/