G92 emulation unable to determine all coordinates to set via x3g:140


#1

I am getting this message in the terminal window "G92 emulation unable to determine all coordinates to set via x3g:140 set extended position" when I try to print in octoprint (1.38) to my FFCP.
The stepper motor is taking very small steps (sounds like it is vibrating) and after a while (~ 3 min) stops and the nozzle heater turns on. In the Temperature graph I get a spike for the nozzle temperature target then it goes back to zero. After several minutes the target goes back to operational temperature and the nozzle heats to target, maintains temperature then target goes back to zero and the nozzle heater goes back to zero. It never starts the print.

Octoprint 1.3.8, octopi 0.14.0

Term tab:
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: <GPX.gpxprinter.GpxPrinter instance at 0x6e340df0>, starting monitor
Changing monitoring state from "Opening serial port" to "Connecting"
Recv: start
Send: N0 M110 N0125
Recv: Sailfish v7.8
Recv: echo: gcode to x3g translation by GPX
Recv: SD card ok
Recv: T:107 /0 B:0 /0 @:0 B@:0
Send: N0 M110 N0
125
Recv: T:107 /0 B:0 /0 @:0 B@:0
Recv: ok
Changing monitoring state from "Connecting" to "Operational"
Send: N0 M110 N0125
Recv: ok
Send: M115
Recv: ok PROTOCOL_VERSION:0.1 FIRMWARE_NAME:Sailfish FIRMWARE_VERSION:7.8 FIRMWARE_URL:http://www.sailfishfirmware.com MACHINE_TYPE:r1d EXTRUDER_COUNT:0
Send: M20
Recv: ok
Recv: Begin file list
Recv: DCIM
Recv: Collered Stopper v8.gcode
Recv: Collered Stopper v8.x3g
Recv: LED Holder v2 v5 v1.gcode
Recv: For Windows
Recv: Gears
Recv: End file list
Send: M105
Recv: ok T:103 /0 B:0 /0 @:0 B@:0
Send: M105
Recv: ok T:102 /0 B:0 /0 @:0 B@:0
Send: M105
Recv: ok T:101 /0 B:0 /0 @:0 B@:0
Send: M105
Recv: ok T:98 /0 B:0 /0 @:0 B@:0
Send: M105
Recv: ok T:97 /0 B:0 /0 @:0 B@:0
Send: M105
Recv: ok T:95 /0 B:0 /0 @:0 B@:0
Send: M105
Recv: ok T:93 /0 B:0 /0 @:0 B@:0
Send: M105
Recv: ok T:92 /0 B:0 /0 @:0 B@:0
Send: M105
Recv: ok T:91 /0 B:0 /0 @:0 B@:0
Changing monitoring state from "Operational" to "Printing"
Send: N0 M110 N0
125
Recv: ok
Send: (@build "LED_Holder_v2_v5_v1")
Recv: ok
Send: N1 M136 (LED_Holder_v2_v5_v1)50
Recv: ok
Send: N2 G92 X0 Y0 Z0 A0 B0
88
Recv: ok
Send: N3 G9019
Recv: ok
Send: N4 M83
28
Recv: ok
Send: N5 M73 P082
Recv: ok
Send: N6 G162 X Y F3000
78
Recv: T:90 /0 B:0 /0 @:0 B@:0
Recv: ok
Send: N7 G161 Z F120055
Recv: T:89 /0 B:0 /0 @:0 B@:0
Recv: ok
Send: N8 G92 Z-5
120
Recv: ok
Recv: // echo: (line 8) warning G92 emulation unable to determine all coordinates to set via x3g:140 set extended position
Recv: // echo: current position defined as
Send: N9 G1 Z0107
Recv: // echo: X:nan Y:nan Z:-5.00 A:0.00 B:0.00
Recv: ok
Send: N10 G161 Z F100
51
Recv: T:88 /0 B:0 /0 @:0 B@:0
Recv: ok
Send: N11 M132 X Y Z A B107
Recv: T:88 /0 B:0 /0 @:0 B@:0
Recv: ok
Send: N12 M135 T0
83
Recv: ok
Send: N13 G1 X150 Y-70 Z30 F900019
Recv: // echo: (line 12) Semantic warning: T0 cannot select non-existant extruder
Recv: ok
Send: N14 G130 X20 Y20 Z20 A20 B20
100
Recv: ok
Send: N15 M12719
Recv: ok
Send: N16 M140 S80 T0
46
Recv: ok
Send: N17 M134 T087
Recv: // echo: (line 16) Semantic warning: T0 cannot select non-existant extruder
Recv: // echo: (line 16) Semantic warning: M140 cannot select non-existant heated build platform
Recv: ok
Recv: // echo: (line 17) Semantic warning: T0 cannot select non-existant extruder
Send: N18 M104 S220 T0
24
Recv: // echo: (line 17) Semantic warning: M134 cannot select non-existant heated build platform
Recv: ok
Recv: // echo: (line 18) Semantic warning: T0 cannot select non-existant extruder
Send: N19 M133 T0*94
Recv: T:87 /0 B:0 /0 @:0 B@:0
Recv: T:86 /0 B:0 /0 @:0 B@:0
Recv: T:86 /0 B:0 /0 @:0 B@:0
Recv: T:85 /0 B:0 /0 @:0 B@:0
Recv: T:85 /0 B:0 /0 @:0 B@:0


#2

I suppose that this problem is unique based on the number of replies. I might add that since the original post, this setup works fine with astrobox by changing the raspberry pi octoprint configured micro SD card to an astrobox configured micro SD card indicating neither the hardware nor printer are at fault.


#3

I'm having the same issue, did you end up finding a solution?


#4

I did not find the problem specifically. What I did to "fix" it was to reload octoprint and start over. In my case, that was not a terrible solution, but a pain to have to reflash everything. Btw, this was a setup that was in use for over a year.
Hope that helps.