VCARVE - EASEL Clarifications Needed

Edward I don’t think you understand the issue I am having.
My configuration wass also done with standard Easel on a late 2016 X Carve. To my knowledge there have been no changes that would come into play here.
When jogging with the VTransfer all axis move as they should.
I believe the issue is that VTransfer thinks contact is made immediately when the probe is plugged in and that is why it raises and alarms when activated.

I ask for any XCarve Vectric users to join in the thread and report their experience with VTransfer.