2.0.05 Upgrade Issue with OneLaser Hydra 13

LightBurn Software Questions
, , ,
1

I have been using 1.7.08 with my Hydra 13 for some time now. I had to run a custom Scan Offset test with this machine and dial in the settings. Everything has been working well, but I had some downtime and decided to give 2.0.05 a try today. I downloaded and opened it, everything seemed to be as expected. Ran a test file and it was a jumbled mess, did a test and my Scan Offset was 3mm out at 1200 mm/s, down to 1.24mm out at 200 mm/s. I ran a full test at 200mm increments between the two and cleared my previous settings (which were as expected inside the device settings menu). I entered the new values, the Write button showed up. Once complete, I hit the write button. It went away as expected. I ran another test, it was unchanged, everything was still off. I thought maybe it was just a coincidence and removed Lightburn 2 (I had just saved my Lightburn 1 App) and restored Lightburn 1 back into the folder. Ran it, and looked at device settings, all the new values I had just done in Lightburn 2 were present, there was no Write button, so I went ahead and sent a test from Lightburn 1 to the machine. It was perfect. Reversed again to Lightburn 2, sent same test from Lightburn 2. It was still off like no offset settings were ever entered. Not sure what the issue is, but I decided to stick with Lightburn 1 for now and report the issue. Anyone else run into this?

2

Open v1.07.08 and do a save Bundle. Install v2.0.05 and import the Bundle. Then you know for sure all your settings are carried to the latest version. Let us know if we get a pass or fail grade. :nerd_face:

1 Like
3

Thanks Mikey. I will do this the next time I get some downtime to try V2 again. Appreciate the tip.

1 Like
4

I had some time to start over attempting to upgrade to V2. This time the scan offset settings (even with Save Bundle) did not carry over once again, but for whatever reason, when I ran a new test and updated them, they stuck. No clue. I have been having some other issues with my Hydra and I am about to update to latest Hydra Firmware once support gets back to me, so maybe that is the issue.