Advanced Search

So pll-error remains 0 for me. App phase hovering between 9800 and 10500

What i did notice, i had all 3 axis vibrate like crazy upon first Launch today. Rebooting lcnc fixed that.

Edit: did another power cycle. No Vibration but sudden clunking on all 3 axis again

I think I overlooked the control type (because its in the pin list rather than a parameter.)

Thanks

QtPlasmaC updates - Master (v2.10):

• fix framing and missed interlock

I'm not sure if I set the control mode to 1. I'll have to check that. I thought I had most of the settings the same as the stepgens that were in use, and those are commanded by velocity command from the PID.

Hello, 

I can see merge of your progress to master? Am I right ?

Regards e.

7i97t_7i74d.bin  would be the correct firmware for a 7I97T +7I74

Note that with this firmware sserial channel 0 is on the 7I97T
and channels 1..7 are on the 7I74 (7I74 physical channel 0 does not work)

 

It seems I will try gmoccapy. It looks more friendly for me. And possibility to add stand alone pyvcp will help me too.

Once more, thank you for real help.

/eugenius

You can certainly get firmware that replaces the step/dir outputs to PWM/DIR,
but then you still need multiple channels of PWM/DIR --> +-10V analog conversion
and then you are still missing the multiple encoder channels needed.
So, a 7I78 is really the wrong starting point here. Mesa should have 7I97Ts
in 1-2 weeks so that is the simplest solution I see. Production 7I77Us are still
about 6-8 week away.

Mbrand1901 wrote:

Can someone please send me the right firmware for that config? I have tried a few and it wouldnt work. Also the encoders stopped working after the new firmeware.

Don't do that, just don't.
You need firmware for 7i97T with 7i74, you do not need anything for 7i84 as that is an SSerial board so it needs no firmware per se, it is a Smart Serial so it arranges things on it's own when communicating with the FPGA.
And, never ever flash Mesa boards with random firmware, except from Mesa website and explicitly for the FPGA you have.

Hello everyone,I am currently working on bringing an old CNC milling machine back to life. The machine uses analog axis drives with a +/-10V command signal.The original controller (NUM 1040) is no longer working. However, the axis drives are still functional. They are ELMO SSA-6/100OPT2 drives.My plan is to replace the controller with LinuxCNC. I already have a Mesa 6I25 and a 7I78 card, but these only provide STEP/DIR outputs, which are not directly compatible with my analog +/-10V drives.I am therefore looking for a solution to convert STEP/DIR signals into an analog +/-10V command. I have seen that it may be possible to convert STEP/DIR to PWM and then from PWM to +/-10V, but I am concerned that this could introduce latency or reduce control quality.Another option would be to use a Mesa 7I97 or 7I77, which natively support analog +/-10V outputs, but unfortunately these cards are currently unavailable.If anyone has experience with a similar setup or knows a reliable solution, I would greatly appreciate your advice.Best regards.

i just tried using the facing one and it does do things, but i really am not a fan of the setup, i suspect it is incomplete compared to the original macros andy put out. it looked to have several missing inputs. and im not a fan of it running without having a chance to see the output plot for verification. i would say the subs need some work before i would use them personally.

did you verify your paths for the subroutines were correct? those look to be correct names to be parsed. it appears you have hardcoded max rpm speed instead of using the ui entry. but other than that the names look to be correct. I would test by copying the subroutine and trying to run it as a program filling in the data as expected and see if you can make it run, may tell you if the subroutines is correctly formatted or not.

Did you set the stepgen to control mode 1?  (velocity mode)

Is the stepgen enabled?

I use stepgens all the time for encoder and frequency counter testing
so this will work.

Sserial parameters can only be set in the hal file, but this is not true of general
hostmot2 parameters, these can be changed at any time. Even though hostmot2 parameters
can be changed at any time, this may lead to unexpected behaviour as these are typically
used as setup rather than process variables.

Also of you want a step frequency change, you will have so set the stepgen acceleration
to a large number.

I have the same issue as TAKUYA, the dc-phased pin never goes high. I managed to fix this using Claude AI and now the dc-phased pin goes high. I have attached a detailed notes of what was changed in the code as well as some screenshots from before and after.

NOTE: this was done entirely with the help of AI and I am not qualified enough to say whether it is correct or not! Grandixximo, could you please review the notes and share your thoughts? Opening the attached HTML file in a browser, you can view the notes which were generated. It is too long to copy-paste here.

EDIT: After testing the code more thoroughly, I'm getting jitter again. It's very likely that the AI's "fix" only addressed the dc-phased pin but broke something else... I've reverted back to the master branch ( github.com/grandixximo/linuxcnc-ethercat ), and everything is working again except for the dc-phased pin.

we are revamping many things in the pyside6 version currently, 2 of the things being worked on is vtk and the gcode plotter. both are seeing some very big changes, so i will add this to the list of things to add some simulation functionality to.