There is another topic on this but the forum master asked me to start a new one. This is Error 14: Startup line too long.
I think we have a strange intermittent problem. Today I got this error on a program that ran perfectly yesterday. I am running FluidNC on a Jackpot2 running a Primo. I was using the UI web interface on my iPhone. Rebooted the Primo, same error. Ran the program from my Macbook and NO ERROR. I had not changed gcode or names of gcode files. Later tried the iPhone again and still no error.
I am running WebUi version 3.0.0.6.FluidNC. Any other info needed? When I click firmware version (picturre of a cat) I don’t link to anything because I am on a local server (the fluid chip).
Please do not take offense to the request to start your own topic! We are all a great bunch of guys! it helps the other topic stay on topic and also brings more attn to your issue, I am very guilty of passing up conversations that are long running, but i always look at the new ones.
Wish i could help you with this one, but i do not have any thoughts to this. But i am sure someone will be along shortly!
I did not take offence at starting another topic. In fact, I think it is a good idea. I just wanted to explain why I am starting a new topic and refer to the old one.
I will collect the information requested in this chain. Not sure how to get the software version as FluidNC has a link to it but since I am looking at the UI over a local wifi connection the link does not work. Maybe I’m just running downlevel code and if I updated FuidNC, error 14 would go away. I know standard practice is to be sure you are running most recent code before worrying about strange problems.
OK, I went back to the Primo after dinner with my iPhone and, of course, could not get Error 14 no matter how I tried to reproduce the actions I took during the afternoon. But I do have the data a from the $SS command, a picture of the board, and a couple of files that caused the error. Hard to tell how the unit is wired up from the picture but it is exactly according to V1 documentation for the Jackpot 2 board and using all cable and hardware purchased from V1. Except for Error 14 the unit, which has the duel stops on X and Y, is running perfectly.
Ok so i downloaded and opened your code. I was surprised you are using Fusion. I see both files star and end with a percent symbol. I cannot be much help here. I am glad it is now working for you!
After consulting the forums on V1 regarding Fusion, i am using MPCNC v3.0 (Beta 3).cps as the PP – which I think is the latest. Of course it is a beta. I use Fusion for most of my design work and I like it because I often design complex devices which consist of both 3d printed and CNC parts. Some have suggested I use Estlcam and I could import STL files into it from fusion if I don’t want to design in Estlcam. I may do that if I have other problems with fusion.
I don’t know why the files start and end with a % but I can edit them out and see what happens.
When I built the Primo I was a little confused about what level of FluidNC I should get, that is, what is supported by Jackpot 2. I think I could not get the supported version and just got the latest. Am I using the right level of FluidNC?
There arent any levels of FluidNC. Any one of the Jackpot boards all run the exact same firmware. You are good on the JP2.
You cant do any design work in Estlcam. It is strictly CAM work. You can import STL’s if you are wanting to do a 3d carve. But if you are doing flat parts I would suggest exporting a DXF of the part from fusion. That will be much easier to work with in estlcam.
Thanks for confirming my firmware level. I will move my heat sinks. I thought they were awkward on top of the cans. I will fiddle with the Error 14 issue but it is not stoping my work. In fact I finished my first project yesterday and the Primo performed well. I can always go the Estlcam route if I have issues with Fusion. Thanks
All Jackpot boards run the same versions of FluidNC, 3.9.5 is workable. There are newer releases but I wouldn’t mess with that until everything ilse is sorted out- and I’d stay off of the 4.x branch until it has more runtime on it.
One nice thing about V1 machines is since we build it ourselves we can tailor our workflow to meet our individual needs.
Please keep us updated on how your Fusion post processor works for you- there are users who prefer to use Fusion CAD and CAM.
I cannot be certain it is a problem, however if you continue to have problems, please try estlcam or something else. The gcode you published is the same gcode you received therror from?
Yes, I was trying to run those files when I got the error. But only when running the WebUI on my iPhone. When I closed it and ran it on my Macbook I did not get the error. Worse yet, when using the iPhone later I would not get an error for the same files. Maybe the iPhone/macbook thing is a coincidence and we just have a strange intermittent error? In any case, the error is not holding me back and I will just try different things when it returns.
