Advanced Search

Well, no. No flashing ever happened. mesaflash instantly threw this error and stopped.

Cant do this anymore bye all wrote:

I guess SPI would tie you to an arm platform or trying to bit bang from the host PC.
SPI is not recommended for long distance runs (its only really meant to board comms), even 6 or so inches can be unreliable when approaching MHz speeds. Seen this when experimenting with a Mesa 7c81.

Serial can use differential signals if there is noise, SPI differential signals can play havoc with timing at speeds.

And in reality unless you have a real hardware serial port, the serial comms is USB (at the host PC), doesn't run in realtime......in fact there is no realtime serial driver for Linuxcnc.
 

I actually mentioned this before as you would think as much legacy is built into LinucCNC someone would have worked on an RT serial component. I know Andy replied something along the lines of "I was wondering the same thing" but didn't offer much insight.

Alot of miniPCs expose Intel UART on GPIO headers. I've gotten it to run at reasonably high baud rates but I've only actually used it at standard baud rates. You're pretty much on point about SPI though I2C does get used in alot of cabled applications, Every HDMI cable has I2C in it. It's pretty easy to convert UART to RS422 with just a transceiver IC so that's not a big deal, not sure if using UART for this has any real benefits being there is no RT component but that's one of the things I was hoping to try out as I'd think it'd be just as easy to setup with Arduino-Connector.

I pretty much dropped what I was doing with Arduino-Connector because the lag on the Python side was intolerable. I just looked at the git issues and somebody figured out that it was just due to some serial timeout settings so I'll probably start messing with it again. One problem is I wasn't thrilled about the way the matrix keyboard setup worked and I would up redesigning my key panel to use I2C IO expanders to use with something else that didn't get finished. Now I'm just hoping someone can get support for I2C IO into Arduino Connector so I can try that. I don't think it would be difficult, but I don't do much code myself.
 

Using the sims.ini file, I set up the following:
.
.
.
[RS274NGC]
INI_VARS = 1

[TOOLSETTER]
z_tool = -1
Z_TOOL_HOME = -0.1
X_TOOL_HOME = 0
Y_TOOL_HOME = -10.25


OK ... when I boot up the system, no errors are indicated.  I "home" the system, and switch to the MDI box.

I then put in the following command:

G0 Z#<_ini[TOOLSETTER]z_tool>

It errors and says that the variable doesn't exist.  Hmmm...   so I tried doing ..

#<_ini[TOOLSETTER]z_tool> = -1.25

It took that without issue...  I then executed 

G0 Z#<_ini[TOOLSETTER]z_tool>

and now it works.  hmmm..  What am I doing wrong?  It is supposed to have a variable defined during ini time... but it isn't, at least that is what I am seeing.

It is appearing to allocate the variable AFTER ok, but not during the ini ...    Please set me right.



 

Du bekommst einen Fehler für " halui.machine.is-on" das es doppelt belegt ist?
Du hast es ja auch 2x.
Einmal hier:
net maschine.ist-an halui.machine.is-on whb.halui.machine.is-on
Und einmal hier:
net machine-is-on halui.machine.is-on

Ist "machine-is-on" mit noch etwas verknüpft? Wenn nicht, schmeiß es raus.

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?