You are not logged in. Please login or register.
SoliForum - 3D Printing Community → Help/Repair/Maintenance → Serial Driver Problem
I need to temporarily use a different computer to run my SD2.
I have installed the serial driver and RH per Solidoodle's web site. All software installed using administrator account.
When I try to connect to the SD2, RH shows the following error:
Serial com error:System.IO.Ports.SerialErrorReceivedEventArgs
I could really use some help diagnosing and fixing this as it will be several weeks until I can get back to my regular computer.
Thanks,
Nick
I have installed the serial driver and RH per Solidoodle's web site.
you mean USB driver?
you might not be connecting to the correct port... when i switched from win7 to winXP, I have to try every single port until I got the correct port... there are about 20 ports from RH's port list.
Thanks for trying. No, I have the correct comm port selected. My SD2 makes a soft sound when connecting (stepper motors?) I hear that sound. Also, there are only two comm ports on the computer being used.
Win7 says the driver/device is working. It shows the driver is from FTDI and that is correct.
I've also tried two different computers: same error.
Nick
It's worth checking that your baud rate is correct too: 115200
In Repeatier go to Setting -> Baud rate
The serial port is configured by the SD config file to: 115200 baud, 1 stop bit, parity none, autodetect transfer protocol.
Nick
nfhill wrote:I have installed the serial driver and RH per Solidoodle's web site.
you mean USB driver?
you might not be connecting to the correct port... when i switched from win7 to winXP, I have to try every single port until I got the correct port... there are about 20 ports from RH's port list.
For the record, you should go into device manager of windows. Under the "ports" section you can see a "serial usb" device, and that's your printer. Next time you won't need to try all of the ports 
You can also look at what ports are available before you plug in the printer, and then look at what ports are available after you plug in the printer and refresh. The new one is the printer!
I'm sorry I don't have a useful answer for the OP though
I'm sorry I don't have a useful answer for the OP though
Me too!
I'm pretty sure the problem is with the driver installation. I just can't think of any way to install it that I haven't tried.
Nick
Oh, well, there are a good amount of ways to incorrectly install the drivers. Recently windows has been trying to autoinstall arduino drivers, which is new in the last two months for them to do so, but it never does it correctly.
What is the port that is "correctly" working called? Is it called Serial USB comm or just USB comm port? The first is I believe what it should be.
Can you uninstall them? Then reinstall by choosing to install files from a local location, and "have disk" and then direct it to the folder in arduino with the .inf files.
For the record, you should go into device manager of windows. Under the "ports" section you can see a "serial usb" device, and that's your printer. Next time you won't need to try all of the ports
everything is listed as usb , you can't tell one from the other. that's why i HAVE to try all of them.
that's just how windows xp rolls, plus it was too slow to slice anything... so i stopped using it.
Oh, well, there are a good amount of ways to incorrectly install the drivers. Recently windows has been trying to autoinstall arduino drivers, which is new in the last two months for them to do so, but it never does it correctly.
What is the port that is "correctly" working called? Is it called Serial USB comm or just USB comm port? The first is I believe what it should be.
Can you uninstall them? Then reinstall by choosing to install files from a local location, and "have disk" and then direct it to the folder in arduino with the .inf files.
I've installed from local location, as administrator, from administrator account. I've run the installer from FTDIchip.com both by running it after download (run not save), downloaded, saved, and then run. I've used the installer from SD. I've tried both the new driver (Aug 1 2013) and the one dated July 2013.
I've tried a different USB cable.
In device manager, it shows as "USB Serial Port (Com6)" and it indicates all is working as it should. In Devices and Printers is shows as a mouse. That shouldn't be a problem as I've run other FTDI adapters OK that have been shown as mouse.
I'm completely stumped!
Nick
Have you tried resetting your sanguinololu a few times right before connecting? [using the button on the back]
I need to do this for my setup, but the thing is that the error I have when I don't do this is just that repetier has 7 commands waiting forever.
And, have you tried uninstalling and reinstalling repetier?
I've reset the SD controller multiple times. I've uninstalled and reinstalled RH multiple times. I've even installed the newer version of RH from the RH website (the one from SD is one rev old now). I get the same error with all variations.
Nick
I need to clarify, have you reset the SD controller *right before trying to connect to it*? I'm not talking nanosecond, but I'm saying within a second of hitting reset. I keep one hand on the mouse to click repetier connect, one on my sanguinololu reset button (gray button on the controller).
Tomek, what you're suggesting doesn't make sense to me, but I will try anything. I've reset the SD controller immediately before clicking connect on RH and reset the SD controller shortly after clicking connect. The result is the same error and no usable connection.
That technique shouldn't be required. Fortunately I will go home again in several weeks and my regular computer should still function ok.
Before this this thread dies, I would like to thank all that have tried to help.
Nick
Tomek's method is a work around that is only necessary when windows has problems and is not working properly to recognize the interface.
Stubbornness pays off!!
I decided to try other things than the driver. I re-flashed the SD firmware: no improvement.
In idle desperation, I decided to try all the baud rate options. At a baud rate of 250000, communication was established! I don't know why that baud rate, but since it works, I'm using it!
Of course, because I re-flashed the SD firmware I have to recalibrate everything. That is made worse because some of the settings in the RH files, as downloaded from SD's website, are wildly off. For Christ's sake, the filament diameter was set to 3mm!! But, at least it's working again!!
Thanks to everyone for helping!
Nick
250000 is the default baud rate the SD is supposed to run at.. I guess I should have looked at your previous posts... I see you mention you set it at 115K... oh well
250000 is the default baud rate the SD is supposed to run at.. I guess I should have looked at your previous posts... I see you mention you set it at 115K... oh well
Yea, my bad. Somehow my firmware had 115200 set, and I needed them to be in sync. I've updated the firmware and am on board with 250000, pun intended.
Thanks for setting me straight.
When I downloaded RH from SD's web site, the included configuration files had the baud rate set to 115200 so I assumed that was the correct value. It was only later that I noticed other values were incorrect.
Nick
You guys are saints. Thank you for the info!
I was updating from an original SD2 to the new Marlin FW and was a few steps away from pulling my hair out. The Baud rate thing I figured might be somewhere in the instructions.
SoliForum - 3D Printing Community → Help/Repair/Maintenance → Serial Driver Problem
Powered by PunBB, supported by Informer Technologies, Inc.
