Looking at your post, I suspect you were dealing with sales support. Think Telstra service desk trying to resolve a dns issue. You do need to understand that they are not native English speakers and that they, normally, would try to do their best to give you a happy ending. That they said ‘our engineer doesn’t give us that’ is normal, too - they are trusted less than a pedo at a primarily school - with tech stuff. They got their job because they read and write and can almost speak English. Nuance is lost on them.
I understand it can be frustrating, but likely a lot less frustrating than a Chinese person calling the NSWDCS.
They didn’t deliberately set out to make things hard.
Have you spoken to the vendor of your machine or the place you bought the controller? That would be the normal channel for support. RuiDa isn’t a retail vendor and would not typically speak to an end-user.
And that is very normal in Chinese tech companies - they’re not just being dicks. They have a relationship with distributors, the distributors deal with the customer - that’s why they get massive discounts.
Here are the files for the 6445G. 19 might show internally as 18, but I believe it was a patched 18 that they didn’t change the internal version number on. I don’t have a 6445G handy to check.
Ver 22: https://drive.google.com/open?id=1vlQdGtosCyFzW8G9Be3RF700t0KsEVys
Ver 15: https://drive.google.com/open?id=1qQnmHN1ILwbs83uI2Zj4iFl5y9AhQC-D
This is, to my best knowledge, the latest mainboard firmware for the 6445G: RDC6445G-HMI-V10.01.07
Upgrading firmware and expecting it to fix your problem is only half the job - there may have been changes in the .22 firmware that need setting, and it may need an accompanying HMI main board firmware change, as well. Again, your vendor should have that information.
What is difficult is getting revision information - like just what did they change, what is needed for that change, any additional parameters, etc. It’s usually a case of trial and error to save your existing config, and most especially, your vendor settings, read the existing config and save it, upgrade, read config and save it and do a comparison. I use what we geeks call a ‘diff tool’ - here’s an easy online one: https://text-compare.com
As to Ruida, they make the best DSP controllers for CO2 lasers out of China. I’m not changing any time soon. I have seen your level of frustration many times - it’s what pays the bills - and invariably I’m being paid to fix an incomplete revision because hobbyists/users think they’re engineers.
Not meant as a slight - it’s just the way it is. I hope you take it constructively.
These are complex devices, they aren’t intuitive and the software the companies use to develop them are years back in the toolchain. Again, understanding why that is results in less frustration.
And you are trying to integrate an accessory that they have no knowledge of.
Rotary engravers are notoriously fiddly to get right, but when you do, you’re laughing.
That your controller just doesn’t seem to understand how to talk to the device says to me, there’s something not right in the device that you’re not accounting for in the firmware config. That no matter what you do, it rotates too much says there’s a setting not right.
And, as I said before, it would be unusual for a company like Ruida to put out a release that has less functionality than before.
I think you need to go back and step-by-step your .18 config and see that when you update to .22, there isn’t a new ‘feature’ that is unpopulated.
It’s annoying and laborious and a pain in the arse, but if you want your machine to run properly, that’s what youre going to have to do.
And understand you bought one of the cheapest-made machines (where are Red and Black based, again?) from some anonymous eBay seller and you have not necessarily received the best QC.
I’m confident this problem can be fixed, despite you knowing of three other people that have had the problem - for no other reason than that Ruida have probably sold tens of thousands of that model controller.
Just as an FYI, the place I source my machines and parts from has a crew that are all ex Beijing University physics lab grads. They are PhDs, MEng, EE, etc. their machines are set up impeccably and I’ve never needed to change firmware except for external damage needing a new board. If your machine came with .22, it should work. If it didn’t come with .22, why did you change it?
And lastly, if it works with .18, why the fuss?