A fan holder is now available to complement Misan’s Another Compact Extruder. More details at Misan’s Another Compact Extruder Fan Holder.
Unclogging a 3D print head is not always an easy task, especially when you lack of the proper tools. They are sometimes hard to find.
To unclog a .35mm J-Head fitted for 1.75 mm filament, I am using a strand of a steel cable and a stake flag. The steel cable strand is small and stiff enough to be inserted in the print head by the tip of it. Its diameter is less than .35 mm. The stake flag provides me a rod that I insert in the filament intake. It is stiff and long enough to push it down to the tip of the print head. Home Depot sells both for less than 4 dollars.
The procedure to unclog the print head is:
- heat the print head to the extrusion temperature of the filament
- remove the filament by reverse extruding it or pulling on it
- push the filament left in the head using the stake flag. Remove the stake flag and remove any filament that sticked to it. Repeat this a few times.
- if the plastic does not go out from the head in a steady flow or the flow is tinier than usual, insert the steel cable strand in the tip of the J-Head and gently pull. Repeat this a few times.
- if the tip of the head is very dirty, gently rub it with a 400 sand paper (very very fine).
You may experience an “Internal server error” on the home page of your site if you are a customer of iPower. You cannot access the home page nor login to WordPress.
Simply edit the php.ini files located in the root directory of WordPress and in the wp-admin subdirectory to fix this issue. If they do not exist, create them. Add a line containing “cgi.force_redirect = Off”, without the double quotes. You will need to update or create these files either using iPower‘s file manager or FTP.
A GCode Analyzer for 3D printing is now available. This on-line tool estimates the amount of filaments required and the cost to print a 3D object. Give the filament type, customize some parameters if needed and upload the GCode files. Dual extrusion is supported. The current version is beta. Click on 3d printing GCode analyzer to give it a spin.
On most Linux distribution, it is impossible to access a serial port (ex. /dev/ttyS0) from a web server such as Apache or lighttpd using a cgi. Simply add the user under which the web server runs (www-data for example) to the group dialout. To do so, use vigr from the command line and add the user on the dialout group line. Such a line will typically look like:
This script lists all the keys on a memcache server.
#!/bin/bash nc localhost 11211 > /tmp/$$.1 <<EOF stats items EOF cut -d: -f2 /tmp/$$.1 | grep -v END | uniq | sed 's/^/stats cachedump /' \ | sed 's/$/ 1000/' > /tmp/$$.2 nc localhost 11211 < /tmp/$$.2 | grep -v '^END' | sort rm /tmp/$$.
The biggest issue when printing 3D ABS objects is warping. As an example, this 8 cm x 8 cm bit holder is badly warped. In this example, 5 mm.
Adding disks (1.5 cm x 1 mm) at each corners prevents warping almost completely. These anti-warping disks can be easily added on the plater of Slic3r. The printing end result printing is shown on the picture below. 1 cm x 0.6 cm disks also works fine.
After trimming the disks, the end result is very good. Warping is less than 0.2 mm.
You can download the OpenScad source file along with some rendered files.
Windows 8 comes with Hyper-V pre-installed. If you want to run Virtual Box, you must completely uninstall Hyper-V through the “Add and Remove Programs” option from the Control Panel. Failing doing so will result in:
- Virtual Box will display error messages when starting up your Virtual Machine
- You will not be able to change the number of processors in Virtual Box
- You virtual machine will run very slowly because of the inability to increase the number of processors
- Hardware acceleration will be disabled
Stopping the Hyper-V service is not enough.
I was not able to reach 110 Celsius with a Prusa PCB Header Bed MK1. My initial installation was with the PCB traces down with a borosilicate glass on top of it. I found out that installing it with the traces up as show below resolved the issue. Nevertheless, the thermistor does not read the real printing area temperature since it is underneath the PCB. There is a 15 Celsius offset and the glass is slightly offsetted. These are small inconveniences. The bed is getting hot pretty fast and is able to reach 110 Celsius.
The G-Code commands supported by Marlin 3D printing firmware are:
|G1||Coordinated Movement X Y Z E|
|G10||retract filament according to settings of M207|
|G11||retract recover filament according to settings of M208|
|G28||Home all Axis|
|G90||Use Absolute Coordinates|
|G91||Use Relative Coordinates|
|G92||Set current position to cordinates given|
|RepRap M Codes|
|M0||Unconditional stop. Wait for user to press a button on the LCD (Only if ULTRA_LCD is enabled)|
|M1||Same as M0|
|M104||Set extruder target temp|
|M105||Read current temp|
|M109||Wait for extruder current temp to reach target temp.|
|M114||Display current position|
|Custom M Codes|
|M17||Enable/Power all stepper motors|
|M18||Disable all stepper motors; same as M84|
|M20||List SD card|
|M21||Init SD card|
|M22||Release SD card|
|M23||Select SD file (M23 filename.g)|
|M24||Start/resume SD print|
|M25||Pause SD print|
|M26||Set SD position in bytes (M26 S12345)|
|M27||Report SD print status|
|M28||Start SD write (M28 filename.g)|
|M29||Stop SD write|
|M30||Delete file from SD (M30 filename.g)|
|M31||Output time since last M109 or SD card start to serial|
|M42||Change pin status via gcode|
|M80||Turn on Power Supply|
|M81||Turn off Power Supply|
|M82||Set E codes absolute (default)|
|M83||Set E codes relative while in Absolute Coordinates (G90) mode|
|M84||Disable steppers until next move, or use S
|M85||Set inactivity shutdown timer with parameter S
|M92||Set axis_steps_per_unit same syntax as G92|
|M114||Output current position to serial port|
|M119||Output Endstop status to serial port|
|M140||Set bed target temp|
|M190||Wait for bed current temp to reach target temp.|
|M200||Set filament diameter|
|M201||Set max acceleration in units/s^2 for print moves (M201 X1000 Y1000)|
|M202||Set max acceleration in units/s^2 for travel moves (M202 X1000 Y1000) Unused in Marlin!!|
|M203||Set maximum feedrate that your machine can sustain (M203 X200 Y200 Z300 E10000) in mm/sec|
|M204||Set default acceleration: S normal moves T filament only moves (M204 S3000 T7000) im mm/sec^2 also sets minimum segment time in ms (B20000) to prevent buffer underruns and M20 minimum feedrate|
|M205||advanced settings: minimum travel speed S=while printing T=travel only, B=minimum segment time X= maximum xy jerk, Z=maximum Z jerk, E=maximum E jerk|
|M206||set additional homeing offset|
|M207||set retract length S[positive mm] F[feedrate mm/sec] Z[additional zlift/hop]|
|M208||set recover=unretract length S[positive mm surplus to the M207 S*] F[feedrate mm/sec]|
|M209||S<1=true/0=false> enable automatic retract detect if the slicer did not support G10/11: every normal extrude-only move will be classified as retract depending on the direction.|
|M240||Trigger a camera to take a photograph|
|M301||Set PID parameters P I and D|
|M302||Allow cold extrudes|
|M303||PID relay autotune S
|M400||Finish all moves|
|M500||stores paramters in EEPROM|
|M501||reads parameters from EEPROM (if you need reset them after you changed them temporarily).|
|M502||reverts to the default “factory settings”. You still need to store them in EEPROM afterwards if you want to.|
|M503||print the current settings (from memory not from eeprom)|
|M999||Restart after being stopped by error|
To know if TRIM is enabled for a particular drive, open “System Profiler” and search for the “TRIM enable” information in the “Serial ATA sub-tree”.
If TRIM is not enabled, the easiest way to enable it is to:
- Download Trim Enabler
- Install “Trim Enabler”
- Run ”Trim Enabler” and enable TRIM
- Power off your computer and power it on again
- Start “System Profiler” and look if TRIM is enabled as described above
Be aware that some SSD does not support TRIM.
It is not obvious to choose and get a 3D printer. There is quite a lot a choices on the market which can be divided in two categories: pre-assembled and kits. Pre-assembled printers are expensive. Kits can be a quite a challenge to assemble as per many testimonials on the web.
I was fortunate enough to attend a 3D printer building workshop given by Voxel Factory. Each participant build his own fully functionnal Prusa Mendel 3D printer in a week-end! Yes, in two days not weeks. Since then, I have printed not only bunnies (I have printed one!) but useful pieces such as filament holders, Raspberry PI plate, Raspberry PI cases, Arduino cases, Dremel tool holders, etc.
If you decide to assemble your own 3D printer, it worth doing it with someone who has experience. 3D printing needs some know how and experience. Expect to see my tricks and tips posted on this blog.
The WiFi USB dongles based on the newest RT5572 chip set do not work out of the box on Ubuntu. Unex DNUR-V72, D-Link DWA-160 Rev B and TP-Link TL-WDN3200 dongles are based on this chipset.
You will need to compile the source code of the driver to make it work. Do not leave this page! This involves only a few easy steps.
1. Save this page’s link. You will have to reboot and come back to it.
2. Un-plug the WiFi USB dongle from your computer.
3. Reboot your computer.
4. Download the driver’s source code from the manufacturer website. Alternatively, you can download a version of this file from this site. Files have been already edited. Steps 9, 10 and 11 are then unnecessary. Note that the filename is slightly different (DPO_RT5572_LinuxSTA_126.96.36.199_20120629_EDITED.tar.bz2.bz2).
5. Open a terminal window.
6. Change to the directory that contains the driver’s source code downloaded previously. For example,
7. Extract the source code. You might need the modify the file name since Mediatek may publish newer source code. For example (there is two bz2 extensions!),
tar xvf DPO_RT5572_LinuxSTA_188.8.131.52_20120629.tar.bz2.bz2
8. Change to the source code directory
9. Edit the file os/linux/config.mk. Set to y the two variables HAS_WPA_SUPPLICANT and HAS_NATIVE_WPA_SUPPLICANT_SUPPORT. Your file shall shows
# Support Wpa_Supplicant # i.e. wpa_supplicant -Dralink HAS_WPA_SUPPLICANT=y # Support Native WpaSupplicant for Network Maganger # i.e. wpa_supplicant -Dwext HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
10. Edit the file os/linux/usb_main_dev.c. Add a line containing MODULE_LICENSE(“GPL”);. This line is important. The position of the line is important. Your file shall shows
MODULE_DESCRIPTION("RT2870 Wireless Lan Linux Driver"); MODULE_LICENSE("GPL"); #ifdef CONFIG_STA_SUPPORT #ifdef MODULE_VERSION
11. Edit the file common/cmm_mac_usb.c and add the lines “#define usb_buffer_alloc(a, b, c, d) usb_alloc_coherent(a, b, c, d)” and “#define usb_buffer_free(a, b, c, d) usb_free_coherent(a, b, c, d)“. The position of the lines is important. Your file shall shows
#ifdef RTMP_MAC_USB #define usb_buffer_alloc(a, b, c, d) usb_alloc_coherent(a, b, c, d) #define usb_buffer_free(a, b, c, d) usb_free_coherent(a, b, c, d) #include "rt_config.h"
12. In the same directory as step #8, compile the driver’s source code. Type the following command:
13. Install the driver. Type the following command:
sudo make install
14. Plug your WiFi USB dongle.
15. After a few seconds, you should see an interface called ra0 if you type the following command:
16. Configure your connection as you would normally do.
It is possible to record a terminal session under Linux with ttyrec. It also records vi, emacs, etc. sessions.
Fisrt, install ttyrec
sudo apt-get install ttyrec
To start recording a session:
To replay a session recording:
A lot of people is having problem setting up a Bluetooth keyboard and mouse on the Raspberry PI. Things get more complicated when your wired keyboard or mouse does not work or prevent your Bluetooth dongle from working. There is hope. This step by step procedure will let you install them or at a minimum let you know what does not work. It uses only the command line interface. It is targeted for the Wheezy Debian distribution.
- First of all, if you already tried to set them up and they do not work, start with a fresh install of the OS. This will rule out anything you have done before that would prevent this procedure from working.
- Plug the Bluetooth dongle directly on the Raspberry PI board.
- Boot the Raspberry PI and connect to it using SSH from another computer if possible. Otherwise, use a wired or wireless keyboard. Logon as pi, password raspberry.
- Switch to root
- Install all the updates. It will take a while.
apt-get update apt-get upgrade
- Enable dbus
update-rc.d -f dbus defaults
- Reconnect as described above. Logon as pi, password raspberry. Switch to root.
- Install the required packages. It will take a while.
apt-get install bluetooth bluez-utils blueman
- Reboot and reconnect as described above. Logon as pi, password raspberry. Switch to root
- Make sure that your Bluetooth dongle is recognized. If not, unplug it and re-plug it.
- Make your Bluetooth device discoverable. Refer to the device manual.
- Make sure that your device is seen by the Raspberry PI. Take note of its MAC address (ex. 75:EF:82:69:D2:83)
- Pair the device. When requested, type a pin like 0000 and hit ENTER. If you are pairing a keyboard, type the PIN you have entered and hit ENTER on the keyboard you are pairing. If you are pairing a mouse, you also need to type a PIN of 0000 when requested and hit ENTER. This PIN might depends on the mouse manufacturer.
bluez-simple-agent hci0 75:EF:82:69:D2:83
- Make the device trusted.
bluez-test-device trusted 75:EF:82:69:D2:83 yes
- Connect the device. After a few seconds, your device will be usable.
bluez-test-input connect 75:EF:82:69:D2:83
- Repeat the steps from “Make your Bluetooth device discoverable” if you need to install another device.
- When you will reboot, the devices will reconnected automatically after a few seconds.
This procedure worked for the following devices:
- Cambridge Radio Bluetooth dongle
- Microsoft Bluetooth Mobile Keyboard 6000
- Apple Bluetooth Keyboard (iPad keyboard)
- HipStreet mini bluetooth keyboard
- RocketFish Bluetooth Mouse
- Razer Orochi Mouse
- iPazzPort Bluetooth (Model KP-810-10BTT)
- Ultra eXo mini keyboard/touchpad
You can initialize your Raspberry PI wireless connection automatically at boot time if the instructions given in a previous post entitled How To Setup A Protected Wireless Connection Via The Command-Line worked. This is pretty straight forward. You must be root to carry out these instructions.
Save the wpa.conf file created in the previous post somewhere on the SD card you use to boot the system. For example in /root/bin/wpa.conf.
Create the following script and save it in a file called /root/bin/initWiFi for example
#!/bin/bash /sbin/wpa_supplicant -Dwext -iwlan0 -cwpa.conf -B /sbin/dhclient wlan0
Protect the files
chmod 700 /root/bin/initWiFi chmod 600 /root/bin/wpa.conf
Add to the file /etc/rc.local before the last exit statement the following line
Setting up a wireless connection via the command line may vary depending on the USB Wireless Interface you are using. These instructions also work for the Raspberry PI running Wheezy. You must be root in order to carry out these instructions.
Make sure that your wireless interface is recognized.
Find your wireless interface name (usually wlan0).
Make sure that your network is visible asssuming the ESSID is broadcasted. Replace wlan0 by you wireless interface name.
iwlist wlan0 scan
iwlist wlan0 scan | grep ESSID
Prepare your wireless configuration file. It will wait for you to type in your wireless network password. Enter your wireless network password an hit ENTER.
wpa_passphrase Replace-with-your-ESSID > wpa.conf
Find out which wireless driver you are using. The drivers are listed in the drivers section. The driver you are using is usually labelled “Linux wireless extensions”. The driver name is most of the time wext.
Initialize the wireless interface. Make sure you replace wpa.conf, wext and wlan0 with the values related to your environment. Some error messages may be displayed. These errors might not prevent your wireless connection from working.
wpa_supplicant -Dwext -iwlan0 -cwpa.conf -B
You can check if your wireless interface is properly initialized.
Issue this command to get an IP address assuming you are using DHCP.
You can install wpa_passphrase and wpa_supplicant is they are not already on your system by issuing the command
apt-get install wpasupplicant