o_lampe, not sure who that comment is directed too? I already have my z-probe hooked up via that pin top, but it is good info for others. I use the machine ground for it.by AK_Eric - Controllers
Quoteo_lampe FYI: I connected the z-probe to "servoPWM3". Don't know if that's the D39 pin? Yep, it is.by AK_Eric - Controllers
Quotedc42 The Pins_RADDS.h file in the source code indicates that there are only 4 active endstop inputs in the RADDS build. If you can tell me the pin numbers of all 6 endstop inputs, I can add the missing ones if those pins are not already used for something else e.g. the Z probe. (going to presume you know this already, but for due diligence) : From this page is this pic: But it has no pinby AK_Eric - Controllers
I got my inductive probe hooked up for bed leveling a while back, been working great. I'm looking to now hook up a simple switch-based out-of-filament sensor. All the reading I've done says I need to hook that switch up to either The E0 or E1 endstop: The E0 endstop is what my inductive probe is hooked to (D39 / E0_AXIS), but I've been unable to find the pin for the E1_AXIS / endstop. Is thisby AK_Eric - Controllers
@o_lampe : Thank's for that info : I currently use the 'Native port' (the one directly under the SD card) for all my work. The 'programming port' (closest to the barrel jack) never seemed to work well for anything. Thanks for the driver, but I'm personally not sure how to install it? I've been doing web searching for such a thing, and haven't come up with anything. Is it something I'd instalby AK_Eric - Controllers
I thought I'd give this upgrade path a shot again: I'm currently on 1.17b. From your github : I copied iapradds.bin to the /sys folder I copied RepRapFirmware-RADDS-1.18alpha2.bin & renamed it to RepRapFirmware-RADDS.bin & RepRapFirmware.bin in the /sys folder I tried issuing a M997 S0 from Simplify 3D (I disabled the M105 calls before hand), Octoprint, and a simple Python script that jby AK_Eric - Controllers
Quotedc42 I have just released RepRapFirmware version 1.17a. There is an untested RADDS build of it at . Remember to follow the link and then press Raw if you want to download it. See for the change list and important upgrade notes. Thanks! Just got it installed without a hitch with successful test print. Feel like I've caught up againby AK_Eric - Controllers
I'm on 1.13a : The only feature I've found missing is the ability to update the firmware off the SD card directly now: I tried to update to Dan's 1.14 port via the SD and M997 S0, but was unsuccessful. I talk about this experience a few pages back. That's the only 'bug' I've found so far. But yah, otherwise I'm really enjoying the firmware, especially with the 5-point bed leveling, it's likeby AK_Eric - Controllers
Thanks for that dc42: I've heard that repeatedly myself... it's slowly staring to sink in Back when I bought my rep1 (5ish years ago now?) I had a 'botstep' fail almost immediately: This made me super paranoid of a board where you couldn't replace them. I had something similar happen on an old Rumba board. But from what I read (and you say) the chance of that happening with a board that hasby AK_Eric - Controllers
Thanks for the info. But since I'm on RADDS, unless Dan finds it in the goodness of his heart to make that firmware port, I'll be sticking with what I got. Beggars can't be choosers, but I'll still beg a little... Maybe a DuetWifi will show up for Christmas....by AK_Eric - Controllers
dc42: per the reprap wiki gcode docs, I saw that you can specify up to 5 points with G30 for Cartesian/core-xy bots, and 7 for delta: Is it possible to specify more for core-xy? And would it help/would you want to? My 5-point setup is working fine (one in each corner, plus the center), but I've learned other firwmare can specify up to 9 (like a grid of 9 points). Also, I'd love feedback on proby AK_Eric - Controllers
My findings: G32 with M557 and no bed.g: READ: Bed equation fits points [49.0, 52.0, 0.794] [49.0, 305.0, 0.635] [299.0, 305.0, 0.203] [299.0, 52.0, 0.552] [149.0, 152.0, 0.655] G32 with bed.g and no M557: READ: Bed equation fits points [49.0, 52.0, 0.798] [49.0, 305.0, 0.639] [299.0, 305.0, 0.205] [299.0, 52.0, 0.555] [149.0, 152.0, 0.657] So only off by a few thousandths. I did it a secondby AK_Eric - Controllers
I'll give it a shot again tonight, and thinking back through my process, I bet your right : I had changed my microstepping from 1/16 to 1/32 during the time I soldered in the header to my radds board: I had forgotten to double my microsteps on the extruder when I was doing my first test, so it was only extruding half as much as it should. I fixed the microsteps at the same time I switched fromby AK_Eric - Controllers
Got help in another forum: Switching the G30's in bed.g to M557's in config.g made all the difference. Properly leveling itself now.by AK_Eric - Controllers
After much work, I've got the bed leveling probe working. It is better than without it. But, it's still not level. I did a before\after comparison with a box the size of my build volume: The back-right corner was too high, nearly causing extrusion to stop. Now, the back right corner looks 'correct', while the rest of my bed is now 'too low', so things aren't sticking quite right. Basically,by AK_Eric - Controllers
Thanks shofman, that confirms what I was thinking, good info!by AK_Eric - Controllers
I'm going to attempt hooking up a LJ12A3-4-Z/BY inductance z-probe proximity sensor. I've read every post on the subject in this thread, whew. I want to use it to do 5-point bed-leveling on my 12" aluminum plate. What I know: * I need to use the PMW3 pin * Most of the gcode/macro stuff. What I don't know: * PMW3 is... 5v... right? The sensor says it needs 6-36v min: This means (I presume) Iby AK_Eric - Controllers
Quotednewman That you got the "Updating main firmware" message means that you had files with the correct names in sys/. However, I've always done this while talking directly to the board over USB without some program which will periodically send commands at the same time to the board. That is, you're using some control software which is also sending other commands to the board at the same timeby AK_Eric - Controllers
Today I thought I try upgrading from 1.13a to 1.14. I followed Dan's steps here: Copied the below RepRapFirmware-1.14-radds.bin file to the sd cards /sys folder, renamed it RepRapFirmware.bin : I placed the iapradds.bin file in the /sys folder as well: After insetting the card I turned on the power supply, plugged in the USB, connected to it, and entered M997 S0 I got this:: SENT: M997by AK_Eric - Controllers
Looks like I'm on 1.13a... and Dan has a version for 1.4 here: Maye I'm SOL for 1.15 since I'm on RADDS, unless Dan finds a buch of spare time laying around. I'll give the manual method a shot!by AK_Eric - Controllers
Pretty sure I'm on that version, but if not I'll upgrade. Thanks for the links, that sounds great.by AK_Eric - Controllers
Thanks for the info DC42! Next question: The relay I had controlling my 12v MakerFarm 12"x12" bed just had a meltdown (literally). After discussion \ research, I just ordered one of these: A nice little board with mosfet, heatsink, plus, PID control. I've been using bang\bang historically. PID on the bed sounds nice. Any suggestions as a starting point for how I should configure my config.gby AK_Eric - Controllers
Random question: Is the concept of 'Z babystepping' possible in RRF? I recently encountered a bed level issue where it would have been really nice to manually tune the z-height during the first layer. Or is something similar available via a custom macro? thanks!by AK_Eric - Controllers
Quoteo_lampe QuoteAK_Eric I have that config right now (well Dan's RAADS port of the dc42 firmware) working successfully. You have to get a special cut of Octoprint for it to work with RRF though, and install a custom Octoprint plugin. I outline this here: Thanks for sharing Eric If I understand it correctly, this dev-version doesn't exactly solve the native_port_problem, but uses the prograby AK_Eric - Controllers
Quoteshofman QuoteAK_Eric I have that config right now (well Dan's RAADS port of the dc42 firmware) working successfully. You have to get a special cut of Octoprint for it to work with RRF though, and install a custom Octoprint plugin. I outline this here: Eric, do you know if Octoprint will upload config files in the future, like the Duet Web interface can do ? I don't know, but based on myby AK_Eric - Controllers
I have that config right now (well Dan's RAADS port of the dc42 firmware) working successfully. You have to get a special cut of Octoprint for it to work with RRF though, and install a custom Octoprint plugin. I outline this here:by AK_Eric - Controllers
I got this working, but not the way I want. This is what looks like happened if I had to venture a guess: * Something went bad with either the endswitch, or wire itself, which initiated this problem around the time I switched to 1.13. * I bought a new endstop, and completely rewired it, making it NC instead of NO. * Regardless of what S0/S1 setting I set in M547, I couldn't get it to detect theby AK_Eric - Controllers
QuoteVDX N/O means, with a broken wire it won't stop ... HA, once it's spelled out it makes a lot more sense, thanksby AK_Eric - Controllers
Quotedc42 QuoteAK_Eric @DC42 : My endstops are 'normally open' microswitches That is a bad idea for repraps in general. I suggest you change the wiring to use the normally closed contacts instead (the outer 2 contacts of the switch), and change S0 to S1 in your M584 command. Also check for a bad connection in the X endstop wiring. Just wondering, but why is N/O bad? But I can give rewiring theby AK_Eric - Controllers
@GroupB : My bot is core-xy, and the build volume and offsets are correct in S3D. Same settings I've used in there for Marlin, Repetier, and now RRF. @DC42 : My endstops are 'normally open' microswitches: If I depress the X-endstop and enter a M119 I get SENT: M119 READ: Endstops - X: at min stop, Y: not stopped, Z: not stopped, Z probe: not stopped And the endstop is definitely hit before anby AK_Eric - Controllers