# M4 Large NC files **URL:** \ **Category:** Troubleshooting\ **Created:** [June 1, 2024, 2:16pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319 "2024-06-01T14:16:46Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![tryon](https://avatars.discourse-cdn.com/v4/letter/t/57b2e6/32.png) [@tryon](https://forums.maslowcnc.com/u/tryon)\ **Post date:** [June 1, 2024, 2:16pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319/1 "2024-06-01T14:16:46Z")
I was attempting to run a job that has two files, one is 2.5 mb and the other is 3.6 mb, when uploading them I get the you are disconnected message: ![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/2/f/2fe2a4079f4ea1fe86ad676502931aa1e5519ac5.png) After reloading I can see the files uploaded to the board. If I select the larger one and most of the time when I select the smaller one it will also give me that timeout message, but a moment later i can see that the cut paths have loaded as they are displayed. ![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/a/3/a360882a68d3420c2b91f74646afb8bdea045e4b.jpeg) I have not had time to dive into the code much but it seems like this is related to some missed heartbeats since the esp or browser is probably processing the NC code and misses a few beats. Perhaps we should have it double-check if the other has come back after throwing that error that communications have recovered. Since the NC file is on the maslow, can I just run them directly from the FluidNC side? ---
**Author:** ![ronlawrence3](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/ronlawrence3/32/7886_2.png) [@ronlawrence3](https://forums.maslowcnc.com/u/ronlawrence3)\ **Post date:** [June 1, 2024, 3:05pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319/2 "2024-06-01T15:05:50Z")
> [@tryon](#): > > seems like this is related to some missed heartbeats Yep, that timeout is tied to “pings” coming to the web ui from maslow (on a websocket, that also supplies the “serial messages”) and is currently hardcoded to 20 seconds. I would think we could bump this up or make it user configurable or even turn it off during the gcode loading process… It is possible that the code sending the gcode to the browser is neglecting sending these “ping” messages during the transmission to the browser. What sort of device are you running the web browser on? How long after the message pops up do you see the gcode appear? I may be able to get you a quick html.gz that has a longer timeout if you want or show you how to build one yourself. ---
**Author:** ![ronlawrence3](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/ronlawrence3/32/7886_2.png) [@ronlawrence3](https://forums.maslowcnc.com/u/ronlawrence3)\ **Post date:** [June 1, 2024, 3:46pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319/3 "2024-06-01T15:46:38Z")
> [@ronlawrence3](#): > > I may be able to get you a quick html.gz that has a longer timeout if you want or show you how to build one yourself. Actually, it looks like the preferences dialog has support for turning this “connection monitoring” off that has been hidden. I turned it back on here locally and it seems to work: ![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/b/3/b33b951b9fec2fa372bf8058a70adb5632f49c1a.png) ![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/8/d/8dfecbbe80d08b8a56655b4f84a835cd65e947b9.png) I’ll get a pull request in today to Bar to include this option again, and I’ll see if I can see anything quick that can make this more reliable on load of large gcode files. ---
**Author:** ![ronlawrence3](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/ronlawrence3/32/7886_2.png) [@ronlawrence3](https://forums.maslowcnc.com/u/ronlawrence3)\ **Post date:** [June 1, 2024, 3:49pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319/4 "2024-06-01T15:49:06Z")
> [@ronlawrence3](#): > > pull request in today to Bar > > > @BarbourSmith > > Allow user to unset enable\_ping for large gcode file loads... > … > > see https://forums.maslowcnc.com/t/m4-large-nc-files/21319 ---
**Author:** ![ronlawrence3](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/ronlawrence3/32/7886_2.png) [@ronlawrence3](https://forums.maslowcnc.com/u/ronlawrence3)\ **Post date:** [June 1, 2024, 3:52pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319/5 "2024-06-01T15:52:20Z")
Here is an index.html.gz I built from this branch if you want to try it: [index.html.gz](https://forums.maslowcnc.com/uploads/short-url/6wNUrNRZ2hMa7QLaSiuNzrGYE22.gz) (158.7 KB) ---
**Author:** ![tryon](https://avatars.discourse-cdn.com/v4/letter/t/57b2e6/32.png) [@tryon](https://forums.maslowcnc.com/u/tryon)\ **Post date:** [June 1, 2024, 4:11pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319/6 "2024-06-01T16:11:23Z")
This is from the .75 release branch, correct? ---
**Author:** ![ronlawrence3](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/ronlawrence3/32/7886_2.png) [@ronlawrence3](https://forums.maslowcnc.com/u/ronlawrence3)\ **Post date:** [June 1, 2024, 4:12pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319/7 "2024-06-01T16:12:18Z")
correct ---
**Author:** ![tryon](https://avatars.discourse-cdn.com/v4/letter/t/57b2e6/32.png) [@tryon](https://forums.maslowcnc.com/u/tryon)\ **Post date:** [June 1, 2024, 4:46pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319/8 "2024-06-01T16:46:21Z")
Using that HTML and turning off the monitoring allows me to upload and select either NC file without an issue. Thanks Ron! Watching the network traffic it seems like it takes close to 30 seconds to send the file to the Maslow ![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/4/0/4090e26de8badd1d3999d7f133c624bc19383c9d.png) and when you select it, the Maslow takes another 21 seconds to send it back. ![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/1/b/1be3abd0ca3104e4e0010ba438a22a87128c1bae.png) This is a good patch, I think would be better if we could find a solution so you don’t have to turn that monitor off when loading large files. ---
**Author:** ![ronlawrence3](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/ronlawrence3/32/7886_2.png) [@ronlawrence3](https://forums.maslowcnc.com/u/ronlawrence3)\ **Post date:** [June 1, 2024, 6:08pm UTC](https://forums.maslowcnc.com/t/m4-large-nc-files/21319/9 "2024-06-01T18:08:50Z")
> [@tryon](#): > > I think would be better if we could find a solution so you don’t have to turn that monitor off when loading large files. I agree. I’ll put an issue in for it so we don’t lose it on the “TODO” list