is a RDC6432G homeable?

[Jeffrey Aley]

yes, ive done that, with all variations of enable homing and limit trigger (both on, both off, one on/one off etc) all to no avail. it just will not home either from software or on start up. its like the controller just ignores those settings...

I apologize in advance if I insult anyone's intelligence.
When accessing the vendor settings, one has to first READ the settings from the machine. That'll clear out the crap that's in RDWorks and replace it with the true settings. Then one can WRITE the settings to the machine. One can also SAVE the settings to a file. But the point is that we must always READ before we change something, and then we must WRITE it back.


At this point I suspect that the OP has a defective controller

[Dexter Oddwick]

thank you for all the replies!

At this point I suspect that the OP has a defective controller

this is what i was beginning to suspect, but it turns out that i have a solution!!!! now everything works correctly, so i will post this to help anybody else in my shoes. after emailing cloudray, i received a detailed fix for this problem. i do not know if it is specific to only 6432 controllers or possibly more, but here it is.

first off, you need to use RDWorks 8.01.54-20210513 to fix this. the only place i have found this version is on cloudray's site.

https://cloudray2021.oss-us-west-1.aliy ... 210513.rar

there is a hidden menu on it with a second set of vendor settings.

hidden_menu.jpg

so once you have a connection, you read from the controller as you would normally change your settings and write back to the controller and VOILA! it now homes automatically on startup and reset.

also, i have seen a few posts on here of people asking for just the opposite, they do not want their machine to auto home on startup. why? who knows, but possibly this might answer their questions too...

again, thanks to all who helped me and taking time to answer my questions!

[Gene Uselman]

Thanks for updating us with the solution- that menu does not exist in older versions of RDworks so I assume it is an RDworks problem instead of the controller series? Lightburn is looking [and working] better all the time.

[Dexter Oddwick]

I assume it is an RDworks problem instead of the controller series?

honestly i am not sure if it is specific to this controller or not. it seems to be a set of hidden options that possibly until now were not accessable through software and ruida just opened them up for editing.

i have seen a few posts where people were wanting to turn off auto homing and this might be the solution if it works for other controllers. i wouldnt know because this is the only one i have. it would be and interesting investigation.

Lightburn is looking [and working] better all the time.

i agree, and now that this is fixed, i will return to lightburn. aside from the fact that i cant connect through usb to my machine (i use a macbook) and have to use an ethernet adaptor, it just works so much better all around!

[Dave Vigness]

It's an RDWorks & Firmware version problem. New firmware and old RDWorks is the problem. If you have old / old or new / new, you're good. It's when you have new firmware and old RDWorks that the signals get confused. Had the same problem with the WIND coming on and off with the laser tube instead of the layer when I upgraded my firmware and didn't have the new RDWorks installed yet. Didn't even dawn on me for your problem.

[Jeff Thorn]

did you ever get it working ? If not I may be able to help, I just went thru the same problems and was able to get cloudray to tell me how to fix it . let me know

[Gene Uselman]

Hi Jeff- it would be a kindness to document the Cloudray procedure as surely the people following in our footsteps will be happy to see it. Thanks Gene