paramite12 wrote:

I've changed settings around, but nothing has helped the random crashes. What a pain in the butt. Any idea when a new version will be out?

Make an issue on RH's Github page. I believe there are a few random crashing bugs on Windows XP.

okay, I'll try that, but I'm using windows 7, so we'll see what happens.

*update* I completely uninstalled and deleted the remnants of repetier host and then installed it again, this appears to have fixed the problem.

I've changed settings around, but nothing has helped the random crashes. What a pain in the butt. Any idea when a new version will be out?

Make an issue on RH's Github page. I believe there are a few random crashing bugs on Windows XP.

Repetier Host 0.85 (the one solidoodle offers) works

Repetier Host 0.90c does not.  Despite all the settings configs matching the other, and it has worked in the past!

Nothing is using the comm, I reinstalled it and reconfigured it and it still doesn't work.

I've also tried every single combination of options in the connection settings area.  Nothing works.  Something is weird about 0.90c on my setup, but I have no idea what it is and why it does not affect 0.85.

Any ideas?

My only suggestions are: DONT drop baud rates - it needs to be 250000 - If it 'fixes' anything its a placebo at best. It isn't the underlying problem, and will cause you mucho grief later with random mysterious print pauses and 'lost' layers...

Your firmware is expecting a baud rate of 250000 - the fact it 'works' at 115200 in older versions is simply a coincidence.

The repetier-host software isn't 'selective' in that if it worked one day, it will continue to work the next. If it doesn't, then something *else* external has effected it. I can say this with some level of certainty because I run 2 different versions, on 3 platforms, across 4 printer controller board types...

What does your Device Manager say about the device when you have it connected ?
Do you have multiple repetier hosts running but minimized (I do this a lot, and it will cause 'non connection' because the com port is already in use ) ?
Do you get errors in Device Manager connecting the device to windows ?
Do you get errors in Event Log about serial comms issues when you try and connect in Repetier-Host ?

You can uninstall everything and try again, including ditching your entries in registry (windows) and preferences list (mac). But your issue sounds more like a simple comms-driver/windows problem... With ONE exception - if you have the New Printrboard clone controller, there *is* an issue with Repetier 0.90, but this was fixed with 0.90B and is a non issue in 0.90C . If you have 0.90C, this is NOT the problem (the printrboard comms issue)

As to MolecularConcepts question: Inside Slic3r Config (not repetier) , go to Help Menu, select 'Check for Updates'.  If you can't see this entry in Help, find your slic3r.ini file, and uncomment the commented entry 'Check for updates=1' or whatever it says specifically - SD in their installers disabled this which means if you first installed their software then you may no longer see the update entry (as subsequent installs will retain your initial .ini config).

For now I guess I'll just have to manually update slic3r inside the old repetier until someone figures out why.  If anyone needs any info, let me know.

how do you manually update slic3r within the old RHost? That's What I originally tried to do...