I tested it as I thought in my previous post and it works as expected.
The offset setting in the controller works different to the offset function in device setting in lightburn.
I deactivated the head 2 offset using the vendor settings function in rd works and then re-wrote the parameters to the controller with no head offset.
This then disabled the virtual “smart calculation” for the virtual array function and the machine now responds with the second head in lightburn (and rd) as described by you originally.
So as I understand it - the offset function in the controller is the exact distance between head 1 and head 2 ( when the head number 2 is at its home position as close to head 1 as possible)
It then uses this figure to calculate the virtual array and give the most economical way to use both heads on its own. The function is actually quite clever and different to how I expected the machine to function.
By deactivating this function in the controller the head number 2 no longer has this calculation ability and works as instructed on a simple basis by either rd or lightburn.
you can manually jog the position of the second head to the desired distance.
You then select the head you want to fire either number 1 or number 2 or both and the system simply follows the shape and cuts the parts with the selected heads.
This way is more complicated to calculate the material you are using but gives more versatility on how the user wants to use the machine.
This is how I expected the machine to operate before I purchased it and also I gather this is how you at lightburn expected it to also.
I haven’t had chance to check exactly how the offset function in lightburn works yet as I could not get it to function in the way I expected.(and ran out of time)
I will run more tests and report the findings.
Thanks for your help and hope my findings are helpful to you also.