I don’t believe so. I think this error is specific to this stacker carrier and how the WOI for the 2D autoload is set. Since you aren’t scanning barcodes, changing the number of positions to 0 in the properties skips the logic for setting the WOI altogether which prevents the error you are seeing.
Setting MlStarNoReadBarcode to 0 accomplishes the same thing, but the WOI still gets set in the background which leads to the error as there is a range issue for this particular carrier.
Using MlStarNoReadBarcode on a standard carrier should still work as expected.
We are working to prevent this error from happening in future releases, but this workaround has been getting past the issue.