Topics created by GeneRisi

@GeneRisi feel free to create a feature request at https://github.com/Duet3D/RepRapFirmware/issues with a link to this thread in it.

@chrishamm Chris, I think it is. Thanks!

@chrishamm I discovered the solution. After loading all of the projects, then do a full clean and then quit Eclipse. Restart Eclipse and now the board build options should be available under the Hammer icon.

@droftarts Copy @droftarts

@GeneRisi some of the RAM is allocated dynamically depending on your configuration; so the linker can't tell you that.

When the machine has run for a while, M122 will tell you how much RAM is unused.

@Phaedrux The problem was that I had entered a move in config.g before axis homing. "Insufficient axis homed" seems to leave the machine in a state similar in this case to config.g not existing.

@jay_s_uk Thank you so much for pointing that out! There are a few things that are wrong; I really appreciate your help!

This is closed. Thanks for the help!

Gene

@Behrouz-AKT said in Parameter passing from within a macro:

@fcwilt I am observing the same thing - a string for some odd reason does not work but it should - actually i am trying to do something similar.

Why do you think a string should be working with the current firmware?

Thanks.

Frederick

@GeneRisi i got the same issue
the image is located in the 4th quartile of the frame
8b933ea3-a150-4d06-8632-c7e4aabf6526-image.png

@GeneRisi you can hack on an external wifi antenna to an ESP8266 https://www.hackster.io/simon-vavpotic/esp32-and-esp8266-external-antenna-f28e6b
or you can change the module to an ESP07s

@chrishamm Thanks! That did it!

@fcwilt I don't know. There is underlying housekeeping that the firmware must be doing. The drive mapping could be changed but I don't know whether that would be sufficient.

@dc42 You know better than I do. I thought the processor in the PanelDue and the amount of RAM available made implementing sorting there impractical

@dc42 I found the problem.

When tool T1 was being returned, the Y "parking" coordinate was off by 1 mm. The tool parking location didn't budge but the firmware thought that the tool location was 1mm beyond where it actually was. The machine is a corexy (E3D), so even though only the Y coordinate was off, I suspect it affected both the x and y location from the the firmware's perspective.

@dc42 👍 👍

@generisi Nist doesn't mention Q, this seems to be a good letter.

@dc42 It works like it should. My mistake.

I think this will only be set if you have an 12864 type display attached not a panelDue.