In the Console Window, please enter
$130=400
and also
$131=400
Which will update the max travel for each axis, should fix your problem.
It’s interesting that the ‘Device Size Mismatch’ dialog reported this in a kind of back-to-front way.
1 Like
Changed that over, now showing below - Interestingly, the promp came back, I accepted the change, but it didn’t change anything in the $ code. weird.
Had a play about but alas, still showing as -380 max travel on the machine positioning when using jog, it will not go past -379, pressed home and its now 397 - extract of $$code below
$120=300.000
$121=300.000
$122=30.000
$130=400.000
$131=400.000
$132=50.000
ok
?<Idle|MPos:0.000,-379.000,-3.000|Bf:35,254|FS:0,0>
ok
?<Idle|MPos:0.000,-379.000,-3.000|Bf:35,254|FS:0,0>
\x85?<Idle|MPos:0.000,-379.000,-3.000|Bf:35,254|FS:0,0|WCO:-399.000,-399.000,-3.000>
?<Idle|MPos:0.000,-379.000,-3.000|Bf:35,254|FS:0,0>
ok
?<Idle|MPos:-379.000,-379.000,-3.000|Bf:35,254|FS:0,0>
\x85?<Idle|MPos:-379.000,-379.000,-3.000|Bf:35,254|FS:0,0>
?<Idle|MPos:-379.000,-379.000,-3.000|Bf:35,254|FS:0,0>
ok
?<Idle|MPos:-397.000,-397.000,-3.000|Bf:35,254|FS:0,0>
Checked the Worksize in the Device Settings tab, and that had been changed back to 380mmx380mm ( I now assume this is what the prompt changed)
Flicked that back to 400x400mm and the machine seems to be jogging as intended!
Hurray.
Glad to hear it! 
2 Likes
Thank you for ALL of your support. I no doubt put this down to Operator Error 
1 Like
It’s my pleasure (and my job ) so not a problem at all!
Not operator error - it is curious that the device was set to 380mm in the controller settings, that would throw you off, and also our mismatch dialog didnt seem to be reporting quite right so I’ll look into that further.
3 Likes
No advanced there but we have it all sorted, seems like a bug