1

Topic: Can't heat bed and nozzle simultaneously...

I just got my SD3 and I'm using the latest software on the Solidoodle site (0.85b, Windows 7 x64) and when I tell Repetier host to heat the bed, it heats. Or, if I tell it to heat the nozzle, it heats. But if I tell it to heat one and then tell it to heat the other, I get "1 command pending" at the buttom of the screen and the temperature readings stop changing and clicking ANYTHING on the screen makes it freeze up and die. I then have to hard reset the solidoodle and force quit Repetier.

Has anyone heard of this? Any suggestions?

2

Re: Can't heat bed and nozzle simultaneously...

Have you tried re-installing everything from scratch?

3

Re: Can't heat bed and nozzle simultaneously...

This is on a fresh install. I literally got my SD3 a couple of days ago. If I'd had success in the past I would first consider reinstalling the software, but it's a clean installation. Might I be better off going to the latest version of Repetier Host instead of the one from the Solidoodle site?

4

Re: Can't heat bed and nozzle simultaneously...

Will it do other commands like home and move axis more than once or is this just specific to the heating commands?

5

Re: Can't heat bed and nozzle simultaneously...

Yes, it seems fully functional besides this simultaneous heating issue. I actually got the first layer of a print done, but unfortunately it didn't stick to the build platform and I think that's mostly because there wasn't much heat there (that, and the build plate is slightly warped... but that's another issue).

6

Re: Can't heat bed and nozzle simultaneously...

Bump. I can't get the latest version of Repetier host to even connect to the SD3, and the version on the SD website still has this "only one heats at a time" problem... This is a serious defect for a thousand dollar investment...

7

Re: Can't heat bed and nozzle simultaneously...

I guess I should have asked before... does Repetier give any error messages in the log window? and also are the led lights inside the printer dimming/flickering when it freezes?

Could you give us a grab of what the log window is showing from when you first start RH, this might help clear things up smile

8 (edited by browner87 2013-12-08 02:08:37)

Re: Can't heat bed and nozzle simultaneously...

Thank you for the reply! I should have thought to do this first! Find the log below. I connected to the printer. Then clicked the "heat nozzle" button, then clicked the "heat bed" button. After the final line of output, the little progress bar at the bottom of the screen said "1 command waiting", and clicking anything else freezes the program.


21:01:23.170 : ok T:22.5 /0.0 B:22.5 /0.0 @:0 B@:0
21:01:23.171 : N0 M110 *3
21:01:23.172 : N1 M115 *7
21:01:23.174 : N2 T0 *24
21:01:23.176 : N4 M111 S6 *67
21:01:23.180 : ok
21:01:23.181 : N5 M220 S100 *68
21:01:23.182 : N6 M221 S100 *70
21:01:23.182 : FIRMWARE_NAME:Marlin V1; Sprinter/grbl mashup for Printrboard FIRMWARE_URL:http://www.solidoodle.com/how-to-2/how-to-update-firmware/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Solidoodle_3 EXTRUDER_COUNT:1
21:01:23.182 : ok
21:01:23.182 : echo:Active Extruder: 0
21:01:23.182 : ok
21:01:23.183 : N7 M111 S6 *64
21:01:23.184 : ok T:22.5 /0.0 B:22.5 /0.0 @:0 B@:0
21:01:23.184 : ok
21:01:23.186 : ok
21:01:23.186 : ok
21:01:23.186 : ok
21:01:23.195 : ok T:22.5 /0.0 B:22.5 /0.0 @:0 B@:0
21:01:26.252 : ok T:22.5 /0.0 B:22.5 /0.0 @:0 B@:0
21:01:29.314 : ok T:22.5 /0.0 B:22.5 /0.0 @:0 B@:0
21:01:32.369 : ok T:22.5 /0.0 B:22.5 /0.0 @:0 B@:0
21:01:33.522 : N12 M104 S190 *126
21:01:33.524 : ok
21:01:35.425 : ok T:22.5 /190.0 B:22.5 /0.0 @:128 B@:0
21:01:38.486 : ok T:22.5 /190.0 B:22.5 /0.0 @:128 B@:0
21:01:41.544 : ok T:23.8 /190.0 B:22.5 /0.0 @:128 B@:0
21:01:43.922 : N16 M140 S90 *75
21:01:43.925 : ok
21:01:44.598 : ok T:25.9 /190.0 B:22.5 /90.0 @:128 B@:0
21:01:47.661 : ok T:28.4 /190.0 B:22.5 /90.0 @:128 B@:0

EDIT: And no, no noticeable flickering or dimming or anything on the printer...

9 (edited by BoxedWino 2013-12-10 17:00:44)

Re: Can't heat bed and nozzle simultaneously...

I had this exact same issue yesterday, I am using repetier Host on a Mac, it seems like it looses the ability to talk to the port.  I also have it where it will heat up the bed, then the extruder and once both are at the right temperature it freezes and no longer responds with heat updates to the chart.  I moved it to a windows 8 machine and opened up a whole other can of worms with the com port.. :-(

Edited....
Got my window 8.1 pro port issues corrected, but I now have the same sort of issue with this machine.  It heats up and after a certain point it starts queuing messages to the com port and no longer gets info back about the temperature.

10

Re: Can't heat bed and nozzle simultaneously...

My issue seems to be firmware side. When I get the lockup, the program crashes if I try to disconnect and I cannot reconnect to the solidoodle until I hard reset it. Is there a way to downgrade from the Marlin firmware to the old one? I'm thinking that might fix it...

11

Re: Can't heat bed and nozzle simultaneously...

Bump? It's been like a month now and I have to yet to make a successful print thanks to everything peeling after a few minutes of printing from the lack of heat... I've tried hairsparay and I'll be trying a glass bed soon too, but I really want this bed to heat. This is really poor support for a product I've easily spent over $1000 on. It's not like this is an issue of lazy calibration or lack of trying, it's a simple firmware bug!

12

Re: Can't heat bed and nozzle simultaneously...

browner87 wrote:

Bump? It's been like a month now and I have to yet to make a successful print thanks to everything peeling after a few minutes of printing from the lack of heat... I've tried hairsparay and I'll be trying a glass bed soon too, but I really want this bed to heat. This is really poor support for a product I've easily spent over $1000 on. It's not like this is an issue of lazy calibration or lack of trying, it's a simple firmware bug!

Well, no I don't think it's a firmware bug. If it was, it wouldn't be so a rare problem. Everybody gets the same firmware. Unless of course you modified your firmware, or the machine itself. I'm assuming you did not.  When did you get the Solidoodle? Which motherboard does it have? Did you buy it used?

All of this matters.

The Solidoodle has a safety feature that shuts down the machine should there ever be inconsistent temperature readings. This might be what you're experiencing when you talk about having to do a hard restart on the machine.

I don't have much to work with here data wise. I'm curious as to how well you can replicate the problem in question. Are you sure that it is only the situation where both the bed and heater and activated that there is a crash? I think you, and the other fellow in this thread are the only folks who have characterized the problem in this way. My instinct is that there might be more to your situation than what you are characterizing, and that it might be one of our more common problems in another form.

My best guess is that there is something electrically wrong with the machine. If I understand what you are saying correctly, then repetier host crashes, and the board on the Solidoodle needs a restart. If this is the case, my best guess is that something is allowing excessive communication between RH and the SD. I know of no such problem having ever occurred, but let me know list a few of our common failures, and maybe this will give you an idea of what is happening:

----------------------------------------
-Faulty USB

It could be that there is excessive loss of commands between the machine and your computer due to a faulty USB cable. We have seen this before, but it usually manifests as problems connecting. Try another USB cable and another computer.

-Improper voltage from USB

If you are using an un-powered USB hub, you might not be getting the full 5V to the motherboard needed for regular operations. This usually results in the board not working at all.

-Improper voltage from the wall

The machine reacts *very* badly to voltage spikes. This usually results in the machine shutting down. In poorly wired homes this can happen when the Solidoodle is plugged directly into the wall, and another appliance is started close to the Solidoodle. A common story goes "I flipped the light switch in the bathroom and the Solidoodle shut off." This problem occurs a great deal in Australia, as line voltage in Australia tends to fluctuate a bit more than in the U.S and Europe.

-Dead Mosfet

The machine has a low voltage and a high voltage side. One is powered via your USB cable, and the other via the wall. The MOSFETs are little gates that allow wall voltage in to power the hot-end and heating mat. We have had a small number of incidents where mosfets have died prematurely. This has one of two outcomes: Constant heating, or no heating whatsoever. I suppose that if you had an issue with the MOSFET on the board, then it might cause weird issues with heating.

In the error, is the error the same regardless of order of operations? If you heat the bed first, then the nozzle does that change things? vice versa?

-Improper Thermistor Wiring

This is by far the most common electric problem on the Solidoodle. The Thermistor for the hot-end is wired up with several molex clips, and solder points which tend to fail in shipping. What will happen is that the machine will work just fine, and as the machine moves around a small open circuit or short may happen - permanently or for a split second. In either case, the result is almost always the machine shutting off. As I said before, the machine has safety feature that locks the machine in case of a weird temperature reading. If massively high, or massively low temperatures are recorded the machine just shuts off. The multimeter article on the solidoodle wiki (wiki.solidoodle.com) has some information on troubleshooting this. Ensure that there is continuity between the thermistor and the motherboard.

Here's a line from your code:
ok T:22.5 /0.0 B:22.5 /0.0 @:0 B@:0

This should be fine, as the bed shouldn't initiate a crash for 0C.

-dead bed

The beds we use are very cheap (saving passed to you!.) We test them all, but sometimes they experience "premature death." Usually this means no heat, period. How well does your bed heat?

Theory: If your bed heats *very* slowly, perhaps the machine is putting the bed on 100% duty cycle to try and reach your desired temperature. This might happen with a slowly dying bed. I could imagine the control algorithm for the bed spewing commands to raise the temperature, and this causing some problems.

-Improperly applied connections between thermistor/heating elements and motherboard

Both sets of heating elements and thermistors and connecting to the motherboard via a set of wires and molex clips. If these are not crimped and installed correctly, the connection to the motherboard may be intermittent. 

-Misc. electrical issues with the motherboard itself

We do occasionally get factory defective motherboards. They typically only function in "door stop" mode, and therefore do not make it past QA.

-Motherboard overheating

The motherboard is vulnerable to overheating. Keep your house extremely hot? Have your machine in a shed in the southern hemisphere? Perhaps you might want to put a cooling fan on the machine. This can manifest as the machine turning off at weird times. The chips for the stepper motors are most vulnerable to this, and this is where most folks place their cooling fans. Most of these cases seem to come up in Texas and Australia during the summer months. I've never supported anyone with "over cooling" issues, but I suppose there is a lower limit too. 


-------------------------------------------

Here's my advice for what you should do:
1) Go to the Solidoodle Wiki and read up on multimeter testing. Read everything, and test everything.
2) Report anything fishy here.
3) Ponder the failures I described above. Let us know if anything here even *remotely* matches your description
4) Try and reproduce the error. Give us a *step by step* list of the things you did to get the error. Pictures and screenshots from RH are appreciated. Numerical data is appreciated. Videos are appreciated. Temperature graphs are appreciated. Firmware readouts are appreciated. Version numbers for RH, your Operating System, and any other thing you are using on the SD will help a great deal.

Now, I don't know you too well so I don't know what your background is. Chances are that are an engineer. A large percentage of our customer base are Engineers. If you are a mechanical engineer or a software developer, call a buddy who is an electrical engineer. Most EE guys are used to dealing with finicky electrical systems like the ones we talking about here. There may even be a friendly electrical expert on this very forum who can meet with you, and give you a hand. 20 minutes of aimless fiddling may solve a months worth of painstaking tech support couldn't resolve.  Our motherboard is *extremely* finicky. I'll be perfectly honest with you, most of the time we get a weird electrical error like this, our repair guys can get the machine working in seconds - it's usually a loose wire or something else that might be "un-fixed" in shipping. 

Also, there is most likely a hackerspace close to where you live, where a friendly 3D printer aficionado likely resides. He may be able to apply the requisite fiddling to get the machine up and running.

I'm not trying to pass the buck here, but talking to a local friend might be faster than what we can do from Brooklyn.

As for the firmware, I wont totally dismiss the chance that the firmware is to blame. You could have changed the firmware, or received a weird version of it (not accusing, I just don't know!), or had some other weirder incident happen. We have resources on both our main website (www.solidoodle.com) and wiki.solidoodle.com that help you out with the firmware. If you received your Solidoodle in the last 2-3 months, you received our latest firmware build, which should work perfectly fine. It is exactly what everyone else has. By your readout, I assume this to be the case.

If you are determined to re-flash your firmware, I should caution you: It is tricky. Non software developers tend to stumble with it. Read the directions *very* carefully. This is *not* like updating the firmware on your phone. For all Solidoodles, the most sure-fire way is to use an AVR programming cable. You should be able to flash without it using USB, but the cable makes things fool-proof. If you decide to go this route, please be patient and read the directions very carefully. It is normal for the process to fail on the first try.

If you have an older machine, or a used machine and you put the latest SD3 firmware on it, that might be your problem but I somewhat doubt it. There is community firmware that better supports the old machines than our official branch does, but none of the changes between the two effects the heating bed/nozzle in the way you describe.

Also, you might want to try using RH on a different machine. Are you on mac? The mac version is a little wonky. SD does not make RH, and RH has never been super up to date on the mac. The best operating system to use in Windows 7.

--------------------------------------------------
As for us the company:

1) Have you contacted SD support? If you have a truly broken machine we're almost always ready to replace the parts or the whole machine. We can't guarantee we can do it fast, but we will do it if the machine is broken due to us. This may be the case. Did they get you what you needed? Were you properly taken care of? I'll make the right calls if you think you were dealt the wrong cards by tech support.

Again: How long have you had the machine? Did you buy it used?

We are far less able to help if you bought the machine second hand.

2) As for the quality of our parts, I understand your frustration. As you can see from what I wrote above, supporting these machines can be challenging. Right now, we are trying to shove a lot into a product that *could* cost two or three times what it costs. If it is any solace, most 3D printers have issues of this ilk. Heating systems in 3D printers are temperamental and cheap parts in them do not help that quality.

We try to make up for that by replacing any factory defective part. We can't avoid some of the complexities of maintenance and usage (and neither can many of our competitors, by the way.) However, we are determined to help you through the process the best we can.

One thing that makes many of our users happy is that the Solidoodle is a *very* sturdy frame for modifications. You can often replace some of the more temperamental parts with more reliable (and expensive) counterparts for far less than it would have cost to buy an equivalent machine.

-------------------------------

I hope something I said in here helps. I understand you are frustrated.

What can we do to help?

Former Solidoodle employee, no longer associated with the company.

13

Re: Can't heat bed and nozzle simultaneously...

Thank you sir for the wall of text (no sarcasm - I love detail). When I am home again I will investigate each item you mentioned further. I spent a year in EE before moving over into Computer Engineering. I have extensive experience with Pic microprocessors, but unfortunately none with AVR. My logic behind a firmware failure is that the board falls to communicate with the PC after the bug occurs. The heating continues (the bed and nozzle reach the set temperatures), but Windows (7, x64) can't communicate with the device without resetting the Solidoodle motherboard manually. In my experience, this is a device side malfunction. I will do some more electrical diagnostics and report back, with a video if possible.

14

Re: Can't heat bed and nozzle simultaneously...

I think it only reads out commands by priority 1 at a time. I know when I turn both on bed stays heating while extruder cycles in readout.
moves lineup by 1st come 1st done commands and say how many pending execution. I dont think you have any problems just how readout handles command/G-code lines. takes a while to get accustom to how it works. wait til ya start making slicer settings lol thats another learning curve. just hang in there it will come together and ask others if ya come to another baffling situation ;^)

I turn bed on 1st then extruder when bed is close to temp setting so extruder dont sit hot waiting for bed temp b4 starting print so filament dont ooz so much.

when you do extra slicer settings save them with new name b4 closing dont overwrite default settings. you will need them again. I already have over 12 settings saved to select from. have fun!

Solidoodle 2 with Deluxe kit cover & glass bed with heater. and 2nd board SD2 used not 3rd and alum platform not installed yet still wood. also need cooling fan installed to board. use Repetier Host couple vers. Slic3r also have all free ware STL programs

15

Re: Can't heat bed and nozzle simultaneously...

bump. I just got this same problem when swapping my SD3 to a windows 7 x64 machine. if I heat either my print bed or extruder I get the command pending issue and the heat readout stops updating. The printer works fine on my xp machine.

16

Re: Can't heat bed and nozzle simultaneously...

Hmmmm... really? I'll try mine on my laptop that is xp this week and see if it works. If so then there clearly is a driver issue. I can try a few os's and both architectures in vms if so to weed out the problem smile

17

Re: Can't heat bed and nozzle simultaneously...

I do believe there is either a driver compatibility issue or bug in the firmware somewhere in the chain of various processes things have to go through to print. My SD3 has been 100% reliable right up to a recent reinstall of the software, now I get the same problem of the connection randomly dropping. It usually happens just after startup when prepping for the first print, at first I thought it was the newer release of Slic3r I installed so I rolled back to what should be a stable version and it still happens.

The "fix" in my case is to disconnect Repetier, unplug the USB cable, plug it back in, and restart Repetier. It occasionally takes 2 or 3 repetitions of this process before everything settles down and I can print although I've also had it die on the second or third layer even when it does print. Eventually it works if I keep repeating the cycle.

Also, it's not isolated to just the SD3. I have a small Delta printer that runs from a different laptop on Repetier. This is a recent scratch build running a Ramps 1.4 and I have similar problems trying to print through the host computer. If I generate the Gcode, put it on an SD card and print directly from the SD card via the LCD panel it works just fine. Everything on the host side seems fine also as I can load STL files and generate Gcode as well as change the configuration used when printing, it just doesn't want to keep communication going between printer and host. I've swapped USB cables on both with others I have on hand and it doesn't seem to make any difference so I'm leaning towards it not being a hardware issue, at least in my case.

Conclusion is something has become broken in the USB communication piece between printer(s) and host computers. Problem is there are too many pieces in the chain, Repetier, Slic3r, native OS, 3rd party USB driver, Marlin firmware, etc. an update to any one of these can potentially cause issues.

My day job is a systems engineer in the computer industry so I see things like this more often than I care to, problem is I don't have sufficient time to sit down and methodically work my way through the entire chain to see exactly where the problem is occurring, best I can come up with at the moment is that it's in the USB communication between host and printer and may have something to do with a recent update to one of the pieces of software since the SD3 worked just fine before I reinstalled everything on the primary computer. It does the same thing when running from the laptop that controls the Delta which is a new install also as I just finished building the machine in the last week.

18

Re: Can't heat bed and nozzle simultaneously...

I seem to have narrowed down the problem I'm having. I disabled all non-essential processes and services on the primary laptop, checked all the settings in Repetier and fired up the SD3. Some things I found before starting the printer, in the Windows registry there is a section where Repetier keeps all its settings, in my case I had two versions of Rep installed and there was what appeared to be some conflicting entries resulting in having connected the same version to 2 different printers without creating full configurations for both, my bad for trying to save time by cutting corners on the way to getting a print started.

I also found the receive cache buffer size set to 127 and in Rep there is a note that after Arduino 1 the default setting is now 63. Don't know if this had anything at all to do with it but I made sure to change it from 127 to 63 and save it.

Right now the SD is an hour into a 3 1/2 hour print job and so far no problem, knock on wood...

I think my problem is likely a case of too much "stuff" loaded on one computer, I have a number of configuration and setup apps for Atmel processor based devices and virtually all of them use USB communication. Somewhere along the line from when I initially installed the Repetier software to the reinstall I most likely installed something else that doesn't play nice with it in USB communication. With most everything else not running and a reboot before starting to print things seem to be back to normal, when this print finishes I'll have to restart all the things that aren't running and see if the communication problem comes back.

19 (edited by browner87 2014-01-25 23:27:46)

Re: Can't heat bed and nozzle simultaneously...

Unfortunately my problem is still 100% repeatable. I pulled out my old XPS laptop with Windows XP 32-bit and made a fresh install with repetier host. No problems whatsoever - levelled the bed with a new piece of glass, home'd the axis, etc. Heating the nozzle? Fine. Tell it to heat the bed now too? "1 command waiting". Device locks up, repetier host locks up, hard reset for everything. In fact any attempt to heat the bed, in any order of operations freezes it now it seems. Faulty bed heater? Faulty sensor?

I swear this board is faulty. There is no way a communications problem this repeatable across multiple PCs has to do with anything else...

EDIT: Also note that the bed does continue heating after locking up.

20

Re: Can't heat bed and nozzle simultaneously...

have you tried calling Solidoodle yet?  sounds like its time if you havent already.

21

Re: Can't heat bed and nozzle simultaneously...

I have yet to find a phone number for them, but I did find an email and I've just started that process. If it solves anything, I'll post back here smile

22

Re: Can't heat bed and nozzle simultaneously...

you can also get ahold of them on skype or IRC ---> http://www.solidoodle.com/contact/

23

Re: Can't heat bed and nozzle simultaneously...

For anyone reading in future - the constant machine "crashing" was due to a bad power supply. Also, the new power supply sent to me ONLY works when hooked to a UPS - apparently my wall outlet power isn't good enough.

24

Re: Can't heat bed and nozzle simultaneously...

browner87 wrote:

For anyone reading in future - the constant machine "crashing" was due to a bad power supply. Also, the new power supply sent to me ONLY works when hooked to a UPS - apparently my wall outlet power isn't good enough.

That sounds shady. Much more likely the replacement power supply has electrical issues than the wall outlet.  Especially if you try another section of your house.

Some of these cheap power supplies cause crazy noise fed back into the outlets. I don't really understand how it works.

25

Re: Can't heat bed and nozzle simultaneously...

browner87 wrote:

For anyone reading in future - the constant machine "crashing" was due to a bad power supply. Also, the new power supply sent to me ONLY works when hooked to a UPS - apparently my wall outlet power isn't good enough.

That sounds shady. Much more likely the replacement power supply has electrical issues than the wall outlet.  Especially if you try another section of your house.

Some of these cheap power supplies cause crazy noise fed back into the outlets. I don't really understand how it works.

UPS would somehow be isolating the problems.