> new printers will already have the Marlin firmware installed, but if you want to change the firmware yourself then you can follow the Solidoodle instructions...
> On Aug 11, 2012, at 16:15 , Neil Martin <neilj...@gmail.com <javascript:>> > wrote:
> new printers will already have the Marlin firmware installed, but if you > want to change the firmware yourself then you can follow the Solidoodle > instructions...
Comparing the two and configuring the current Marlin for the Solidoodle would be a worthwhile project. The things that would need to be looked at, off the top of my head-
Thermistor table (Should be 1 or 6, the current Marlin says 1 is better)
Heater 0 and Bed heat and Thermistors turned on
Settings related to Y home being at the back of the printer (MAX).
Change #define Y_HOME_DIR -1
To
#define Y_HOME_DIR 1
In pins.h in the sanguinololu section Change
# define Y_MIN_PIN 19 # define Y_MAX_PIN -1
to
#define Y_MIN_PIN -1
#define Y_MAX_PIN 19
Max extruder temp allowed set to 210 to avoid melting the hot end
Motherboard defined as the Sanguinololu, #62 I think
In addition there are the default axis steps, and reducing the default homing speed. Hopefully there aren't other gotchas that will make it simply not work, but I'm expecting at least a little trouble.
On Saturday, August 11, 2012 4:02:29 PM UTC-7, Brandon Fosdick wrote:
> Fixing the thread jacking…
> Would someone mind catching me up on the firmware situation? I'm a bit new > here. At the very least, where do I find this "Marlin" firmware?
> On Aug 11, 2012, at 15:46 , Neil Martin <neilj...@gmail.com <javascript:>> > wrote:
> > I did a diff between the current marlin code and the Solidoodle 2nd Gen > Marlin code to see if they've changed or fixed the homing code. They've > completely rewritten it. The strange thing is, the new version now runs two > completely different pieces of code for "home all" and "home <axis>". > Whereas the older 2nd Gen Marlin code runs the same code wrapped in ifs, > it's simple enough to paste here, so here it is...
> Comparing the two and configuring the current Marlin for the Solidoodle would be a worthwhile project. The things that would need to be looked at, off the top of my head-
> Thermistor table (Should be 1 or 6, the current Marlin says 1 is better)
> Heater 0 and Bed heat and Thermistors turned on
> Settings related to Y home being at the back of the printer (MAX).
> In addition there are the default axis steps, and reducing the default homing speed. Hopefully there aren't other gotchas that will make it simply not work, but I'm expecting at least a little trouble.
> On Saturday, August 11, 2012 4:02:29 PM UTC-7, Brandon Fosdick wrote:
> Fixing the thread jacking…
> Would someone mind catching me up on the firmware situation? I'm a bit new here. At the very least, where do I find this "Marlin" firmware?
> On Aug 11, 2012, at 15:46 , Neil Martin <neilj...@gmail.com> wrote:
> > I did a diff between the current marlin code and the Solidoodle 2nd Gen Marlin code to see if they've changed or fixed the homing code. They've completely rewritten it. The strange thing is, the new version now runs two completely different pieces of code for "home all" and "home <axis>". Whereas the older 2nd Gen Marlin code runs the same code wrapped in ifs, it's simple enough to paste here, so here it is...
The start.gcode is wrong. This is the start.gcode for the Gen 1 Solidoodle which homed Y to the front. Looks like they forgot to update it in the OSX installation. Copy and paste the gcode I posted and see how it goes.
I asked for pictures of the case, and how it covers the back because you seem to be the first person who received one. Everyone else has been told that the cases would be shipped later since they weren't ready yet but they wanted to get the printers out. Would you mind putting yours on and showing it off?
> Does any part of the pulley rub against the plastic mount?
no but the black plastick mount is getting looser the more I test the printer.
> Unfortunately tightening that would involve taking out the pulley with the > belt, and I wouldn't want to mess with that without guidance for getting > the tension right when putting it back on. Does the mount actually pivot > up and down? Does the pulley seem to wobble in relation to the bolt that > it's on?
It wobbles the most when trying to move towards the front. That is when pressing down on the screw (reference the pic) tightens the line and prevents studdering. I don't think I can hold it down for a 2 hour print! Would I void any chance for a return or warranty if I try to tighten the black plastic thing w a hot glue gun?
As for the Gcodes, it's a bit different than yours. Should I my start.Gcode with what you have?
> You should see that at the beginning of the gcode file you created. Try > starting a print with the extruder somewhere in the middle of the bed, > rather than already up against an endstop. It should go right, hit the > endstop, back up and hit it again. The it goes backward and taps the Y > endstop twice before going to the center and tapping the z endstop. Does > it go to the X endstop and then run to the front instead of the back? If > so, does hitting the +Y button cause it to come forward rather than > backward? If you see the printer running willy nilly at a side that > doesn't have an endstop, hit Motors Off before it gets there rather than > let the motors try and force it through the steel frame. It sounds like > either the X and Y motors are plugged in the wrong places on the board, or > the Y motor is wired wrong or something, causing it to turn in the opposite > direction.
> On Saturday, August 11, 2012 3:21:25 PM UTC-7, Ming Hsiung wrote:
>> Hey Ian,
>> So I think I found out why I'm having Z movement problems.
>> This image shows the left side's belt pully thing. It feels like a loose >> tooth compared with the other side. If I hold it still the machine moves >> back better. I can see it wobble if I'm not holding it in place. Perhaps it >> loosened during shipment. >> I also wonder, if the 1 screw holding the pulley isn't directly behind >> the pressure point of the belt, perhaps 2 screws would secure this thing >> better as I'd imagine eventually this would keep loosening.
>> I will keep looking for your blog on start codes via slic3r. a link when >> you have a chance would be awesome. But even if I got the that working, I >> think I have faulty hardware.
> On Saturday, August 11, 2012 3:21:25 PM UTC-7, Ming Hsiung wrote:
>> Hey Ian,
>> So I think I found out why I'm having Z movement problems.
>> This image shows the left side's belt pully thing. It feels like a loose >> tooth compared with the other side. If I hold it still the machine moves >> back better. I can see it wobble if I'm not holding it in place. Perhaps it >> loosened during shipment. >> I also wonder, if the 1 screw holding the pulley isn't directly behind >> the pressure point of the belt, perhaps 2 screws would secure this thing >> better as I'd imagine eventually this would keep loosening.
>> I will keep looking for your blog on start codes via slic3r. a link when >> you have a chance would be awesome. But even if I got the that working, I >> think I have faulty hardware.
copy pasted and will test it out, but my loose tooth issue is gonna get worse. would i be voiding any warranty or return possibility if I tried stablizing it w a hot glue gun?
Try wedging something like a washer between the head of the pulley bolt and the frame. I think that part would be a lot more stable if they used a washer behind the pulley rather than countersinking the bolt into the plastic.
> copy pasted and will test it out, but my loose tooth issue is gonna get worse.
> would i be voiding any warranty or return possibility if I tried stablizing it w a hot glue gun?
there's aprterface-ma-Mar2012 in the skeiforge folder and a pronterface.command in the kliment-Printrun-901023b
each with their own alterations folder. which should I use? One is fancier than the other (showing a graph next to the check temp button. anyways, I updated both gcodes since it was still headed for the front.
the older pronterface is showing a much cooler temp. I will wait for this to heat up and report back. Thanks again for all your help
nice yeah I ended up jamming some gay ass looking paper clips and it's stable! A fitted washer or a cap would be excellent as a part to make... if I CAN ACTUALLY PRINT something :)
So I updated both start.gcodes assuming the apps would be reading them but the second I hit print the nozzle heads to the front. I hit motor off asap but it still runs into the front and jams for a second. Sigh
> i have windows 64 installed on my mac.... I think I will try it from > there. Is the PC side of things more worked out? I don't mind being an > early adopter and all..but I really don't think the mac side is even close > to a minimum viable product.
I run a bootcamped MBP, and tried to set this up on the OSX side as well and gave up very quickly. I wasn't even trying to install the Solidoodle stuff yet, just some other 3D printing software that also runs on Python. It looked like getting Python working right was going to require some research, so I just said to hell with it and moved over to windows for printing related stuff.
On Aug 11, 2012, at 5:53 PM, Ming Hsiung <minghsi...@gmail.com> wrote:
> i have windows 64 installed on my mac.... I think I will try it from there. Is the PC side of things more worked out? I don't mind being an early adopter and all..but I really don't think the mac side is even close to a minimum viable product.
The OS X package is definitely rough around the edges, but it does appear to work after a bit of fiddling. With a bit more polish it shouldn't be so bad.
I suspect that something like this really needs to be a native app. Mac apps are generally expected to be more polished, or at least prettier, and python can only take us so far. At the very least pronterface should use a toolkit that uses native widgets. wxWindows seems to be competing with tcl/tk for some sort of ugliness award.
On Aug 11, 2012, at 18:07 , Ian Johnson <ikelseyjohn...@gmail.com> wrote:
> I run a bootcamped MBP, and tried to set this up on the OSX side as well and gave up very quickly. I wasn't even trying to install the Solidoodle stuff yet, just some other 3D printing software that also runs on Python. It looked like getting Python working right was going to require some research, so I just said to hell with it and moved over to windows for printing related stuff.
> On Aug 11, 2012, at 5:53 PM, Ming Hsiung <minghsi...@gmail.com> wrote:
>> i have windows 64 installed on my mac.... I think I will try it from there. Is the PC side of things more worked out? I don't mind being an early adopter and all..but I really don't think the mac side is even close to a minimum viable product.
On Sat, Aug 11, 2012 at 7:44 PM, Brandon Fosdick <bfosd...@gmail.com> wrote:
> Did the Solidoodle folks forget to fork the project on github? A quick
> search didn't find turn up anything.
> On Aug 11, 2012, at 16:22 , Ian Johnson <ikelseyjohn...@gmail.com> wrote:
> The current Solidoodle firmware is at the Solidoodle web site under How
> To, for How To Update Firmware
> Comparing the two and configuring the current Marlin for the Solidoodle
> would be a worthwhile project. The things that would need to be looked at,
> off the top of my head-
> Thermistor table (Should be 1 or 6, the current Marlin says 1 is better)
> Heater 0 and Bed heat and Thermistors turned on
> Settings related to Y home being at the back of the printer (MAX).
> In addition there are the default axis steps, and reducing the default
> homing speed. Hopefully there aren't other gotchas that will make it
> simply not work, but I'm expecting at least a little trouble.
> On Saturday, August 11, 2012 4:02:29 PM UTC-7, Brandon Fosdick wrote:
>> Fixing the thread jacking…
>> Would someone mind catching me up on the firmware situation? I'm a bit
>> new here. At the very least, where do I find this "Marlin" firmware?
>> On Aug 11, 2012, at 15:46 , Neil Martin <neilj...@gmail.com> wrote:
>> > I did a diff between the current marlin code and the Solidoodle 2nd Gen
>> Marlin code to see if they've changed or fixed the homing code. They've
>> completely rewritten it. The strange thing is, the new version now runs two
>> completely different pieces of code for "home all" and "home <axis>".
>> Whereas the older 2nd Gen Marlin code runs the same code wrapped in ifs,
>> it's simple enough to paste here, so here it is...
Trying to get printer talking to mac os x 10.7.4 --- tried most of the suggestions in here but can't get pronterface to see the printer -- just sits at "Connecting...". What are folks picking for the port?
On Wednesday, August 8, 2012 10:56:49 PM UTC-4, Brandon Fosdick wrote:
> Here are a few quick notes about installing the software on a 2011 Macbook > Pro running Mountain Lion. Overall it's not bad, but anyone who isn't > developer-level familiar with OS X will have problems. What's the best way > to submit documentation changes to Solidoodle?
> The first step mentions installing the unicode package for Python, but > links to the page for wxPython. Playing along anyway, I downloaded the file > and ran the installer, which produced the error message > "wxPython2.8-osx-unicode-universal-py2.7.pkg is damaged and can't be > opened". Turns out you have to have Gatekeeper disabled first. It might be > a good idea to mention that in the instructions because not too many users > know to check for it, or how to disable it.
> Next, I downloaded the Solidoodle Macintosh package. The zip uncompressed > just fine, and install.command did it's thing, although it really should > explain why it's asking for root privileges (or at least mention it in the > instructions).
> Next, I installed wxPython again…why do we need to install it twice? > Again, it might be good to remind everyone that Gatekeeper needs to be > disabled for this step as well.
> Next, I ran pronterface.command, which promptly died while complaining > about wxPython not being installed. I'm pretty sure I just installed it. > Twice. Apparently, wxPython is compiled for 32bit while the Python that > comes installed on Mountain Lion runs in 64bit mode. So, trusting the > internets, I added "export VERSIONER_PYTHON_PREFER_32_BIT=yes" to > pronterface.command and…it worked!
> Hopefully the documentation, and pronterface.command, will be updated soon > so others don't have the same problems.
> That's all for now. I'm off to try my first print. > -Brandon
On Thursday, August 30, 2012 10:27:26 PM UTC-4, John Albano wrote:
> Trying to get printer talking to mac os x 10.7.4 --- tried most of the > suggestions in here but can't get pronterface to see the printer -- just > sits at "Connecting...". What are folks picking for the port?
> On Wednesday, August 8, 2012 10:56:49 PM UTC-4, Brandon Fosdick wrote:
>> Here are a few quick notes about installing the software on a 2011 >> Macbook Pro running Mountain Lion. Overall it's not bad, but anyone who >> isn't developer-level familiar with OS X will have problems. What's the >> best way to submit documentation changes to Solidoodle?
>> The first step mentions installing the unicode package for Python, but >> links to the page for wxPython. Playing along anyway, I downloaded the file >> and ran the installer, which produced the error message >> "wxPython2.8-osx-unicode-universal-py2.7.pkg is damaged and can't be >> opened". Turns out you have to have Gatekeeper disabled first. It might be >> a good idea to mention that in the instructions because not too many users >> know to check for it, or how to disable it.
>> Next, I downloaded the Solidoodle Macintosh package. The zip uncompressed >> just fine, and install.command did it's thing, although it really should >> explain why it's asking for root privileges (or at least mention it in the >> instructions).
>> Next, I installed wxPython again…why do we need to install it twice? >> Again, it might be good to remind everyone that Gatekeeper needs to be >> disabled for this step as well.
>> Next, I ran pronterface.command, which promptly died while complaining >> about wxPython not being installed. I'm pretty sure I just installed it. >> Twice. Apparently, wxPython is compiled for 32bit while the Python that >> comes installed on Mountain Lion runs in 64bit mode. So, trusting the >> internets, I added "export VERSIONER_PYTHON_PREFER_32_BIT=yes" to >> pronterface.command and…it worked!
>> Hopefully the documentation, and pronterface.command, will be updated >> soon so others don't have the same problems.
>> That's all for now. I'm off to try my first print. >> -Brandon
I just for pronterface to connect via port /dev/cu.usbserial-AE01ICD7 in OSX 10.8.1. Per the troubleshooting wiki, I had to change the baud rate to 250000, otherwise I got all kinds of errors, e.g.,
Connecting...
Can't read from printer (disconnected?).
Traceback (most recent call last):
File "/usr/local/lib/wxPython-unicode-2.8.12.1/lib/python2.7/site-packages/wx-2. 8-mac-unicode/wx/_core.py", line 14669, in <lambda>
lambda event: event.callable(*event.args, **event.kw) )
File "/usr/local/lib/wxPython-unicode-2.8.12.1/lib/python2.7/site-packages/wx-2. 8-mac-unicode/wx/_controls.py", line 1843, in AppendText
return _controls_.TextCtrl_AppendText(*args, **kwargs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/enc odings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: invalid continuation byte
Traceback (most recent call last):
File "/usr/local/lib/wxPython-unicode-2.8.12.1/lib/python2.7/site-packages/wx-2. 8-mac-unicode/wx/_core.py", line 14669, in <lambda>
lambda event: event.callable(*event.args, **event.kw) )
File "/usr/local/lib/wxPython-unicode-2.8.12.1/lib/python2.7/site-packages/wx-2. 8-mac-unicode/wx/_controls.py", line 1843, in AppendText
return _controls_.TextCtrl_AppendText(*args, **kwargs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/enc odings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0x98 in position 4: invalid start byte
Traceback (most recent call last):
File "/usr/local/lib/wxPython-unicode-2.8.12.1/lib/python2.7/site-packages/wx-2. 8-mac-unicode/wx/_core.py", line 14669, in <lambda>
lambda event: event.callable(*event.args, **event.kw) )
File "/usr/local/lib/wxPython-unicode-2.8.12.1/lib/python2.7/site-packages/wx-2. 8-mac-unicode/wx/_controls.py", line 1843, in AppendText
return _controls_.TextCtrl_AppendText(*args, **kwargs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/enc odings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xd9 in position 6: invalid continuation byte
On Thursday, August 30, 2012 7:27:26 PM UTC-7, John Albano wrote:
> Trying to get printer talking to mac os x 10.7.4 --- tried most of the > suggestions in here but can't get pronterface to see the printer -- just > sits at "Connecting...". What are folks picking for the port?
> On Wednesday, August 8, 2012 10:56:49 PM UTC-4, Brandon Fosdick wrote:
>> Here are a few quick notes about installing the software on a 2011 >> Macbook Pro running Mountain Lion. Overall it's not bad, but anyone who >> isn't developer-level familiar with OS X will have problems. What's the >> best way to submit documentation changes to Solidoodle?
>> The first step mentions installing the unicode package for Python, but >> links to the page for wxPython. Playing along anyway, I downloaded the file >> and ran the installer, which produced the error message >> "wxPython2.8-osx-unicode-universal-py2.7.pkg is damaged and can't be >> opened". Turns out you have to have Gatekeeper disabled first. It might be >> a good idea to mention that in the instructions because not too many users >> know to check for it, or how to disable it.
>> Next, I downloaded the Solidoodle Macintosh package. The zip uncompressed >> just fine, and install.command did it's thing, although it really should >> explain why it's asking for root privileges (or at least mention it in the >> instructions).
>> Next, I installed wxPython again…why do we need to install it twice? >> Again, it might be good to remind everyone that Gatekeeper needs to be >> disabled for this step as well.
>> Next, I ran pronterface.command, which promptly died while complaining >> about wxPython not being installed. I'm pretty sure I just installed it. >> Twice. Apparently, wxPython is compiled for 32bit while the Python that >> comes installed on Mountain Lion runs in 64bit mode. So, trusting the >> internets, I added "export VERSIONER_PYTHON_PREFER_32_BIT=yes" to >> pronterface.command and…it worked!
>> Hopefully the documentation, and pronterface.command, will be updated >> soon so others don't have the same problems.
>> That's all for now. I'm off to try my first print. >> -Brandon
