Advanced Search

Actually it throws the error when attempting to change tool from 0 to 1.
Would I be correct to say that unless probe routines are created and probe defined, then Probe Basic Lathe cannot be used as an interface for Lathe?

Axis works perfectly, so I can at least use that!

Apologies if this is an obvious thing, still learning here

Something tells me that this python reference to the os.path is incorrect?

Qtvcp python plugin found: /home/andy/.designer/plugins/python/qtvcp_plugin.py
Traceback (most recent call last):
  File "/home/andy/.designer/plugins/python/qtvcp_plugin.py", line 49, in <module>
    from qtvcp.plugins.dialog_plugin import *
  File "/home/andy/linuxcnc-dev/lib/python/qtvcp/plugins/dialog_plugin.py", line 5, in <module>
    from qtvcp.widgets.dialog_widget import *
  File "/home/andy/linuxcnc-dev/lib/python/qtvcp/widgets/dialog_widget.py", line 33, in <module>
    from qtvcp.widgets.versa_probe import VersaProbe
  File "/home/andy/linuxcnc-dev/lib/python/qtvcp/widgets/versa_probe.py", line 47, in <module>
    ICONPATH = os.path.join(PATH.find_image_path(), 'probe_icons')
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen posixpath>", line 76, in join
TypeError: expected str, bytes or os.PathLike object, not NoneType

Since OS is already included. Or perhaps the var isn't already defined?

Wow I never thought of needing to setup the probe first!
And yes was looking to use probing to calibrate tool offsets, have seen this done by at least one other person and it seemed a useful and reliable method

So the sim does not have probing configured for lathe either?

But to be honest, main reason for using QtPyVCP is because it looks so very, very, nice!

Did you do
mesaflash --addr 192.168.1.121 --device ETHER --reload
or power off/on the board after flashing?

Hi,

I'm trying to flash my 7i96s mesa card to get a second PWM (btw - I had a hard time finding this file. PCW always mentions the '7i96s-support-file-zip, but I have failed to locate it).

Card works ok and:
mesaflash --addr 192.168.1.121 --device ETHER --readhmid
works without problems and produces this output (abbreviated):

Configuration Name: HOSTMOT2

General configuration information:

  BoardName : MESA7I96
  FPGA Size: 20 KGates
  FPGA Pins: 256
  Number of IO Ports: 3
  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
...

I was a bit confused about the first line above, but it is indeed the 7i96S. At least that's what's written on the board.
Upon flashing, I get this:

markus@JanusL:~/mesa_firmware/7i96s_2pwm$ mesaflash --addr 192.168.1.121 --device ETHER --verify 7i96s_2pwmd.bin
Checking file... OK
  File type: Efinix bin file
Verifying FLASH memory sectors starting from 0x100000...
  |
Error at 0x10004B expected: 0xA but read: 0x16

Thanks
 

zelo, you speeds in your config arent that crazy. you should be abkle to go faster. if you are only seeing the issue with jogging, try doing a test, by lowering the accel and raising the velocity.

Hi all, I am trying to troubleshooting my router set up on qtdragon_hd  with manual tool change with a tool length sensor. It will run the tool length procedure just fine (without a multi-tool file loaded) and will run a single tool gcode no problem but starts yelling at me when I try to run anything with a M6 command. The issues are probably not with the gcode I am using but just to be sure can someone please send me a simple example of a part with three tool changes? I am using mm.

many thanks 

Luke 

 

Servos often drift when the controller (linuxcnc) is disabled.
The usual way to counteract this problem is to disable the servo drive when linuxcnc is in 'machine off'

For instance the signal 'x-enable' is the signal used to disable the X axes servo.

Your servo drive surely has a enable/disable connection.