# Parsing error appeared after firmware update

**URL:** <https://klipper.discourse.group/t/parsing-error-appeared-after-firmware-update/10645>\
**Category:** General Discussion\
**Created:** [September 23, 2023, 6:34pm UTC](https://klipper.discourse.group/t/parsing-error-appeared-after-firmware-update/10645 "2023-09-23T18:34:36Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonawald](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@jonawald](https://klipper.discourse.group/u/jonawald)\
**Post date:** [September 23, 2023, 6:34pm UTC](https://klipper.discourse.group/t/parsing-error-appeared-after-firmware-update/10645/1 "2023-09-23T18:34:36Z")

</div>

### Basic Information:

TRONXY X5SA  
 MCU / Printerboard: cxy-v6-191121  
Klippy.log  
[klippy (1).log](https://klipper.discourse.group/uploads/short-url/cCP39OSPNo09hIfZBLXmJfreF1c.log) (1.7 KB)

After updating Klipper via Fluid/system/updates, I get a weird parsing error that was not there before. Can anybody help me resolve this?  
The error is related to the PFPTouch sensor I printed and installed[PFPTouch](https://www.thingiverse.com/thing:2890290)

I am also having issues with temperature configuration on the Triangle labs Volcano hotend I installed. After some tinkering, I discovered that at normal temperatures this sensor reads over 500°.

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [September 23, 2023, 6:46pm UTC](https://klipper.discourse.group/t/parsing-error-appeared-after-firmware-update/10645/2 "2023-09-23T18:46:21Z")

</div>

Please attach your printer.cfg

---

<div class="post-metadata">

**Author:** ![jonawald](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@jonawald](https://klipper.discourse.group/u/jonawald)\
**Post date:** [September 26, 2023, 1:50pm UTC](https://klipper.discourse.group/t/parsing-error-appeared-after-firmware-update/10645/3 "2023-09-26T13:50:22Z")

</div>

Sorry, I thought that was included the clippy log. Here you go.

Here is the error I get.

File contains parsing errors: /home/pi/klipper\_config/printer.cfg  
[line 195]: ‘G4 P300\n’

Jonathan  
[printerCFG.cfg](https://klipper.discourse.group/uploads/short-url/A8vyj7KZht1vIfZYwkbWZC9xGOC.cfg) (3.6 KB)

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [September 26, 2023, 2:44pm UTC](https://klipper.discourse.group/t/parsing-error-appeared-after-firmware-update/10645/4 "2023-09-26T14:44:44Z")

</div>

![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/3/31e16e22425a5fcaa8bad7f9ac79abd0afd46232.png)

Correct this misplaced indention

![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/c/cedda5eb124323c5e3aff9f0cd0426ae2190f219.png)

Add the missing indention on the marked items

> [@jonawald](#):
>
> Sorry, I thought that was included the clippy log. Here you go.

Yes, you are right, but in case of a parsing error, we need to see the original file to assess which might cause a parsing error.

---

<div class="post-metadata">

**Author:** ![jonawald](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@jonawald](https://klipper.discourse.group/u/jonawald)\
**Post date:** [October 7, 2023, 11:47pm UTC](https://klipper.discourse.group/t/parsing-error-appeared-after-firmware-update/10645/5 "2023-10-07T23:47:07Z")

</div>

Thanks by the way. This worked for me.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [December 6, 2023, 11:47pm UTC](https://klipper.discourse.group/t/parsing-error-appeared-after-firmware-update/10645/6 "2023-12-06T23:47:09Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
