HELP ! Permanent cooling Alert

I’m a french owner of a GF basic and I met 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 lid black cable problem. I inspected it, it seems in perfect condition and the GF worked perfectly until the “cooling alert”.

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 as soon as the power is on.

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.

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).

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. I’m not under 6 month garanty and I feel myself ready to open the beast and change spare parts (if GF give me a dismounting guide to do it in the right way)

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:

Ouch. Burning PVC creates hydrogen chloride (HCl) which is better known as hydrochloric acid when it is dissolved in water (such as the water vapor in the air). It will have been blown all around the inside of the machine. All sorts of things could be damaged. (And the acid is probably still sitting on everything, continuing to eat through it.)

1 Like