Advanced Search

Search Results (Searched for: )

  • programador
  • programador's Avatar
15 Jan 2025 12:29 - 15 Jan 2025 12:30
Replied by programador on topic home axis problem

home axis problem

Category: AXIS

Good morning, to no home index, try this code in the INI file, but be careful, there may be severe collisions if you exceed the machine limits.
HOME_USE_INDEX = NO
  • hellvetica
  • hellvetica
15 Jan 2025 12:23

Using G64 with M66 for smooth robot control

Category: General LinuxCNC Questions

Hi, I've been using linuxcnc to control my delta robot arm through HAL pins and M66 commands.
This is my GCODE
(AXIS,stop)

O500 WHILE [1]

( Main loop )
M66 E0 L0 ; Read from motion.analog-in-0 (X)
#1 = #5399 ; Store the read value in variable #1
M66 E1 L0 ; Read from motion.analog-in-1 (Y)
#2 = #5399 ; Store the read value in variable #2
M66 E2 L0 ; Read from motion.analog-in-2 (Z)
#3 = #5399 ; Store the read value in variable #3

G1 X#1 Y#2 Z#3 F1000 ; Move to the new position


; G4 P0.1 ; Wait a short time before the next read (optional)

O500 ENDWHILE
M30

I connect custom pins to the motion analog in pins and then set the xyz values in my python or c program.
This works great, but when I try to add G64 blending to make the robot keep its speed it doesn't work.
Obviously this is because the trajectory planner doesn't know the next target point until it's read by M66 in the next gcode loop, so I tried adding the next target point into the gcode as well with 6 analog inputs:
(AXIS,stop)
G64 P50
O500 WHILE [1]

; G4 P0.001 ; Wait a short time before the next read (optional)

( Main loop )
M66 E0 L0 ; Read from motion.analog-in-0 (X)
#1 = #5399 ; Store the read value in variable #1
M66 E1 L0 ; Read from motion.analog-in-1 (Y)
#2 = #5399 ; Store the read value in variable #2
M66 E2 L0 ; Read from motion.analog-in-2 (Z)
#3 = #5399 ; Store the read value in variable #3

M66 E3 L0 ; Read from motion.analog-in-3 (X)
#4 = #5399 ; Store the read value in variable #4
M66 E4 L0 ; Read from motion.analog-in-4 (Y)
#5 = #5399 ; Store the read value in variable #5
M66 E5 L0 ; Read from motion.analog-in-5 (Z)
#6 = #5399 ; Store the read value in variable #6

G1 X#1 Y#2 Z#3 F30000 ; Move to the new position

G1 X#4 Y#5 Z#6 F30000 ; Load next position


O500 ENDWHILE
M30

This only works for every other point, because when the gcode loops, the trajectory planner has no information about the next point.

What I would need is to load the next target point into the trajectory planner so that G64 can use it, but not go there with G1. I tried adding O500 continue between the G1s but then the gcode is smart and ignores the second G1.

Is there a way to do this?


 
  • programador
  • programador's Avatar
15 Jan 2025 12:18
Replied by programador on topic LinuxCNC with OKUMA OSP MX-55VA

LinuxCNC with OKUMA OSP MX-55VA

Category: Basic Configuration

Good morning, my friend. Unfortunately, there won't be a ready-made cake recipe. Each machine requires a different methodology. I would start by studying the electrical part of the machine, to find out how many inputs and outputs it has, then how many movements it has, and finally which devices will be used. With this, you can get an idea of ​​which electronic boards from the manufacturer Mesa  store.mesanet.com/ will be necessary for the Retrofit. If you post the electrical part on this forum, we can help you.
  • timo
  • timo
15 Jan 2025 11:13 - 15 Jan 2025 11:18

Can the stepgen LPT work in conjunction with the mesa card?

Category: General LinuxCNC Questions

It is a PCIe Mesa 6i25 with 7i76 plug and go kit. I do not know when I updated Linux CNC last time on that device. Must be a two or three year old installation.

I do not think it will make a difference, besides the naming conventions in the hal files.

How I did it:
a) create a Machine configuration with stepconf
b) create similar Machine configuration with pncconf

Then I deleted the axis information from the pnconf generated file, for the motors that will run on the parallel port. I deleted all the axis information from the stepconf gnerated file, that will belong to the Mesa card.

Then I merged the two configs step by step by copying the "Mesa stuff" into the LPT configuration. (ended up with a convoluted hal and ini file that works and contains snippets of "both worlds")

Greetings Timo

p.s. I did not have mentionable prior experience, so it took a while to get it "free of startup errors", but no involved adjustments. Mainly removing double entries and correcting my own typos.
  • tivoi
  • tivoi's Avatar
15 Jan 2025 10:58
  • nicton
  • nicton
15 Jan 2025 09:04

Can the stepgen LPT work in conjunction with the mesa card?

Category: General LinuxCNC Questions

Files

File Attachment:

File Name: mesa122.hal
File Size:12 KB

File Attachment:

File Name: mesa122.ini
File Size:5 KB

File Attachment:

File Name: mesa122.hal
File Size:12 KB

File Attachment:

File Name: mesa122.ini
File Size:5 KB
  • Aciera
  • Aciera's Avatar
15 Jan 2025 08:27
Replied by Aciera on topic LCNC 2.10 - Ask for AUTOMATIC_G43

LCNC 2.10 - Ask for AUTOMATIC_G43

Category: Gmoccapy

code snippets:

gmoccapy.py:
        if self.prefs.getpref("show_startup_messsage", True, bool):
            title = "Important change for version 2.10"
            message = "Gmoccapy does no longer automatically retain G43 after a toolchange!"
            sub_message = "Automatic reactivation of G43 is possible using a REMAP.\nAn example can be found in any Gmoccapy SIM configuration."
            cb_value = self.dialogs.show_startup_message(self, _(message), _(sub_message), _(title))
            if cb_value:
                self.prefs.putpref("show_startup_messsage", False, bool)

dialogs.py:
    def show_startup_message(self, caller, message, sub_message, title = _("Operator Message")):
        dialog = Gtk.MessageDialog(caller.widgets.window1,
                                   Gtk.DialogFlags.DESTROY_WITH_PARENT,
                                   Gtk.MessageType.WARNING,
                                   Gtk.ButtonsType.NONE)
        dialog.set_title(str(title))
        dialog.set_markup("<span size='12000'><b>" + message + "</b></span>")
        dialog.format_secondary_text(sub_message)
        ok_button = Gtk.Button.new_with_mnemonic(_("_Ok"))
        ok_button.set_size_request(-1, 56)
        ok_button.connect("clicked",lambda w:dialog.response(Gtk.ResponseType.OK))
        box = Gtk.HButtonBox()
        box.add(ok_button)
        cb = Gtk.CheckButton(label = "Don't show this again")
        box.pack_start(cb, True, True, 0)
        dialog.action_area.add(box)
        dialog.set_border_width(5)
        dialog.show_all()
        self.emit("play_sound", "alert")
        response = dialog.run()
        dialog.destroy()
        return cb.get_active()
  • Aciera
  • Aciera's Avatar
15 Jan 2025 08:17 - 15 Jan 2025 08:22
Replied by Aciera on topic LCNC 2.10 - Ask for AUTOMATIC_G43

LCNC 2.10 - Ask for AUTOMATIC_G43

Category: Gmoccapy

Turned out to be not too difficult, adds an entry 'show_startup_message' in the .pref file:  
 
  • besriworld
  • besriworld
15 Jan 2025 08:01
Replied by besriworld on topic Gmoccapy 3.5.0 - opinions needed

Gmoccapy 3.5.0 - opinions needed

Category: Gmoccapy

Yes, this is a useful feature, thanks!
  • marcom528
  • marcom528
15 Jan 2025 07:50

7i95t firmware brick because i flashed a 7i95 bitfile in the fallback

Category: Driver Boards

thanks for the fast response PCW!

for my understanding!?
1)flashing the firmware to the fpga using the infinty software and the ftdi4232 jtag interface.
am i flashing to the fpga ram (Volatile Memory)? after power loss, the firmware is gone right?

2)write the firmware to the fallback and the eeprom (is it a part of the fpga? or is it an external eeprom on the 7i95t?)

mesaflash --device 7I95T --fallback --write FPGAFILE.BIN
mesaflash --device 7I95T --write FPGAFILE.BIN

after writing the .bin file it should be permanently saved to the storage and the 7i95t should work porperly again after power loss?

the ftdi4232 mini should be deliverd on friday, i'll give it some trail and error then :)
  • liutas4x4
  • liutas4x4
15 Jan 2025 07:40

Connecting to FANUC αi-B βi-B (62XX) series servos to LinuxCNC system?

Category: Driver Boards

Two moments:
1. My target is B series Fanuc.
2. How to control with new protocol? Mesa? Connected to original Fanuc adater?

/eugenius
  • besriworld
  • besriworld
15 Jan 2025 07:32

Can the stepgen LPT work in conjunction with the mesa card?

Category: General LinuxCNC Questions

And what does it matter?
if you still have a problem, upload the configuration files. Most likely something wrong with them.
  • chrischan
  • chrischan
15 Jan 2025 07:25
Replied by chrischan on topic Maus funktioniert nicht bei Spindel Start

Maus funktioniert nicht bei Spindel Start

Category: Deutsch

Unfortunately the VFD is a special construction from Paulimot (Paulimot F207-V). I have to take a closer look insight the machine if it is possible to use ferrite beads.

Propably for better understanding I added the wiring diagram of my relays:

 

Yellow marked are the contacts that are provided by the Mesa 7i76. The TB6_OUT_Pin03 switches +12V when spindle is activated in LinuxCNC.

I made 2 tests: 
- When disconnecting Pin03 and using 12V directly from power supply, there is no problem with the mouse.
- When using Pin03 (activated) and then stopping the spindle with stop switch (in the middle) the mouse is also Ok.

On the left side the 2 red cables at the bottom are connected with the internal VFD.

I already ordered a SSR and will test it the next days. And I will have a look inside the VFD.
  • notJamesLee
  • notJamesLee
15 Jan 2025 06:10 - 15 Jan 2025 16:50
Replied by notJamesLee on topic First Start Up - E Stops

First Start Up - E Stops

Category: General LinuxCNC Questions

Thanks for the reply.

I added the code in the linked tutorial, does that bind it to a specific pin? It looks like the last line (below) assigns it to pin10? should I change this to the pin i have mine currently wired to? 
net remote-estop estop-latch.0.fault-in <= parport.0.pin-in10-not
The video so far is very informative and ill use it as a reference when im out working on it tomorrow but no info on how to daisy chain them. I assume since they're NC i can just wire them in series to one input pin? or is that a no-no? 
Displaying 20116 - 20129 out of 20129 results.
Time to create page: 0.390 seconds
Powered by Kunena Forum