MUST BE IN RANGE [NaN,NaN]
no value seems to resolve this error…
Attach your workspace.json to inspection
Also, did you configure your min/max rates on settings?
no, min is set to one on X,Y but max always reverts back to infinity regardless of value entered.
PS. (release 1.0.24 no longer has NaN error but will not proceed past %50 on Gcode generation)
From .json:
{
“settings”: {
“__version”: “4.0.991”,
“__selectedProfile”: “fff”,
“latestRelease": “2018-05-04T16:48:19Z”,
“showMachine”: true,
“machineWidth”: 387,
“machineHeight”: 290,
“machineBeamDiameter”: 0.2,
“machineBottomLeftX”: -387,
“machineBottomLeftY”: -290,
“machineFeedRange”: {
“XY”: {“min”: null, “max”: null},
“Z”: {“min”: 1, “max”: 1},
“A”: {“min”: 1, “max”: 1},
“S”: {“min”: 1, “max”: 1}
},
“machineXYProbeOffset”: 0,
“machineZEnabled”: false,
“machineZMatThickness”: 0,
“machineZToolOffset”: 0,
“machineZStartHeight”: “”,
“machineZProbeOffset”: 0,
“machineAEnabled”: false,
“machineBlowerEnabled”: false,
“machineBlowerGcodeOn”: “”,
“machineBlowerGcodeOff”: “”,
“pxPerInch”: 96,
“forcePxPerInch”: false,
“dpiBitmap”: 300,
“toolGridWidth”: 387,
“toolGridHeight”: 290,
“toolGridMinorSpacing”: 10,
“toolGridMajorSpacing”: 50,
“toolSafetyLockDisabled”: true,
“toolCncMode”: false,
“toolImagePosition”: “C”,
“toolUseNumpad”: false,
“toolDisplayCache”: false,
“toolUseGamepad”: false,
“toolCreateEmptyOps”: false,
“toolVideoDevice”: null,
“toolVideoPerspective”: {“enabled”: false},
“toolVideoLens”: {“a”: 1, “b”: 1, “F”: 1, “scale”: 1},
“toolVideoFov”: {“x”: 1, “y”: 1},
“toolVideoResolution”: “720p(HD)”,
“toolVideoOMR”: false,
“toolVideoOMROffsetX”: 0,
“toolVideoOMROffsetY”: 0,
“toolVideoOMRMarkerSize”: 20,
“toolWebcamUrl”: “”,
“toolFeedUnits”: “mm/s”,
“toolTestSValue”: 1,
“toolTestDuration”: 0,
“gcodeStart”: “G21 ; Set units to mm\r\nG90 ; Absolute positioning\r\n”,
“gcodeEnd”: “M5 ; Switch tool offEnd\r\n”,
“gcodeHoming”: “G28.0”,
“gcodeToolOn”: “M4”,
“gcodeToolOff”: “M5”,
“gcodeLaserIntensity”: “S”,
“gcodeLaserIntensitySeparateLine”: false,
“gcodeSMinValue”: 0,
“gcodeSMaxValue”: 1000,
“gcodeCheckSizePower”: 1,
“gcodeToolTestPower”: 0.1,
“gcodeToolTestDuration”: 0,
“gcodeConcurrency”: 2,
“comServerVersion”: “4.0.127”,
“comServerIP”: “localhost:8000”,
“comServerConnect”: false,
“comInterfaces”: [“USB”, “ESP8266”, “Telnet”],
“comPorts”: [
{
“comName”: “COM3”,
“manufacturer”: “wch.cn”,
“pnpId”: “USB\VID_1A86&PID_7523\5&C1BD4D0&0&9”,
“locationId”: "Port#0009.Hub#0001”,
“vendorId”: “1A86”,
“productId”: “7523”
}
],
“comAccumulatedJobTime”: 553,
“connectVia”: “USB”,
“connectPort”: “COM3”,
“connectBaud”: “115200”,
“connectIP”: “”,
“jogStepsize”: 100,
“jogFeedXY”: 8000,
“jogFeedZ”: 300,
“macros”: {
“*GotoXY0”: {
“label”: “Goto XY zero”,
“gcode”: “G0 X0Y0”,
“keybinding”: “ctrl+f1”,
“_locked”: false
},
“*LaserOff”: {
“label”: “LASER OFF”,
“gcode”: “M5”,
“keybinding”: “ctrl+f2”,
“_locked”: false
}
},
“uiFcDrag”: {“x”: -77.35915837451046, “y”: 19.934427604841517}
}
}
editing of the .json file and setting min.max to 1,300000 results in the message for cut rate to now display those values after a restart of LW.
Fixed. Compiling patched version (will be ready on a couple hours)
Thank you Jorge, (grin) I have 40 years experience with the “fix it here, break it there” coding issue and totally understand.
Thanks! Was literally an uppercase-lowercase mistake