I have a problem with the stepgen: the max velocity is too high. Where and which value do I need to adjust? My steps with the Mesa 7i96 are 10,000 steps for the spindle.

The second problem concerns the MVO rotary encoder. The spindle and the normal feed work, but the rapid-feed encoder does not. Even when I swap the inputs for feed and spindle, it still doesn’t work. It seems to be an issue with the GUI/interface? Where can I start looking to solve this?

 

Hello there, I'm new here and have been looking into a reliable way to test my PC latency using different BIOS settings and found this script.
I like it a lot but I have only found the initial version of the script, the one attached to the very first post. I'm only running it from a live image, currently version 2.9.4. Apart from replacing the Vimeo link with a working one, I also found a minor spacing error on line 576: should be:
I also experienced the missing latency output after the script finished so I replaced "secs" on line 936 with "us sdev" as mentioned  here by arvidb:
At line 631, lsusb is called and it was not installed so I ran the following and that fixed it:
I will look for other things to fix and post it here. I hope this thread is not completely dead even though it seems like it, but I feel it would be a shame to let all this good work "go to waste" and not keep the script updated, because during my testing and while running the script, I encountered a larger latency spike than what I could produce manually.

   
Was ist mit "Referenzpunkt gemeint"?
Hast du evtl. versehentlich bei den zwei Setups mit unterschiedlichen 0 Punkten gearbeitet?
Ich würde versuchsweise mal mit einem Setup die Sache probieren.

G-code kann dann für jede einzelne Operation (rechte Maustaste) separat erzeugt werden.

Wenn in der Simulation am Rechner alles "normal" und nur an der Maschine falsch ist, dann sind wahrscheinlich unterschiedliche Nullpunkte benutzt.
 

I take it if still available.

Hallo,
danke dir, ich glaube das könnte die richtige sein.
Zumindest sehen die Bilder so aus wie meine Karte.

Das problem ist ja immer, das die Motor-Outputs, die man in Mach3 eintragen muss, immer anders belegt zu sein scheinen.
Mal ist es 2-3, 4-5, 6-7 usw und mal ist es eine andere Kombination.

Ich mache nachher den Rechner mal an und schließe die Karte an, mal sehen ob es geht.

Für die alte Karte, die jetzt defekt ist, brauchte ich einen Treiber damit das ding funktioniert.
Den hab ich zwar installiert, aber ich hab den nicht mehr.
Habt ihr sowas ?

Danke euch
Matthias

It's working now. But I have no idea what was wrong. I tried so many things, one of them must have worked. Thanks for your help

RotarySMP wrote:

...Could you please post some close up photos of that MACH interface board at top RH in the control cabinet. Is that something like a smart servo for Mach 3?

These are: the CSMIO-IP-S (controller), CSMIO-ENC (encoder interface), and CSMIO-MPG (MPG interface). The picture is attached.
I think I’ll try selling these when I don’t need them anymore, but for now they’re helpful for seeing how the last owner had everything implemented.
The screw-terminal to flat-cable interfaces around these modules are something I will probably keep; they might help clean up the incoming signals in the electrical box.And the answer to that L-holder with the bend on the wrong side is actually that it’s for the single back toolholder. I’m not sure how long it would have taken me to come up with that idea.

I pushed an update for stat-at-speed pin.
Logic was reversed , now it works in csv and pv mode. Should work is best to say.

The cs401pv module just scales and forwards the actual-velocity from the drive.
There isn't much I can do if the drive doesn't provide actual velocity in pv mode.
Look at available pdos and see if you find something that looks like actual velocity?

Hallo Matthias,
wie sah denn deine Konfiguration aus, als deine Maschine noch funktioniert hat?

Grüße 2tinker

I currently have my minimum frequency set in the VFD to 20Hz, as I thought driving the motor near zero would cause overheating. I'll try resetting that to 0Hz, and try your two options. I do like having the spindle disabled when the spindle is not on. So the real solution is to finally send my damaged spare 7i84 to Peter (Talla83), pray he can fix it, and install it so I have enough 24VDC outputs to command the VFD's quick stop pin, and also to control the electromechanical brake,  which is lounging around in the motor cabinet, not pulling it's weight.

While I am also thinking spindles:

I currently have:
The VFD analog command voltage:
net spindle-vel-cmd-rpm-scaled  => [HMOT](CARD0).7i83.0.1.analogout0
...and the spindle RPM measured from the encoder
net spindle-vel-fb-rps       <=   [HMOT](CARD0).encoder.00.velocity
In between these two is a dumb back gear and a dumb variator, and without feedback the gear ratio, and this the scale value for to scale the VFD analog command voltage to RPM is unknown.

To caclulate my instantenous gear ratio, I need to multiply the frequency by a constant to give motor RPM, and then divide encoder RPM. That value can then be setp'd to scale.0.gain
I read that HAL supports all the maths operations of the rtapi_math.h, but I could not find any syntax examples. Do I need any braces or brackets to for this? Can you use HAL signals and HAL pins as variables? 
If you have to do this with INI variables, how do you get the value out of a HAL signal into the INI variable?

setp inst-gear-ratio <= spindle-vel-cmd-rpm-scaled * 56 / spindle-vel-fb-rps
verses
setp inst-gear-ratio <=  [HMOT](CARD0).7i83.0.1.analogout0 * 56 / [HMOT](CARD0).encoder.00.velocity

setp scale.0.gain = {inst-gear-ratio}

It is cold in the basement, and I would prefer not to spend a couple of hours motionless in front of the control trying every imaginable combination of syntax idea
Cheers,
Mark

Start by commenting out core_sim.hal and simulated_home.hal in the ini file.
You are now in the real world, not the simulated.

A quick 5 minute video outlining how to use APT pinning to upgrade Trixie to LinuxCNC version 2.97 and keep Linuxcnc current forever.

Please like and subscribe for other LinuxCNC specific content.

wrote:

PCW wrote:

First, is the a 7I92M or 7I92TM?
 
This is old machine, so it's probably an old board, so it's probably a 7i92M (sans "T").

Just for future reference, the age of machine will have no bearing on whether it's a T or sans T. It will depend on the period the card was bought. History will show the the Spartan 6 FPGA was hard to get at one stage, hence the switch to the Trion device.

In real life, despite what the "maker community" will tell you, a capacitor isn't the end all and be all. Also you'll really need to know the load current,ripple and frequency for determining the capacitor reqired, which will differ from application to application, just mentioning this as a PSA.
What is the best option is a quality PSU, yep a bench PSU is great for testing, a genuine Meanwell or Weidmüller (depending on where you are not as easy to get hold of and a little more $$$) supply wont let you down once installed, I only mention these as these are the ones I've been using for eons, all DIN rail mount. I usually switch the computer PSU on, then the MESA boards PSUs, then the stepper power and finally the servo driver for the spindle. To tell the truth with all the relays (self latching) and stuff the PSU wiring was way more complicated than maybe what is should have been. But each circuit controlling the mains is independently controlled.
Regarding powering the 7i77/7i776 or any other DB-25 daughter I've been powering mine(7i76/7i74/7i73/7i83)by the DB-25 connector, found it to be a simple and solid solution. The 7i73 & 7i83 are also powered by the smart serial cable via the 7i74.

OK i understand but it is the full HMI and the servo part of the xml. These are the only new things i just added due to the new Servo module i got. I did the same config like it is on page 1 where all others sayed it worked fine for them. What would u need to help?