Advanced Search

  Does this diagram apply to a bipolar connection?
www.aliexpress.com/p/tesla-landing/index...aXGaNZQaAvhREALw_wcB

I have now installed version 2.1 which accepts the official version of mesaflash 4.3.6... and I have no problem with exporting the configuration, but mesact messes up the configuration and here are a few things
1: does not export the given maximum velocity
2: export joint 0 instead of x for 7i77
3. will not enable drivers trough ena+ ena- on 7i77
4: instead of recognizing the pins it exports something like 7i96s.0.7i77.0.4 analogout instead of 7i96s.0.7i77.0.1
5.i/o also exports 7i96s.7i77.0.3 instead of 7i96s.0.7i77.0.0
and so on... I can't get a configuration that otherwise works with pnccfg normally, except that I would have to manually enter everything related to 7i96s, so in the end I will have to do that. I don't know how to post what you suggested on github so that the errors can be corrected. sure thank you very much

SOLVED  -
matrixkins is a standard technique for correcting the curvature of the portal in the LinuxCNC 2.10 kernel (and above). The issue of mutual correction of XYZ coordinates is resolved by specifying correction coefficients. However, this component is provided for single-engine machines, i.e. XYZ schemes. To use this software correction for LinuxCNC2.9 and possibly 2.8, you must manually compile and install the matrixkins module (create a text file matrixkins.comp and copy-paste text from github.com/LinuxCNC/linuxcnc/blob/master...ents/matrixkins.comp + sudo halcompile --install matrixkins.comp), and you must make changes to the ini machine configuration file. Hal file does not require correction. MAN does not give these examples. However, in the ini file 
instead of -
KINEMATICS = trivkins coordinates=XYZ
set -
KINEMATICS=matrixkins
then explicitly specify non-zero correction factors, for example -
halcmd setp matrixkins.C_yx -0.00252427184466  

You will find the coefficient values and the transformation matrix in MAN.
The halcmd setp matrixkins.C_yx correction command -0.00252427184466 can be executed in the terminal (not while the machine is moving!), i.e. the parameter can be changed on the fly.

In case you have a multi-engine XXYZ configuration, etc., you need to change the source code of the matrixkins component ( github.com/LinuxCNC/linuxcnc/blob/master...ents/matrixkins.comp ), similar to  www.forum.linuxcnc.org/38-general-linuxc...xyyz?start=20#338894

+ sudo halcompile --install matrixkins.comp

you need to be in teleop mode to jog so I think selecting MDI mode disable this. Check sate of halui.mode.is-teleop 
and select teleop mode by setting halui.mode.teleop to true

added them to the first post, pretty messy but that's where I'm at so far

Any issues relating to this please post here as they apart of the RPi Trixie build
github.com/ozzyrob/pi-gen-linuxcnc

Twice the money is still zero.

Your major issue is a lack of knowledge of how things work. First being not understanding how directory listings are produced by a web server. Secondly not understanding how a Debian repo works, and thirdly not bothering to find out how these things work.
Hoenstly, and I'm trying to be as diplomatic as I can, you have a low knowledge of how and why things work and yet this doesn't stop you giving out adice based on your knowledge. A classic example was when you suggested apt was stupid or frustrating or something similar for not installing packages due to version mismatches, this is to protect the system (and user) from a broken system.
Another thing that is an issue is when you make statements that you have no evidence for such as BSD has low latency, which also points to a lack of understanding of latency and jitter, hopefully you followed the link I provided to an explanation of latency within the context of the Linuxcnc ecosystem.
The thing that hurts the forum is that "member status" is based on the amount of posts. So when you give advice that is wrong or similar it is more hurtful than a recently joined member.
This is not a preseason issue, tho I have made some, I hope offensive remarks regarding yourself, but rather an issue that affects the quality of information that is given in the forum.
Yes I understand we are not born knowing everything, and the more you learn the less you tend to realise you know. Sometimes I am cagey about making sweeping claims, as I know Andy is aware of something that refutes what I said if it was made as a sweeping claim. And I'm thankful for that, I learn a little bit more. We all get corrected no one is special.
So what I'm trying to convey is if you sit back, observe, read and either make mental notes or notes in a notebook or similar and refer to them when answering you will become a member who's post have value. If not you will be seen as just a nuisance.

Stepconf is only for PC parallel ports.
Byte2Bot Parallel Port Raspberry Pi Hat is not an actual Parallel Port, yes it is confusing and probably somewhat misleading the way the Vendor names it. It does not provide any of the logical functions of a PC Parallel Port only presents the pins in a DB25 format and provides some level shifting.

The below is a thread that is more or less an index for the Main RPi4/5 thread.
forum.linuxcnc.org/38-general-linuxcnc-q...l-images-only#325007
Has a section regarding GPIO and there is a working config if you follow the links.
They are there you just have to look.

Just about everything regarding the Rpi4/5 is in this thread
forum.linuxcnc.org/9-installing-linuxcnc...official-images-only

The reason for these 2 threads was to provide users with a "self service and all in one stop".

Don't bother no longer needed.

hal & ini files ?

I'll send you the information tomorrow because I don't have it here at my house.

How to get the AXIS into manual mode at start up?

I have the typical cheap pendant (XYZA select, X1, X10, X100 and 100count MPG) wired into the encoder of a new 7i96s and I've got everything working on the test bench (after some help with an axis scale = 1 issue...)
At first the MPG worked fine until I made any MDI move (home all axis or a G0 x1) and then the MPG would stop responding.
I eventually thought the problem was similiar to one posted here concerning joints vs axis so I went in a swapped a bunch of lines from joint and changed them to be given in axis format and that worked... sort of
The pendant now doesn't respond until I make some form of MDI move (home all or a G0 x1 type thing)
Looking through what I can see, the program is starting in MDI and I really want it to start in Manual
Tried a handful of things relating to force halui.teleop.enabled in the custom.hal and then in the custom_postgui.hal thinking that it was getting overwritten before the program actually got going but with not luck
Tried
setp halui.mode.manual 1
and then
setp halui.mode.teleop 1
in either the custom.hal or post_customgui.hal with no change

I've got forced homing off in the ini and would like to keep it that way
I know the logic behind having the machine not in MPG mode until it's homed but since I can do any MDI command (g0 x1) and it works after than the way is should so it's not a safety thing

As always, any help would be appreciated
M
 

Hello. I am a new user. I've been at this for days and no joy. I just came to the realization that StepConf Wizard does not work on my setup. Here is my logic. 
I have a Raspberry Pi 5 with a :
Byte2Bot Parallel Port Raspberry Pi Hat                  byte2bot.com/products/parallel-port-raspberry-pi-hat
5 Axis CNC Interface Adapter Parallel Breakout Board For Stepper Motor Drivers      byte2bot.com/products/5-axis-cnc-interfa...tepper-motor-drivers.

I am running Linux Bookworm with an installation of LinuxCNC. 

When I run StepConf Wizard and get to the X-Axis page I attempt ot see if I can move that axis - no joy. 

My theory is that it doesn't work. I feel that when I complete the process for a machine which I will call Machine, I end up with a Machine.hal program that has lines containing "hal_gpio.PIN21-out" or "hal_gpio.PIN12-out".

Using the Byte2Bot parallel port, you are NOT allowed to refer to the output on the DB25 connector as PIN1, PIN2, PIN3 etc. Using a Byte2Bot hat with a Raspberry Pi 5, you must refer to the GPIO pin that is connected to PIN2 or PIN3 as it's corresponding GPIO pin on the Raspberry Pi. As an example, PIN2 is actually GPIO9, so the line would have to be "hal_gpio.GPIO9-out" to activate PIN2. 

Seeing how StepConf Wizard is asking me what feature I want to assign to PIN2, I assume it is passing on the command ""hal_gpio.PIN2-out" which doesn't work, rather than "hal_gpio.GPIO9-out" which is required. 

I have noticed that you can pick different interfaces prior to getting to the Axis X page, and the assignments change, BUT there is no corresponding change for the Byte2Bot setup.

I might also point out that I have found examples that PIN2 etc. that reportedly works on the Pi 4  

Having made my case I suspect that I will hear "We can't set it up for every possibility" but I think I am missing something. 

EdWorks


 

I see there wasn't an "actual-position" pdo. There absolutely must be an actual-position PDO when using csp.
I think lcec_configgen didn't do a good job this time and maybe selected wrong PDOs.

There is a long thread about Lichuan LC10E and problems to get that to work.
On page 7 forum.linuxcnc.org/ethercat/52341-proble...rive?start=60#304887
they come to a working setup, a working ethercat-conf.xml
And when I look at it, it's just a standard setup with configurable PDOs, often used.
Combine the ethercat-conf.xml with the hal file from cia402 component github.com/dbraun1981/hal-cia402/blob/main/example/cia402.hal
and I think it should move.

Step/dir at 10000 steps/turn and 6000 RPM (1 MHz step rate) in not an issue for the 7I96S
but it would require a step pulse length < 0.5 usec. Not sure if the drive will work with that.
(the manual seems to lack timing specs) You can change the steps per turn scaling to make this
easier.


You could also use analog in unipolar mode (0 to +10V  plus a direction signal)
This would require an external 10V power supply (12V would be OK with the proper hal setup)