Gweike Cloud - Y Axis Rotary Workflow Problem (goes to 10000 after each job)

I have been through enough with this machine at this point to know the Ruida controller is not a “standard” Ruida controller, and there will be quirks. However, I’m wondering if the devs can give me any workarounds for this problem because it’s becoming super annoying when working with rotary.

I’ve set “Return Position” to “No Return” and I’ve tried disabling homing, but the Y-Axis always resets to 10000 in LightBurn. If I could set the Y axis to 10000, that would work fine, but LightBurn does not seem to allow this, unless it’s another controller quirk. That would be an easy solution to this problem. Even in the Move saved settings I can enter “10000”, but then when it moves, it seems to be limited to “3000” instead, but then only will go to “300” max (which is the Y Axis max on this device).

The problem is that I need to have custom calibrated settings when working with the Rotary, so I save my position for easy job setup since the device always wants to home (but the Y axis ends up at 10000 after homing).

So my workflow is terrible because every time I want to set the position to a saved setting, LightBurn wants to unroll the Y axis from 10000 to zero, which the controller happily performs, but it take a couple minutes between jobs to roll from 10000 to zero. :frowning:

Combine this with the fact that it always resets after the job is complete, and I have a horrible workflow right now.

Is there another way to prevent the machine from resetting after the job is complete that I’m missing? Is there a way LightBurn can entertain either allowing me to enter 10000 in the Y-axis Move save setting or disable the Y-axis for setting - for people dealing with situations like this?

I do not have one of these, so I might be well off base … I understand it will also perform a home operation after it completes a job… Also that the Gweike has custom firmware.

I run a standard 6442g and it doesn’t reset values.

If it does home, it can’t do so with a rotary that doesn’t have a homing switch, so I’d expect that axes to read the default 10000 value you are getting.

I don’t know how the rotary is setup with these… do you have a different starting value?

:smile_cat:

No, when the machine starts up with the rotary switch on LightBurn reads 10000 from the start (which probably means it couldn’t read a value). But then if I try to set a saved position, LightBurn happily rotates it from 10000, all the way back to zero. :upside_down_face:

And if you activate the home switches manually between jobs?
As a test.

If the Ruida fails to home, it sets it failed axes to 10000.

I understood it homes again when you run a job and/or when it completes… ?

Can you confirm that? This would reset it to 10000.

Someone with one of these will have to jump in for an assist… I’m not really sure how these operate, especially when switched into rotary mode.

:smile_cat:

Yes, despite Machine Settings that I configure otherwise, when the job completes, it appears to be be homing again, which means it goes back to 10000. The thing is, if LightBurn would just allow me to set 10000 as a value (or ignore Y Axis) then the Move command would not have to touch the Y Axis. That’s all I would really need to workaround this quirk.

Don´t know if I am understanding you correctly, because I believe 10000 is a Ruida thing but you said this:

Try this in your Start GCode, this tells the controller that the position where the laser is, is X0 Y0, pay attention that this may create a limit error.
image

GCode is not an option… this is a Ruida controller with a driver that Gweike provides.

Sometimes I don’t notice it. It’s the late night posts.

1 Like

@jkwilborn What would be the best way to turn this into a feature request? Basically, I need to be able to save a Move position as only X and Z axis moves (ignore Y). Because if I manually move the X and Z axis, this would have the same effect. But if I try to use the window/tab or saved positions, it wants to move the Y axis also, and that is what is interfering with my workflow.

I think the link said it all. Any way to sponsor the change to get it done quicker? LOL. It’s seriously a time killer for me waiting for the Y axis to unroll from 10000 to 0 every time.

It might be an easy fix, but the Ruida may not allow software to change this…

I can enter values to move, but I don’t think it actually changes the axes value.

Might ask one of the technical people and see if they have a usable solution to your issue. I suspect it’s a Ruida/Gweike firmware thing.

Suggest you read through this thread… similar and seems more up to date with some the technical people working with them.

:smile_cat:

Yeah, but this isn’t really my problem. I have everything worked out with the rotary now. If I just use LightBurn to move the X axis for example, that works fine. However, the only way LightBurn gives me to move the Z axis is with the little arrows or with the saved settings. So I cannot set the Z axis precisely otherwise, but LightBurn definitely doesn’t have a problem doing so. It’s really just a “user interface” problem I’m having here. Instead of using the little jog buttons, if I could only just set the X and Z axis numerically (without needing to touch Y) or in the saved settings, then I would have a solution.

I don’t know what to suggest… maybe @JohnJohn knows something about these issues with the Gweike

Hang in there :scream_cat:

:smile_cat:

Well, I found another hacky workaround. I don’t know how to feel about it. LOL. It works, but it’s a crappy solution to a problem the software can definitely help with.

What I did was setup another device profile for rotary printing, and I set the Y axis max (height setting) to 10000.0(mm) for this device so LightBurn would allow me to save a setting with a value of 10000.0(mm). It works and the laser will now move without unrolling the Y axis back to zero. It just stays at the “home” value of 10000 now.

However, there is clearly a UI bug or work needed here. When I setup the device like this, I’m glad I can save Move settings to workaround this problem for now, but the Move window number boxes will only allow values up to 3000.0, so I can only do this by saved settings. That’s fine for now, because I can also only change the Z axis precisely by using a saved setting.

1 Like

For anyone else having a similar problem, here is the feature request I opened:

3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.