Advanced Search

Are you sure it is not stalling because your accel/velocity values are too high?

if the distance moved with a 100 mm command is not inversely proportional
to the scale, the hardware is not following the  command.

500 mm/s is way faster than is possible.

Even at 300 steps per mm, 500 mm/s  needs a 150 KHz step rate, but your base thread
period limits you to only about 5KHz (5 KHz = about 16.6 mm/sec at 300 steps/mm)

I am trying to create a simple subroutine to surface a block before engraving. It originally complained about an EOF in the file so I decided to execute each move command individually using MDI to make sure the code was correct.

Here the snippet that is giving an error:

    G0 X2.144 Y-0.125   (Move to start)
    G0 Z-0.02           (Lower spindle)

    G91             (Relative Moves)
    G0 X-11.163     (Make cut)
    G90             (Absolute Moves)
    G0 Y1.6921      (Move Y for next cut)

    G91             (Relative Moves)
   -- -> G0 X11.163      (Make cut) <---
    G90             (Absolute Moves)
    G0 Y3.5092      (Move Y for next cut)
    G0 Z0.1         (Move to safe height)

At the line indicated --->  <--- LCNC reports an error to the effect that Linear Move will exceed limits of the machine.  The program zero is located at the right-front corner of the block. Since I could move to the starting location in line 1 and do the first cut to "G0 X-11.163" which is negative, I naively expected moving opposite direction the same distance would be acceptable.

The block, 3.25 x 7.00 in., is located in the center of the 19 x 11 in. table with ample space on all sides for the 2 in. surfacing mill to clear the block. Fortunately, this was my first attempt to use LCNC on this machine so I was cutting air for the test, so no material was damaged.

Can someone help explain the error and how to resolve it?

Kind Regards,

The GMOCCAPY documentation indicates that the arrow-keys, pg-up, pg-down are enabled by default, however, they are not responding on my installation from the main screen. I've looked for a configuration parameter to enable them, but the only key I found disables all hot keys, not just the jog keys. Am I doing something wrong or did I miss something in the documentation?

Hi I has problem with my setup  ini file  I do not understand the behavior of this if I use 200 step for the scale in my z axle and then G0Z-100 and the movment stop at 40 mm 
step 300 = 60 mm
step 400 =  81mm
step 500 = 78 mm
step 600 = 59 mm
Why can´'t I hit 100 mm in my set up I tryed many diferent value of steps with 50 increasment  
computer = Raspberry Pi 5 ,breakoutboard db25 cinese make , stepperdriver DM542  , 1/4 800 steps , motors 200 steps
are there any kind to help me in the right direction
yours sinserly Krister



   

I am looking for someone who would help me with my LinuxCnc project. We use laser welding to weld electric motor shaft before grinding. I am at the end but some small issues I can't resolve. If there is someone who can spare some time and help( I am willing to pay) would be much appriciated.

Boris

1 Yes
2 Yes
3 Yes
4 Yes, if you do not use any encoders
5 Yes

Hi all,Thanks in advance to everyone who responds!I’m using the following HostMot2 bitfile for my Mesa 7i92:

BoardName : MESA7I92
FPGA Size: 9 KGates
FPGA Pins: 144
Number of IO Ports: 2
Width of one I/O port: 17
Clock Low frequency: 100.0000 MHz
Clock High frequency: 200.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256

Modules in configuration:

Module: DPLL
There are 1 of DPLL in configuration
Version: 0
Registers: 7
BaseAddress: 7000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: IOPort
There are 2 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: QCount
There are 6 of QCount in configuration
Version: 2
Registers: 5
BaseAddress: 3000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: StepGen
There are 5 of StepGen in configuration
Version: 2
Registers: 10
BaseAddress: 2000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: PWM
There are 1 of PWM in configuration
Version: 0
Registers: 5
BaseAddress: 4100
ClockFrequency: 200.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P2
Pin#  I/O   Pri. func    Sec. func       Chan      Pin func        Pin Dir

 1      0   IOPort       PWM              0        PWM             (Out)
14      1   IOPort       None           
 2      2   IOPort       StepGen          0        Step/Table1     (Out)
15      3   IOPort       None           
 3      4   IOPort       StepGen          0        Dir/Table2      (Out)
16      5   IOPort       StepGen          4        Step/Table1     (Out)
 4      6   IOPort       StepGen          1        Step/Table1     (Out)
17      7   IOPort       StepGen          4        Dir/Table2      (Out)
 5      8   IOPort       StepGen          1        Dir/Table2      (Out)
 6      9   IOPort       StepGen          2        Step/Table1     (Out)
 7     10   IOPort       StepGen          2        Dir/Table2      (Out)
 8     11   IOPort       StepGen          3        Step/Table1     (Out)
 9     12   IOPort       StepGen          3        Dir/Table2      (Out)
10     13   IOPort       None           
11     14   IOPort       QCount           0        Quad-A          (In)
12     15   IOPort       QCount           0        Quad-B          (In)
13     16   IOPort       QCount           0        Quad-IDX        (In)

IO Connections for P1
Pin#  I/O   Pri. func    Sec. func       Chan      Pin func        Pin Dir

 1     17   IOPort       QCount           1        Quad-A          (In)
14     18   IOPort       QCount           1        Quad-B          (In)
 2     19   IOPort       QCount           1        Quad-IDX        (In)
15     20   IOPort       QCount           2        Quad-A          (In)
 3     21   IOPort       QCount           2        Quad-B          (In)
16     22   IOPort       QCount           2        Quad-IDX        (In)
 4     23   IOPort       QCount           3        Quad-A          (In)
17     24   IOPort       QCount           3        Quad-B          (In)
 5     25   IOPort       QCount           3        Quad-IDX        (In)
 6     26   IOPort       QCount           4        Quad-A          (In)
 7     27   IOPort       QCount           4        Quad-B          (In)
 8     28   IOPort       QCount           4        Quad-IDX        (In)
 9     29   IOPort       QCount           5        Quad-A          (In)
10     30   IOPort       QCount           5        Quad-B          (In)
11     31   IOPort       QCount           5        Quad-IDX        (In)
12     32   IOPort       None           
13     33   IOPort       None         

   

1. I only need 4 axes (X, Y1, Y2, Z). Can I use the last StepGen for torch on and laser pointer outputs?
2. I do not need encoders. Can I use the QCount pins as general-purpose inputs?
3. Can I use the pins labeled “None” or “unassigned” in the bitfile as inputs or outputs, depending on their pin direction?For example, pins 10 and 15 as inputs, and pin 14 as output?
4. Are pins 13 and 15 on P2 free to use as I/O?
5. My breakout board has 5 inputs labeled P10, P11, P12, P13, and P15. Can I use all of them as inputs

thanks again to everyone who helps!Best regards,
 

yes, I just needed to make sure

Info : By measuring I found that between the encoder inputs A-A/,B-B/,Z-Z/ there is a resistance of 120 Ohm, they are already integrated in the MESA card. So additional resistors are not needed. I did not find information about this in the manual

I need to work more organized!! 

Thank you for all the help you gave me!!! I am going out to configure the VFD so I can finish the machine, I am under a lot of pressure!! Thank you!!!!!

 EDIT: 
tested functionality: step-dir servo X,Y,Z
step-dir spindle
MPG


untested:
probe
limit switch
linear ruler and encoder spindle

it is possible to configure all these functions on the 7i95T board using PNCCONFG  in LinuxCNC 2.10 (with the need for simple manual editing of the HAL file for MPG -axes switch)


not yet tested - I'm worried that I connected it wrong - it's my first experience with MESA
I'd be happy for any comments
 

I'm not sure if I should ground the shielding of the servo motor data cables to the MESA board - the drivers are already grounded via the ground wire from the ~ 230 V power supply and a ground loop is created, which could cause EMC interference
 


more details on my channel :
www.youtube.com/channel/UC_zOVvs96VKX6R_DIO5KyJg






 

 

 

Initially I was considering using a RPi5, but my intention is for LCNC to be networked and not host the UI, instead I would use the second nic to recieve individual commands or whole files if/when needed.

There are hats, but it seems it is likely easier to get a PC, there have been some topics but it has been some time since then, does anyone have recommendations for the smallest formfactor solution with dual NIC? Ideally we would be priced similar to RPi, but I would be happy <€300.

(I know it was a few years ago but in the Marco reps video it seemed that he had a ncie solution, but I couldn't find details on his).