https://reprap.org/mediawiki/api.php?action=feedcontributions&user=Gnomeby&feedformat=atomRepRap - User contributions [en]2024-03-29T10:01:14ZUser contributionsMediaWiki 1.30.0https://reprap.org/mediawiki/index.php?title=Melzi&diff=187159Melzi2019-12-28T05:52:05Z<p>Gnomeby: Spell mistake</p>
<hr />
<div>{{Languages}}<br />
<br />
{{Development<br />
|name = Melzi<br />
|status = working<br />
|image = melzi2.jpg<br />
|description = Release Version 2.0<br />
|author =Joem & Adrianbowyer<br />
|categories = [[:Category:Electronics|Electronics]], [[:Category:Development|Development]], [[:Category:Mendel Development|Mendel Development]] {{tag|8/16-bit board}}<br />
|cadModel = https://github.com/reprappro/melzi<br />
|reprap = Sanguinololu<br />
<br />
}}<br />
<br />
[[Category:Mendel Development]]<br />
[[Category:Electronics development]]<br />
[[category:Melzi]]<br />
<br />
==Introduction==<br />
<br />
A compact all-in-one controller board for RepRaps with one extruder head, optimized for mass production.<br />
<br />
The point of RepRap is to make itself, of course. But sometimes people just want plug-and-play RepRap electronics so they can concentrate on the other aspects of the machine, or just because they are more software or mechanics oriented than electronics oriented.<br />
<br />
Melzi is designed to be a complete set of RepRap electronics that should be very cheap to mass produce. It was originally based on the [http://arduino.cc/blog/2011/09/17/arduino-launches-new-products-in-maker-faire/ Arduino Leonardo] and is named after [http://en.wikipedia.org/wiki/Francesco_Melzi Francesco Melzi], who was Leonardo da Vinci's pupil.<br />
<br />
==Versions==<br />
<br />
Field guide to identifying your Melzi board:<br />
{| class="wikitable"<br />
|-<br />
! Board Name<br />
! ATMEGA mcu<br />
! Stepper Drivers<br />
! Manufacturer<br />
! Year<br />
|-<br />
| RepRap Melzi 2.0<br />
| 1284P<br />
| A4982<br />
| RepRapPro<br />
| 2012-present<br />
|-<br />
| "Melzi 2.0 1284P" (eBay hybrid)<br />
| 1284P<br />
| A4988<br />
| Various eBay vendors<br />
| 2012-present<br />
|-<br />
| Melzi Ardentissimo 1.0<br />
| 644P<br />
| A4988<br />
| RepRapPro<br />
| 2011<br />
|-<br />
|}<br />
<br />
===Melzi Version 1.0 (Ardentissimo)===<br />
<br />
[[File:Melzi-ardentissimo.jpg|1000px]]<br />
<br />
The Melzi V1 used a ATMEGA 644P microcontroller, and 4 x A4988 stepper drivers. However, problems with the routing of the fine tracks on the PCB quickly became apparent, which made them hard to make reliably. Often thermistor readings are inaccurate, or fail.<br />
<br />
BEWARE! Some cheap online sellers still sell this version of the Melzi! See 'How to get it' list lower down this page.<br />
<br />
===Melzi 1.0/2.0 eBay Hybrid ===<br />
<br />
[[File:Melzi V03.jpg|1000px]]<br />
<br />
Most listings online for "Melzi 2.0 1284P" or "Melzi V03" (as above) actually use the 1.0 board schematic, including "Melzi Ardentissimo" lettering and A4988 steppers like the 1.0, but use an ATMEGA 1284P microcontroller like the 2.0. Firmware for the 2.0 will work on these hybrids, however the ADC problems still exist. Some boards register a full 10C less than they should... but only when the printbed is activated, indicating severe EMF and/or power stability problems. As a general rule these boards should not be trusted.<br />
<br />
===Melzi Version 2.0===<br />
<br />
[[File:Melzi2.jpg|1000px]]<br />
<br />
Specification:<br />
<br />
# Processor: ATMEGA1284P ([http://sanguino.cc/ Sanguino] compatible)<br />
# All screw connectors - no soldering<br />
# Micro SD card slot for GCode files<br />
# Mini USB interface<br />
# 4 x A4982 stepper drivers<br />
# 3 x MOSFET drivers for hot end, bed and cooling fan<br />
# Dimensions: 210mm x 50mm x 17mm<br />
# Weight: 70g<br />
<br />
[[File:melzi-circuit.png|1000px]]<br />
<br />
[[File:melzi-pcb.png|1000px]]<br />
<br />
==Source files==<br />
<br />
Version 1.0 of Melzi was developed by [https://github.com/mosfet/melzi Joe Mosfet].<br />
<br />
Version 2.0 of Melzi was developed from Joe Mosfet's original by [http://reprappro.com RepRapPro Ltd]. It can be found at: https://github.com/reprappro/melzi<br />
<br />
==Setting up Melzi==<br />
Most boards are supplied with bootloader and firmware pre-installed and the stepper driver currents preset. If not, read on...<br />
<br />
===Bootloader Upload===<br />
<br />
If the ATMEGA chip on your board is supplied blank or you have had to replace the chip on your Melzi (for example, if you have short circuited the ATMEGA chip), you will need to flash/burn a bootloader onto the chip.<br />
<br />
To replace the Atmel ATMEGA1284P chip on the Melzi, this is the technique RepRapPro uses:<br />
<br />
#Remove old Atmel ATMEGA1284P chip - we find a hot air soldering iron is easiest; be careful not to overheat the crystal that is right next to the chip. You can heat it up in a solder oven, but be careful not to nudge other components.<br />
#Solder on new chip - make sure it is the right way around! Use a flux pen to put plenty of flux on the board first, then solder the chip in place. You can do this with a fine tipped soldering iron, hot air soldering iron, or solder oven.<br />
#Check there are not bridges on the pins with a strong magnifying glass or microscope<br />
<br />
Uploading the bootloader with an AVR programmer:<br />
<br />
#The chip comes blank; you will need to flash/burn a bootloader onto the chip. When it's blank, it can't even talk via USB, only via the In-Circuit Programming (ISP) pins on the board.<br />
#To burn the bootloader, you will need an AVR programmer, like http://www.atmel.com/tools/AVRISPMKII.aspx This is the official one, and quite expensive, but cheaper ones are available on ebay. Check that you get one that is compatible with ATMEGA1284P chip; the USBtinyISP does NOT work with these chips.<br />
#Download the latest version of Arduino IDE software (at time of writing 1.0.5) from http://arduino.cc/en/Main/Software<br />
#Make sure you download the latest 'Sanguino' folder from https://github.com/reprappro/Marlin and put it in your Arduino/hardware folder (there should already be other folders called 'arduino' and 'tools' in this folder)<br />
#Connect the AVR programmer to your PC, via USB. Connect the programmer to the Melzi, via the SPI pins. Connect USB to the Melzi - it needs power from the USB.<br />
#Open Arduino IDE. Under 'Tools | Board' menu, select 'Sanguino W/ATmega1284p 16 mhz'. From the 'Tools | Serial Port' menu, select the port your AVR Programmer is on. From 'Tools | Programmer' select your AVR Programmer type.<br />
#From 'Tools' menu, select 'Burn Bootloader'. You may receive an error; search the internet with the error message to troubleshoot what part isn't working properly. It mostly depends on the AVR Programmer you are using. Of course, there may also be a problem with your board.<br />
<br />
Uploading the bootloader with an Arduino UNO as an In-Circuit-Programmer (ISP):<br />
<br />
#You can burn/flash a bootloader with a Arduino UNO. The first thing is to turn your UNO into an ISP by programming it with the ISP software. <br />
#Download the latest version of Arduino IDE software.<br />
#Open Arduino IDE. Load the ISP software 'File | Examples | ArduinoISP'. Under 'Tools | Board' menu, select 'Arduino UNO'. Select the correct serial port.<br />
#Click on the upload button to transform your Arduino UNO into an ISP programmer. Don't worry, your UNO doesn't have to be an ISP forever; it can be reprogrammed for other purposes at any time.<br />
<br />
Once the Arduino UNO is an ISP programmer, one can connect it to the Melzi board with 4 wires:<br />
<br />
* pin 1 MISO (Melzi) on pin 12 (Arduino)<br />
* pin 3 SCk (Melzi) on pin 13 (Arduino)<br />
* pin 5 Reset(Melzi) on pin 10 (Arduino)<br />
* pin 4 MOSI (Melzi) on pin 11 (Arduino)<br />
<br />
[[File:Arduino as ISP.jpg|200px|thumb]]<br />
<br />
#Connect both Arduino UNO and Melzi board to your PC.(The Melzi board needs power)<br />
#Download the latest 'Sanguino' folder and install it as described above.<br />
#Open Arduino IDE. Under 'Tools | Board' menu, select your card from the Sanguinos listed. If you don't know the card, you can pick one randomly. If you have selected the wrong card, the Arduino UNO will not burn the bootloader and will give you an error.<br />
#From the 'Tools | Serial Port' menu, select the port your Arduino UNO is on. From 'Tools | Programmer' select 'Arduino as ISP'<br />
#If the board you selected previously wasn't the correct board, you will receive an error message saying something like board id 'XX' isn't the right one, where XX is in hexadecimal. If 'XX' is 'ff', double check wires, otherwise try another board type under 'Tools | Board' menu or check on Google the board type with the 'XX' value.<br />
<br />
===Firmware Upload===<br />
<br />
There is a version of the [[Marlin]] RepRap firmware for Melzi on [http://reprappro.com RepRapPro Ltd]'s Github repository [https://github.com/reprappro/Marlin here]. It contains the extra files needed for the [http://arduino.cc Arduino IDE] to talk to a Sanguino (and hence to the Melzi). These also allow you to flash the bootloader using an appropriate programmer.<br />
<br />
There are more detailed firmware instructions on the [https://reprappro.com/documentation/mendel-tricolour/maintenance/ RepRapPro site here].<br />
<br />
As an alternative to the Marlin firmware there's the Repetier firmware for the Melzi which in my case worked better than the Marlin firmware. More details about this firmware can be found [http://www.repetier.com/documentation/repetier-firmware/rf-installation/ here]. There's also a special firmware configuration [http://www.repetier.com/firmware/v092/ tool (v0.92)] with some nice features. If you like Repetier you can [http://www.repetier.com/download-software/ donate] some money.<br />
<br />
====Melzi Arduino Pin Numbers====<br />
<br />
<br />
<pre><br />
#define X_STEP_PIN 15<br />
#define X_DIR_PIN 21<br />
#define X_MIN_PIN 18<br />
<br />
#define Y_STEP_PIN 22<br />
#define Y_DIR_PIN 23<br />
#define Y_MIN_PIN 19<br />
<br />
#define Z_STEP_PIN 3<br />
#define Z_DIR_PIN 2<br />
#define Z_MIN_PIN 20<br />
<br />
#define E0_STEP_PIN 1<br />
#define E0_DIR_PIN 0<br />
<br />
#define LED_PIN 27<br />
<br />
#define FAN_PIN 4 <br />
<br />
#define HEATER_0_PIN 13 // extruder<br />
<br />
#define HEATER_BED_PIN 10 // bed (change to 12 for breakout pin on header)<br />
#define X_ENABLE_PIN 14<br />
#define Y_ENABLE_PIN 14<br />
#define Z_ENABLE_PIN 26<br />
#define E0_ENABLE_PIN 14<br />
<br />
#define TEMP_0_PIN 7 // Analogue pin<br />
#define TEMP_BED_PIN 6 // Analogue pin<br />
#define SDSS 31<br />
<br />
#define SLAVE_CLOCK 16<br />
</pre><br />
<br />
===Setting motor currents===<br />
<br />
This is covered on this page: [[RepRapPro_Setting_Motor_Currents]]<br />
<br />
==Melzi additions==<br />
<br />
===Melzi with Bluetooth===<br />
In order to get rid of the USB connection between Melzi and the PC one may like to use Bluetooth. There is a cheap module available in the market called 'JY-MCU' (vendor Shenzhen Jiayuan Electronic Co.,Ltd.).<br />
<br />
[[File:jy-mcu_f.jpg|300px]] [[File:jy-mcu_b.jpg|300px]]<br />
<br />
====Change setting====<br />
Before the module can be used the baud rate must be changed from default to 115.2k. Connect the module to a PC using a USB<->RS232 (RxD/TxD) interface with default settings (9600, N, 8, 1). The module shouldn't be paired at that moment. Use a terminal program and issue the following AT commands:<br />
<pre><br />
AT OK <br />
AT+BAUD8 OK115200BAUD (set baud rate for Melzi)<br />
AT+NAMEHUXLEY OKsetname (optional set name, default: linvor)<br />
AT+PIN0000 OKsetPIN (optional set pin, default: 1234)<br />
</pre><br />
<br />
More details about the configuration you will find here [[http://apirola.wordpress.com/2012/09/05/setup-jy-mcu-bt-board-v1-2/]]<br />
<br />
====Wiring====<br />
We must level-shift the logic from 5V to 3.3V to communicate with the Bluetooth module. The Melzi has an 4050D IC with unused buffers that we can use. A total of 5 wires must be soldered. Note that the TXD outputs are connected in parallel which is not recommended. On Arduino boards the serial chip is connected to the main IC via 1kOhm resistors for this reason. These are not present in the Melzi board design. <br />
<br />
[[File:BT Connection.png|400px]]<br />
<br />
====Connect via Bluetooth====<br />
Once you have setup your BT devices you can select from drop down list and control your RepRap as usual.<br />
<br />
=== Lcd screen ===<br />
<br />
Gert added an LCD+rotary encoder on his Melzi, here are some [https://plus.google.com/u/0/100131364074868309585/posts/AhGc2hbyW8i pictures]<br />
<br />
A regular text-based LCD can be connected via I2C, as shown on [http://diycrap.blogspot.com/2013/08/i2c-display-and-rotary-encoder-on-melzi.html this blog]. The latest version of Marlin already supports a number of I/O expanders (PCA8574, PCF8574, MCP23017, MCP23008).<br />
<br />
The [[Panelolu2]] LCD+encoder is [http://blog.think3dprint3d.com/2013/03/panelolu2-for-melzi.html designed to work with Melzi] and has an adapter board for easy connection.<br />
<br />
==Melzi Fixes==<br />
<br />
Broke your Melzi? Maybe you can find a fix here (feel free to add your fixes):<br> <br />
<br />
==Twin motor attachment on the Z axis==<br />
<br />
Howto to be determined --[[User:Jobo|Jobo]] ([[User talk:Jobo|talk]]) 14:58, 6 September 2017 (PDT)<br />
<br />
===Mini-USB connector detached from board===<br />
<br />
A repair by Kevin T: http://forums.reprap.org/read.php?4,239276<br />
<br />
===Can't connect to the Melzi (FTDI driver problem)===<br />
<br />
There has been an issue where a FTDI driver update, pushed out through Microsoft update, disables Melzi controllers that have a non-genuine FTDI chip. This chip is used for USB communication, so the board may look like it's working (LED flashing) but doesn't show up correctly, and Arduino IDE/Pronterface can't connect to it.<br />
<br />
This thread describes the problem in detail: http://hackaday.com/2014/10/24/ftdi-screws-up-backs-down/ <br /><br />
Apparently, the only way to visually check the chip is described here: http://hackaday.com/2014/10/24/ftdi-screws-up-backs-down/#comment-2059852 <br /><br />
There is a thread about it on the reprap forums here: http://forums.reprap.org/read.php?1,417199 <br /><br />
There is a work-around for the problem (forcing driver installation, for Windows) here: http://forums.reprap.org/read.php?1,417199,418768#msg-418768<br />
<br />
If the chip has been effected by the driver (ie deemed fake), the device PID is set to '0000'. You can check this in the Mac System Profiler, or on Ubuntu open a terminal window, run "lsusb" and it should show a device at "0403:0000". If you use Ubuntu, there is a tool for resetting the device PID correctly: http://www.minipwner.com/index.php/unbrickftdi000<br />
Then update the FTDI drivers on your machines so it doesn't rebrick the FTDI chip.<br />
<br />
===Melted screw terminals===<br />
<br />
Sometimes, the screw terminals on a Melzi melt. More often than not, it's the bed terminal, and is due to the wire being poorly connected, ie loose in the screw terminal. It can also cause the MOSFET to fail, as it cannot dissipate heat generated as it switches on and off. RepRapPro advises customers to check the screw terminal connections periodically: https://reprappro.com/documentation/mendel-tricolour/maintenance/#Regular_maintenance<br />
<br />
If the Melzi PCB is undamaged, you can simply replace the screw terminal. There are a couple of different screw terminal blocks, these are the most common: <br /><br />
This is the most common one - http://uk.farnell.com/multicomp/mc000048/terminal-block-pcb-5-08mm-2way/dp/2008019 <br /><br />
this one is a bit taller, and easier to get the wires into - http://uk.farnell.com/phoenix-contact/mkdsn2-5-2-5-08/header-pcb-screw-5-08mm-2way/dp/1792766 <br /><br />
<br />
The heated bed power cable carries about 10A at 12V, so any poor connection will tend to heat up. Check that your power and heated bed wires are stripped back far enough to go well into the screw terminals, and it's always worth checking that the screw terminals are well-tightened occasionally. Also, wire the printer with enough slack on the heated bed power wire so that it can be attached to frame, and there shouldn't be any movement of it at the Melzi end. But strain relief on any moving wire is necessary - try to make the movement in the actual wire, rather than at a connection point, to avoid the wire fatiguing.<br />
<br />
===Hotbed or extruder reporting wrong values===<br />
<br />
If your hotbed or extruder are reporting values even when the thermistor is not connected, it may be because the capacitor is spoilt. Try removing the capacitor and replacing it.<br />
<br />
See RepRapPro Mendel/Huxley troubleshooting documentation for other temperature issues [https://reprappro.com/documentation/mendel-tricolour/troubleshooting/#Melzi_temperature_problems HERE]<br />
<br />
===The avrdude errors when flashing firmware ===<br />
The avrdude response is "avrdude: stk500_program_enable(): protocol error, expect=0x14, resp=0x50...)" when I try to flash firmware<br />
<br />
First check that a new serial port appears when you plug the card into your PC.<br />
Then be sure that the microcontroller has been programmed with a bootloader (see 'Bootloader Upload' section).<br />
<br />
=== X axis only moves in one direction and/or Endstops do not work ===<br />
This may be due to bad 644P Fuse Settings.<br />
The settings come from the bootloaders "hardware/arduino/boards.txt" file from sanguino.<br />
Good setting for 644P board are:<br />
<br />
atmega644.bootloader.low_fuses=0xFF<br />
atmega644.bootloader.high_fuses=0xDC<br />
atmega644.bootloader.extended_fuses=0xFD<br />
<br />
Then you need the reburn the bootloader with these settings.<br />
<br />
===Melzi Issues (Geeetech)===<br />
Below is a list of issues encountered with the Geeetech Melzi boards. These boards currently retail for as low as $50 USD (The v2.0 from other manufactures and some Sanguinololu's cost upwards of $80-90). My personal opinion is that the Geeetech boards are inferior, and will cost more in rework/repair/time than if a more expensive controller board were purchased instead (e.g. Melzi 2.0, Sanguinololo, or RAMPS). I purchased 5 of these back in January 2014, have repaired/reworked all of them, and have already replaced/upgraded two with other controllers --[[User:FlyingLotus1983|FlyingLotus1983]] ([[User talk:FlyingLotus1983|talk]]) 19:47, 23 March 2014 (PDT)<br />
<br />
*Random short-circuits on the PCB traces. This is a manufacturing defect that happens to cheap boards that are not electrically tested. For example, one board had a short between the X direction logic signal and ground, which caused the X axis to only move in one direction. Another board had one of the microstepping jumper signal wires shorted to ground, so when I set the jumper (MS1-3), this shorted out the 5V rail to ground, which is very bad and dangerous.<br />
<br />
*The BTEMP and ETEMP resistors (R4 and R5) are the wrong value. The original Melzi was also 10K but changed to 4.7K over two years ago (The Melzi 2.0's use the correct value), however Geeetech is still using the wrong value. This hurts the precision of the thermistor, therefore it is better for to rework and replace with 4.7K than use 10K and change the thermistor tables in the Marlin firmware.<br />
<br />
*The voltage regulator is not capable of 24V input voltage. This is understandable if it was designed this way, but the board should still say somewhere in the documentation "only supports up to 18V input" or something like that. It doesn't. The "fix" for this is to set the jumper ("PWR-SEL") to USB, and also to possibly disable/remove the 7805 voltage regulator. Another fix would be to buy a 7805 that is actually capable of 24V input, from Digikey or another distributer.<br />
<br />
*The MOSFET transistors used will literally let out magic blue smoke if used with a standard Mk2b PCB heated bed wired for 12V. With 12V input voltage, and the Mk2b bed wired for 24V, the bed does not get hot enough to be useful. And when wired for 24V and given 24V input voltage, it does work, but only if an external heatsink is added to the MOSFET. This is very dangerous, and at the very least, the specifications of voltage and current should be disclosed to the user so they can add appropriate external MOSFET or solid-state relay. Obviously, as mentioned before, there are no specs anywhere on what sort of current/power the heated bed circuit can handle. The Geeetech boards do not use the RFP30N06LE's like the original Melzi board spec'd out, so I am unsure of exactly how much current and power it is capable of. Please use caution when hooking up a heated bed to this board.<br />
<br />
*One of the boards resets when the SD card is plugged in. Have not yet gotten around to trying to troubleshoot this one. (This is standard on all Melzi boards, and is because the SD socket shares the reset pin, I think. However, it may be because the SD socket runs on 3.3V, which it gets from the FTDI chip.)<br />
<br />
*The LED is really dim. They should use around 390 ohm for R25 but for some reason they use 1K.<br />
<br />
*The stepper motor trim pots used to set current (T1-T4) are not set to a low value from the factory. If they are not set to something reasonable (say 0.4V) before the stepper motors are plugged in and power applied, the board will get really hot and may be damaged. Instead the board should be powered up at 5V using USB and the voltages at the trim potentiometer wiper should be measured with a DMM, and tweaked until they read 0.4 volts. This should be done for all four trim pots, preferably before shipping to the customer. Since this step is not done, do not forget to do it. They do not come with instructions.<br />
<br />
Please note that after contacting Geeetech, they have issued a product recall for a batch of boards (From 12/2013 to 03/2014).<br />
They have posted on their blog how to get the replacement components. <br />
<br />
They say that "the main problems are the heatbed and extruder thermistors are using resistors that are 10kohms instead of 4.7Kohms. Secondly, The MOSFTEs for the heatbed used the 10N06 which can only take 10A current (now changed to the 35N06).<br />
For customers who are facing the Melzi boards issues, please contact GEEETECH service team via myorder@geeetech.com, and we will ship you the components for replacement free of charge."<br />
<br />
This probably means installing them yourself, but its quite good.<br />
<br />
==== Digikey replacement parts for Geeetech Melzi: ====<br />
<br />
P4.7KECT-ND (4.7 OHM 1/4 Watt resistor)<br />
<br />
IPD035N06L3 GCT-ND (MOSFET N-CH 60V 90A)<br />
<br />
== How to get it ==<br />
[https://reprappro.com/shop/components/melzi-pcb/ RepRapPro] - Melzi V2.0</div>Gnomebyhttps://reprap.org/mediawiki/index.php?title=User_Manual:_Host_Software&diff=185721User Manual: Host Software2019-07-02T15:33:28Z<p>Gnomeby: </p>
<hr />
<div>{{merge to |DriverSoftware}}<br />
<br />
<br />
{{Alternative Toolchain Notice|software|use}}<br />
<br />
<br />
__TOC__<br />
<br />
==Troubleshooting==<br />
*If you are having trouble with any of the axes make sure you check your Cartesian-bot for mechanical problems (friction, alignment) and check to see if your [[Electronics_Hints|Electronics]] are working properly.<br />
<br />
==Setting Host Port Preferences when using Windows==<br />
<br />
To find out which COM port the USB or serial port is using, go to the Windows Control Panel (Start -> Control Panel) and then the Hardware Manager (System -> Hardware -> Device Manager). Scroll down to Ports (COM & LPT) and expand the tree by clicking on the plus sign. There you should see something to the effect of a Communications Port (COM1) and USB Device (COM5). It may not be COM5 on your machine it all depends on how Windows addressed it when you installed the drivers<br />
<br />
Then use search to find the reprap.properties file. Right click and edit. Search for Port(name) and change to match your com number. This must be in caps without spaces. Mine for example is Port(name)=COM4.<br />
<br />
Save the changes.<br />
<br />
An alternate way to update this information is to go into the Reprap program, and edit the Preferences from the GUI: ''RepRap Console=>Print Tab=>Preferences [pink button]=>Globals Tab=>Port(name) [third item, right column]''<br />
and type in '''COM4''' and then scroll to the bottom and click okay. You may need to restart the program to get it to work from there.<br />
<br />
Note: Some Windows users will have this USB-as-a-COM port set up already, others will not. In this case you need to add a FDTI driver, which will create a virtual COM port out of a USB plug. It can be downloaded [http://www.ftdichip.com/Drivers/VCP.htm here] along with install help.<br />
Documented case: Windows XP SP2<br />
<br />
==Setting Host Port Preferences when using Linux==<br />
<br />
Copied from [[http://forums.reprap.org/read.php?12,4546 RepRap forum]]<br />
<br />
The procedure for using the USB adapter from the BOM wasn't in the wiki - nor was it immediately obvious, so, here goes.<br />
<br />
<br />
If you are using the usb -> RS232 adapter, the serial drivers may need to be installed for the device to work properly. After plugging in the device, first check the hardware messages to see the device was detected:<br />
<br />
dmesg<br />
<br />
Torward the end of the messages, you should see this:<br />
<br />
usb 1-1: new full speed USB device using uhci_and address 2<br />
usb 1-1: configuration #1 chosen from 1 choice<br />
<br />
Now, we need to figure out the device vendor number and product number to tell the usbserial driver. For this we can use lsusb. The easiest way to find the information is to first unplug the device, then run lsusb:<br />
<br />
lsusb<br />
<br />
<br />
You will see a summary list of your USB devices on the system, I only have one:<br />
<br />
Bus 001 Device 001: ID 0000:0000<br />
<br />
Now, plug the device back in, and run lsusb again:<br />
<br />
lsusb<br />
<br />
Which returns the summary list again, but now showing the new USB device:<br />
<br />
Bus 001 Device 002: ID 4348:5523<br />
Bus 001 Device 001: ID 0000:0000<br />
<br />
<br />
Now, we can load up the driver for this device:<br />
<br />
sudo modprobe usbserial vendor=0x4348 product=0x5523<br />
<br />
Finally, check dmesg again to ensure it loaded properly.<br />
<br />
dmesg<br />
<br />
Near the end, you should see something like:<br />
<br />
usbserial_generic 1-1:1.0: generic converter detected<br />
usb 1-1: generic converter now attached to ttyUSB0<br />
usbcore: registered new interface driver usbserial_generic<br />
<br />
Congratulations, your link is up - in this example, the device can be used on /dev/ttyUSB0. As much fun as you had doing this, there is some chance you want to do this automatically in the future. Just add this line:<br />
<br />
usbserial vendor=0x4348 product=0x5523<br />
<br />
to /etc/modules with the vendor and product numbers you found. Now, you should have no problem using this device for RepRap like a normal serial port. Huzzah! grinning smiley<br />
<br />
<br />
<br />
If when starting the reprap host software you get this error:<br />
<br />
<pre><br />
DEBUG: Can't open port: /dev/ttyUSB0 - no RepRap attached. [0.122s/9ms]<br />
------------*<br />
</pre><br />
it could be that there is a '''blank space''' in the port preference. Just open the reprap host software, go in the Print tab, press Preferences and remove the trailing blank space from the port name.<br />
<br />
==package org.jdesktop.layout does not exist==<br />
This apparently means Ant or Eclipse or whatever environment you are building from can't find Netbeans. <br />
<br />
To get Ant to work I did the following:<br />
<br />
find / -iname '*swing-layout*jar' 2>/dev/null<br />
<br />
This spits back the location of the netbeans package. For me it was "~/projects/reprap/Reprap/lib/swing-layout-1.0.3.jar".<br />
<br />
Next I opened up ~/projects/reprap/Reprap/build.xml<br />
I then edited the javac element to contain the netbeans package in the classpath:<br />
<br />
<javac source="1.5" target="1.5" destdir="bin"><br />
<src path="src"/><br />
<classpath><br />
<path refid="project.classpath"/><br />
<path location="lib/swing-layout-1.0.3.jar"/><br />
</classpath><br />
</javac><br />
<br />
I'm not sure this is the best way, but it got things working for me.<br />
<br />
<br />
==Using reprap software on ubuntu karmic amd64==<br />
<br />
To install reprap on AMD64 [[Installing RepRap on your computer#Linux AMD64|See Here]]<br />
<br />
<br />
[[Category:Software| ]]</div>Gnomeby