Lid Temperature Errors

Hi, I’m hoping I can avoid a $1,000 shipping fee to send my UK based glowforge back to the USA for repair.

HELP!!!

The unit has suddenly started cutting out, usually mid-engrave, very occasionally mid-cut - but only if there is little head movement.

GF have said they can’t fix remotely (hence the hefty back to base cost).

The unit just stops. Fans still running, but the laser is off and the head is stopped. In fact the head is free, I can move it around easily, no resistance from the motors. Also lifting the lid does not cancel the job.

My only option at that point is to reboot the machine. But, it won’t. It needs a 20 to 30 minute gap between power off and power on to actually restart - then it will work fine for a while. I suspect a thermal switch needing to reset?

Finally, it seems more sensitive when room temperature is warmer, though that is harder to test.

I think I’ve got a temperature sensor issue and/or the “black cable” problem.

Venting and air flow looks fine. Cables around lid all look fine, no obvious wear or breaks (in fact I rarely open the lid fully)

And having download the logs I can see:

This near the start up

2019-09-23_18:57:50.84042 38921 INFO: lid_image [73582859]: state=ready
2019-09-23_18:57:50.85338 38925 INFO: cam: Entering state Capture
2019-09-23_18:57:50.85343 38925 ERROR: cam_flash_on: failed to set cam_flash_on=0 (9c0908) (src/cam_peripheral.cpp:31)
2019-09-23_18:57:50.85345 38925 ERROR: cam_flash_mode: failed to set cam_flash_mode=2 (9c0901) (src/cam_peripheral.cpp:31)
2019-09-23_18:57:50.85346 38926 ERROR: cam_switch: Failed to get cam_switch (8000008) (src/cam_peripheral.cpp:14)
2019-09-23_18:57:50.85347 38926 ERROR: total_buffers: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85349 38927 ERROR: corrupt_buffers: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85350 38927 ERROR: cam_switch: failed to set cam_switch=0 (8000008) (src/cam_peripheral.cpp:31)
2019-09-23_18:57:50.85351 38927 ERROR: mipi_csi2_phy_state: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85352 38928 ERROR: mipi_csi2_error1: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85354 38928 ERROR: mipi_csi2_error2: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85927 38929 ERROR: camera_peripheral: Unable to select to lid camera: MIPI_CSI_PHY_STATE=0x00000000, MIPI_CSI_ERR1=0x00000000, MIPI_CSI_ERR2=0x00000000 (src/cam_manager.cpp:274)
2019-09-23_18:57:50.85932 38929 ERROR: mipi_csi2_phy_state: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85933 38929 ERROR: mipi_csi2_error1: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85935 38930 ERROR: mipi_csi2_error2: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85936 38936 ERROR: total_buffers: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85937 38937 ERROR: corrupt_buffers: read error (9: Bad file descriptor, src/source.h:209)
2019-09-23_18:57:50.85939 38939 ERROR: cam: Failed to capture frame (src/cam_task.cpp:98)
2019-09-23_18:57:50.86445 38944 INFO: cam: Entering state Standby

And a lot of these repeated over and over again to the end of the log:

2019-09-23_18:59:52.47652 160550 ERROR: fused_temp: could not read lid temp sensor (src/sensor_task_peripherals.cpp:397)
2019-09-23_18:59:52.47656 160557 ERROR: i2c_transfer: ioctl failed (9: Bad file descriptor, src/i2c.cpp:26)
2019-09-23_18:59:52.48204 160559 ERROR: i2c_transfer: ioctl failed (9: Bad file descriptor, src/i2c.cpp:26)
2019-09-23_18:59:53.18192 161263 ERROR: i2c_transfer: ioctl failed (9: Bad file descriptor, src/i2c.cpp:26)
2019-09-23_18:59:54.18299 162264 ERROR: i2c_transfer: ioctl failed (9: Bad file descriptor, src/i2c.cpp:26)
2019-09-23_18:59:54.96745 163049 ERROR: i2c_transfer: ioctl failed (9: Bad file descriptor, src/i2c.cpp:26)

I’ve also got in yesterdays log a lot of these:

2019-09-22_11:08:57.91872 4067841 ERROR: fused_temp: could not read lid temp sensor (src/sensor_task_peripherals.cpp:397)
2019-09-22_11:08:57.92287 4067852 ERROR: i2c_transfer: ioctl failed (5: Input/output error, src/i2c.cpp:26)
2019-09-22_11:08:57.92863 4067854 ERROR: i2c_transfer: ioctl failed (5: Input/output error, src/i2c.cpp:26)
2019-09-22_11:08:57.92868 4067855 ERROR: i2c_transfer: ioctl failed (5: Input/output error, src/i2c.cpp:26)
2019-09-22_11:08:57.92869 4067855 ERROR: lid_accel_axes: Reading of flags failed with error: 01 (src/accelerometer_axes.tpp:159)
2019-09-22_11:08:57.92871 4067856 ERROR: Lid I2C communication alert (src/hw_task_messages.cpp:318)
2019-09-22_11:08:58.13264 4068063 ERROR: i2c_transfer: ioctl failed (5: Input/output error, src/i2c.cpp:26)
2019-09-22_11:08:58.14491 4068068 ERROR: lid_accel_axes: Reading of flags failed with error: 01 (src/accelerometer_axes.tpp:159)
2019-09-22_11:08:58.14495 4068069 ERROR: Lid I2C communication alert (src/hw_task_messages.cpp:318)
2019-09-22_11:08:58.34331 4068273 ERROR: i2c_transfer: ioctl failed (5: Input/output error, src/i2c.cpp:26)
2019-09-22_11:08:58.37528 4068279 ERROR: lid_accel_axes: Reading of flags failed with error: 01 (src/accelerometer_axes.tpp:159)
2019-09-22_11:08:58.37533 4068279 ERROR: Lid I2C communication alert (src/hw_task_messages.cpp:318)
2019-09-22_11:08:58.51764 4068448 ERROR: i2c_transfer: ioctl failed (5: Input/output error, src/i2c.cpp:26)

again repeated until the end of the log. I think these are from when it has failed to start.

My thanks in advance, any suggestions welcome.

You, my friend, have a communication problem with the lid. The control board talks to accelerometers, lid temperature sensors and the lid camera through an I2C bus. That communication bus runs through the black cable.

Due to a design flaw, the black cable contacts the sharp corner of the metal frame, and eventually breaks. Get Glowforge to send you a new cable, and it will most likely fix your problem.

A possible reason why it is temperature sensitive could be that there is a hairline fracture in the circuit traces on the cable. When it is cool, the cable shrinks and it makes contact. When it warms up, the cable expands and the hairline crack separates, breaking the connection.

3 Likes

Thank you - that was my diagnoses too. Sometimes you just need somebody to confirm your bias :slight_smile:

I’m trying to get a replacement cable shipped to me - instead of shipping the whole damn thing to GF.

Will report back as things progress.

2 Likes

Hey sqw, did you fix your issue ???

I’m a french owner of a GF basic and i met almost the same temperature and cooling issue.
By the way, I can’t afford the 1000 USD shipping fee to send back my machine to the USA for repair.

For my part, this does not seem to be a black cable problem. I inspected it, it seems in perfect condition.

My GF suddenly went into cooling alert and the exhaust fan started running. I let it run for hours without effect. Power off, reboot, leave the machine unplugged for several days, nothing works and the cooling alert persists with the orange button lit constantly.

I just tried again a month later. Everything seemed ok in the homing sequence until you hit the white button for the print. Immediately alert cooling, orange button, fan in continuous function and any command is blocked.
Yet the temperature is 21 ° C (70 ° F).

I printed the log file that reports an error:
2019-10-19_14: 50: 08.52848 428012 INFO: print [79062950]: cut canceled
2019-10-19_14: 50: 08.52851 428012 DEBUG: update_lock: updater lock released
2019-10-19_14: 50: 08.53208 428016 DEBUG: button_led_pulse_timer: setting to 0 ms
2019-10-19_14: 50: 08.83206 428320 ERROR: hw: Coolant monitor temperature alert (src / hw_task_errors.cpp: 168)
2019-10-19_14: 50: 09.52380 429011 DEBUG: HWFSM: event WAKE handled by state not_ready_to_start
2019-10-19_14: 50: 09.83181 429319 ERROR: hw: coolant monitor temperature alert (src / hw_task_errors.cpp: 168)
2019-10-19_14: 50: 10.83206 430320 ERROR: hw: Coolant Monitor Temperature Alert (src / hw_task_errors.cpp: 168)
2019-10-19_14: 50: 11.83215 431320 ERROR: hw: coolant monitor temperature alert (src / hw_task_errors.cpp: 168)
2019-10-19_14: 50: 12.83156 432319 ERROR: hw: coolant monitor temperature alert (src / hw_task_errors.cpp: 168)
2019-10-19_14: 50: 13.83216 433320 ERROR: hw: Coolant monitor temperature alert (src / hw_task_errors.cpp: 168)
2019-10-19_14: 50: 14.52929 434016 INFO: hunt [79063216]: state = ready
2019-10-19_14: 50: 14.54241 434020 INFO: hunt [79063216]: Hardware Not Ready
2019-10-19_14: 50: 14.54245 434022 DEBUG: HWFSM: event WAKE handled by state not_ready_to_start
2019-10-19_14: 50: 14.54247 434022 DEBUG: HWFSM: CANCELLED event handled by state not_ready_to_start
2019-10-19_14: 50: 14.83170 434319 ERROR: hw: Coolant monitor temperature alert (src / hw_task_errors.cpp: 168)
2019-10-19_14: 50: 15.52723 435015 DEBUG: HWFSM: event WAKE handled by state not_ready_to_start
2019-10-19_14: 50: 15.83246 435320 ERROR: hw: Coolant monitor temperature alert (src / hw_task_errors.cpp: 168)

I think there is a problem on the thermal sensor.
GF have said they can’t fix remotely and don’t want to send spare parts at the moment which is detrimental to foreign customers far from the USA.

FYI, I cut vinyl records and this generated a lot of smoke may be toxic for cicuits and embedded electronic parts (GF told me that it was not laser compatible).

If someone has already encountered this kind of problem and, above all, has managed to fix it, I am very interested.

For now my machine is under a blanket in my workshop, not great for the creation (nor a good advertisement for the after sales service of GF)

I like my GF and I want to go on cutting and burning amazing things so please help wanted :wink:

Definitely not the same problem. In my case I pushed them EU 2 year warranty and they agreed to swap it out for a replacement unit. Only cost was I had to pay VAT again, but no shipping etc.

However, cutting vinyl is I understand a complete no no - and has probably filled your GF with hydrochloric acid fumes.

Whether you’ve got a faulty sensor or a wider coolant issue I don’t know.

Best of luck