Auto squaring and end stops

Ya sure i can do that when i get a chance. No worries on the hijack, no two better people to hijack a thread lol

I did some more detailed testing, and this is what I found.

If you power on the machine in the middle somewhere, and try to move into the negative space, it will in the Z and not in X, Y. I found that with the LCD or the computer (I was using pronterface, I hope that isn’t making a difference).

If I go into the positive somewhere, and issue a G92 X0 Y0 Z0, it will then go negative, but not more than the original 0. For example:

G01 X1 Y1 Z1
G92 X0 Y0 Z0
G01 X-1 Y-1 Z-1 ; OK
G01 Z-2 ; OK, because of that setting
G01 X-2 Y-2 ; Doesn’t go there.

I was using the buttons to move around, mostly. I assume that these, and RH’s buttons are both just sending the G01 commands.

I’m surprised it has any concept of machine coordinates or home coordinates.

Another thing I noticed is that the ā€œresetā€ button in pronterface wouldn’t always reset it, but if it showed the vicious logo, then it was actually reset.

If you are still finding the problem, can you paste or email me a .zip and maybe a gcode file that illustrates the problem? Some gcode snippets are fine too. It’s just more specific than english.

I think it is fine, no one should be manually moving negative after using a touch plate and it works with gcode so perfecto. The new firmware has it set.

So the bug fix 2.0 is fully functional and the one I want? As Ryan said I don’t care about manually moving negative in x and y as long as I can home all the way at any given point.Goina try this tonight.

Mine should be, I edited and tested a bunch last night and have been doing it all day so it should be good but you know me, far from perfect the first time, every time.

Ok great I’ll let you know how it works out…here’s a picture of the finished map sign in the video…I think the only other project picture I have posted here was the test map… what’s with me and maps your thinking?..I swear I don’t just set around cutting them all the time lol

558672B5-10A3-4896-AB53-E630FBDEDF17.jpeg

Looks awesome, adding it to the gallery.

1 Like

That looks great. I think Hawaii and Alaska are in the wrong place though.

It looks really good though. Just wrong. :slight_smile:

I’m just glad he got the whole state! Most people forget to add the sliver that includes the state capitol…

Just now getting around to trying the new firmware. I get the following message when i try to compile it:

Arduino: 1.8.4 (Windows 7), Board: ā€œArduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)ā€

fork/exec C:\Program Files\Arduino\hardware\tools\avr/bin/avr-gcc.exe: The filename or extension is too long.
Error compiling for board Arduino/Genuino Mega or Mega 2560.

This report would have more information with
ā€œShow verbose output during compilationā€
option enabled in File -> Preferences.

 

I notice it looks completely different in file explorer from the other firmware i have compiled. Meaning the others where not broke into folders and were just a big list of files with the .ino somewhere in the middle. This new firmware has everything in folders and i am only finding a .ino file under the ā€œmarlinā€ folder. Maybe i did something wrong with github?? I downloaded both of the ones that specify for ramps and duel end stops and tried them. If you show ā€œVerbose outputā€ it instantly hits this file location and keeps looping until it errors out. I’m guessing this is a dumb mistake on my part. I have a feeling its something simple i’m just not familiar with. Is there a step i’m missing before pulling it into Arduino? Thanks for your help.

 

Andy

So, in addition to getting dual endstops, this firmware is 2.0. So your getting a lot of new changes at once. One of them is the new folder structure.

I see on the Arduinos website that 1.8.5 is available. I’m guessing that is the problem. Marlin is jumping ahead of Arduino sometimes, so I think with this version, you really need the bleeding edge.

If it still fails, follow their advice and show the full error. It will at least tell you what file name is too long.

This error is why I wanted to see if you could compile it. Originally I could not.

2 fixes to try. First is Arduino beta to see if they have sorted out the long file structure issue, second is move the marlin folder to a root folder of your driver preferably a different drive.

For me it compiles file if I do if from my backup drive D:/MArlin, It didn’t work when I tried it on my home drive c:/marlin.

The issues is something to do with the temp folder and the added file depth goes over the arduino limit. I knew it was an issue but I wanted to see if it was fixed or there was an easy workaround. Arduino will address it eventually, I do not think Marlin has any intentions on a fix and this might be the very reason they have not committed to V2 yet.

If you can not get it to compile/build, you can turn off the LCD in the firmware and it will compile.

At the same time Andy this is a new build for you, I highly recommend you do not use the dual endstops right now. The only real reason for them is multiple process jobs and at first you probably should not be attempting that yet, you have cut perimeters to figure out first and throwing in a very new firmware feature on top of that could really make for a hard time. I still have not used it for a real cut yet, I have had some other matters come up since posting the PR news.

Ok…Ryan I think you may have me confused with another user with that second post. I have been using the original dual end stop firmware for a while…it’s great besides the soft end stop issue I ran into.

 

Thanks,

Andy

Most of the marlin devs are using PlatformIO instead of arduino now - so in the 2.0 branch especially things are breaking on Arduino and not getting patched up right away. At least until they officially release 2.0 it’s probably best to use PlatformIO to build it instead of Arduino - or be ready for issues.

The long filename issue one they’re aware of and working on. I haven’t followed ALL of the details but basically It’s due to a major change with the library they use to talk to the LCD’s. The version of the library they use hasn’t been updated for a long time as it’s developer has moved on to a newer version and abandoned the version Marlin relies on…but with the move to 32bit Marlin needed some major changes to the library. So they just created an internal fork of that library with the changes they need to get it working on 32bit boards.

There’s been a bunch of discussion in various issues on their github account about it this weekend but I haven’t been able to keep up with them all because my wife was out of town and I had to try and keep my 7 year old daughter occupied all by myself. Which meant I had precious little time to myself and the time I did have I was too exhausted to do much :smiley:

2.0 is pretty exciting…but right now it’s a bit of a mess with a lot of changes going on and things breaking VERY regularly. So if you’re looking to build from source it’s probably better to stick with a 1.x build or be ready for things to blow up and take a few days to get working again…possibly longer if you’re using Arduino instead of PlatformIO.

 

Hello,

Looking at getting a MPCNC kit (hopefully before christmas) and would like to ā€œfutureproofā€ it. I just want to make sure I have the stuff for the end stops if the times comes and I want to add this. From what I have read all I need are 4 limit switches and 4 end caps? Is this still the case? If so where can I find the end caps? I woudl assume I need end stop plugs as well?

It looks like there is an option to get this in the shop but it is currently unavailable. Any idea when this will be available? Also it says that it comes with the wiring kit. Is that required in addition to the 4 limit switches?

Side question. Is there a good general purpose bit that would be good to get for milling/routing?

Thank you!

You need a board that can support it (I offer the full sized rambo), end stops (rambo comes with 3 you will need another), a wire for the extra switch (I have one in the misc section that requires splicing). For the moment that is what I have to get that rolling. Most recent orders stick with the series kit and add the straight wires for later. Best not to try and learn them both at once.

Not sure what you are referring to with ā€œend capsā€?

Everything mentioned above is in stock, If you could give me a link I can verify.

You chose series wiring (normal) or or straight (dual endstop). As I mentioned above most new comers are just ordering the extra wires for later on. Again, comes with three if you get the rambo and needs another limit switch, unless you want them all to match (aesthetics) then get four.

The single flute kyocera I have in the shop, by far.