Advanced Search

A very common method was to start on Y configuration and then switch to Delta. The motor starter switched between Y and Delta (contactors).
Ask google or chatgpt for the reason.

Depends on what you are aiming at, but a standard chinese VFD controlled by Modbus/USB is a common way to get speed control of the spindle.
The rpms can be somewhere 50%-150% of nominal rpm. Low torque at low speeds, possibly balancing issues at high speed, but at least some variation up and down is possible.
USB/Modbus is somewhat sensitive to electric noise so it is usual to have USB serial/RS485 with optocouplers and line filter for the mains.

Good point about checking chrome://gpu, it shows a number of problems with graphics features, such as hardware decode being software only.

Graphics Feature Status
Canvas: Hardware accelerated
Direct Rendering Display Compositor: Disabled
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
OpenGL: Enabled
Rasterization: Hardware accelerated on all pages
Raw Draw: Disabled
Skia Graphite: Disabled
TreesInViz: Disabled
Video Decode: Software only. Hardware acceleration disabled
Video Encode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
WebGPU: Disabled
WebNN: Disabled

 

Problems Detected
WebGPU has been disabled via blocklist or the command line.
Disabled Features: webgpu
Accelerated video encode has been disabled, either via blocklist, about:flags or the command line.
Disabled Features: video_encode
Accelerated video decode has been disabled, either via blocklist, about:flags or the command line.
Disabled Features: video_decode
Disable partial swaps on Mesa drivers (detected with GL_VERSION): 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Expose WebGL's disjoint_timer_query extensions on platforms with site isolation: 808744, 870491
Applied Workarounds: enable_webgl_timer_query_extensions
Some drivers can't recover after OUT_OF_MEM and context lost: 893177
Applied Workarounds: exit_on_context_lost
Avoid waiting on a egl fence before swapping buffers and rely on implicit sync on Broadcom GPUs: 938286
Applied Workarounds: rely_on_implicit_sync_for_swap_buffers
Disable GL_MESA_framebuffer_flip_y for desktop GL: 964010
Applied Workarounds: disable(GL_MESA_framebuffer_flip_y)

Full report attached below.

I don't think the issue is hardware or resolution, since it is just this image that has these problems.

Small update. When there is no g96 /G95 command in the program, the program calculates the approximate time correctly. Maybe feed per rev is not calculated correctly. Thanks for the great work! I understand that this problem is not in the field of gmoccapy

Thanks for the report, this has been fixed.

JT

Hello EmilDLo,
mine is right now working with your config. I can start it up to explicit RPM, change RPM and even stop without problem. I didnt change anything on your XML, Ini or hal, so your problem completly is in your VFD set up.

Thanks for that, nice touch having the interval/on times adjustable from the status page, very handy.

The WLED should be great for general status conditions and minor warnings at a glance, looking forward to adding some bling to my machines.

Cheers.
Russell.

I managed to resolve it. Turns out those boards are maybe not for the same type of encoder? The sin and cos were inverted and so were their + and -. The connector was also mirrored the wrong way. I managed to cross the DB15 connector pins in a way to get it to work, though, and I can happily report it's basically plug and play after that. All that's left is to play around with the resolution with the jumpers a bit...

a little tip on what you can do with the wled's to display the status:

 

in dev branch and untested (only via testbench):

github.com/multigcs/riocore/blob/dev/rio...s/interval/README.md

little config example 10 seconds on / interval 20 minutes default
looks like this:
 

and the onTime can be adjust between 5 and 20 seconds / interval between 600 and 1800 seconds (10 - 30 minutes)

 

i will add a new plugin named 'interval' or so.
then you can configure the on-time and the interval-time via gui/hal

You can make "no encoder reset" & use standart linuxcnc homing procedure

Hey,

I have a Mesa 7i95t board that to my understanding has support for RS485.

I want to connect my Delta MS300 VFD to LinuxCNC over RS485, and I think I have two options:
* I've got a USB RS485 dongle that I can connect to the PC and to the VFD on the other end
* I can connect the Mesa board's RS485 terminals to the VFD

Which one of these options are preferable? Are both these options correct, and are there any pros/cons to either?

Thanks!

Guten tag zusammen,
Ich wende mich an euch weil ich den Anschluss vor lauter kabeln nicht mehr sehe.

Konkrekt geht es um 
4 x Step-Dir Servos
1 x -10 bis +10V Spindelservo
2-3 0-10V Spindelservo
8 Eingänge für je 2 Achsendschalter
4 Ausganänge für Bremsen

dann noch Aus und Eingänge für Allfälliges 

Die erste Kombi die mir eingefallen ist war 
7i92TH
7i77
7i90HD
7i85
die 7i77 und 7i90HD kann man über IDC26 P1 und P2 mit IDC26 -> DB25 verbinden
aber dann hat die 7i85 noch keine ansteuerung. Kann ich die auch an die 7i92TH hängen? wenn ja wie bitte oder braucht die 7i85 eine weitere 7i92TH

Das war so mein gedanke 
was würdet Ihr verwenden oder einsetzten 

Danke mal wieder für die hilfe und schöne grüße aus Österreich
 

i found a solution that worked.
i change inside my inverter to 0-5v input and adjust the potentiometer on the china pwm to analog pcb.
then i change the scale in the hal for the pwm.

50% 12000 rpm 203hz
100% 24000 rpm 400hz
75% 18000 rpm 305hz
25% 6000 rpm 101hz
12.5% 3000 rpm 49hz

it works for me

thanks guys

Thank you so much PCW