I suggest that in the future when you tell someone to Reset, you also tell them to save the configuration in a json file. I lost more hours of time trying to get my machine working again. Also, the problem went away for about 8 cuts and then started up again:
I am trying to make a new spoiler board. It is cut to be smaller than the actual cutting size and positioned inside a rectangle I cut using a v-bit to show the maximum cutting positions. I made the spoiler board 47 3/4 x 31 3/4. I cut all the holes and now want to cut slots. I ran the solt cutting code on a test piece, and it worked perfectly. So I mounted up the new spoiler board and now get nothing but errors.
I will save my config and reset the machine one more time. However, should I be going back to 1.3.1 to avoid these problems?
I am currently running firmware 1.0.9 and I was thinking about upgrading the firmware to the newest version (1.4.0), but I am not sure. It seems like people are having problems with the new version also. Another thing is do I have to download all of the other versions to get the fixes before I go to 1.4.0?
Yes, twice. I have it working now. I made the spoiler board even smaller. So it is about 47.75"x31.75".
I was making a test surface cut and I kept getting way too much surface removed. After checking software and rechecking my methods, I had a thought: What if the probe block is not the same size as the firmware thinks it is. And sure enough, the probe is thinner by around 1mm and shorter on each side by less than 1 mm. Now, when I surface, Iām taking off what I intended.
During this surface test I hit the Stop button (square). I made an adjustment to the Probe settings and went back to run th etest program. It was gone. Deleted. Thatās a bug.
There is a pretty basic defect with the file deletion nobody has listed on this thread. If you have a file uploaded in a folder with the same name as another file in the default folder (and I assume any other folder) it deletes both. This is a pretty basic coding miss. If you are allowing files to be stored in folders the context of a delete should be the file you selected to delete. These are sadly the type of issues that lower our faith in the black box controller updates. While as an original early adopter I still stand behind this controller as it is right for my needs, this type of miss is very disappointing. These are the logic flaws that college students drop letter grades over.
Good to know as I rebuild my entire file library on the controller as the update deleted all my files. Generally I have a unique name for all files CNC (g-code) related as each one serves a unique purpose.
I uploaded a folder from my laptop and it did not show on the controller itself. If we are required to restart the controller to refresh the list that is not useful. I refreshed the screen multiple times. Folder upload also does not work from android and the file drop down displays under the preview adjustment buttons on chrome for android making it unusable to select loaded files.
After you uploaded the folder, do you check the drop down next to it? It should show up. It does for all our tests. If you can upload a video of what you are seeing it will help us.
Sadly I was unable to reproduce it when I tried. I had done some file deletes and other things in between uploading and looking on the controller but canāt reproduce it. If I figure out the pattern I will post it
So is this firmware 32bit or 64bit?
I read through but did not see that mentioned anywhere.
Only asking because I want to get the file/folder features for organization.
I donāt want to update and then when replacing the Rpi 3b to a 4 or 5 have 32bit.
Just updated to 1.4.0. Is there any way to create a folder within a folder? Or are all folders that are created at the same level as the default folder?
