I just sent a job to one of my lasers, using a new computer. I backed up the bundle from the old computer and imported it into the new.
I was doing some bidirectional etching and it came out terrible (Double letters, etc.).
I re-imported the bundle, but still no success.
Finally, I exported the offsets (lbso file) from the old computer and imported them into the new. This fixed the issue.
I’m not sure if the exclusion of the offsets in the bundles is intentional or an oversight, but I can’t imagine why you wouldn’t want them to be included, since both machines are sending to the same laser, so the physical properties would be the same.
I can’t seem to reproduce this. In the testing I’ve done the Scanning Offset Adjustments look to be included in the exported bundle on a per device basis. Import also brought it in correctly.
Is there something unusual about your setup or were there any issues during the bundle backup?
I’m not aware of anything unusual, but the older computer has the most history.
I wonder if the issue I’m having is on the import side. I only imported the machine, not wanting to risk overwriting my settings for other lasers that aren’t on the original machine.
If that’s the case, I apologize. I would have expected those settings to be machine specific.
I am running v1.7.03 for windows on both machines. (Windows 10).
There must be something going on, unique to me.
I went back and cleared out the offsets on the new machine and have tried importing them again. I’ve now done it 4 times, but the offsets don’t show up for me.
They do import correctly from the lbso file though.
I think I figured it out. I already have a machine with the same name. I assumed, apparently incorrectly that it would get overwritten. Instead, each time I import it makes a new copy of the machine with a (1), (2), (3), etc. which I didn’t notice, because I wasn’t clicking the device dropdown.
I did the import and saw a machine with the correct name selected in the devices and didn’t look any further.
A prompt to overwrite the machine or keep the prior copy would have been helpful, but it appears to work fine as it is.