HacDC Wiki - User contributions [en]

Makerbot machines.xml

2011-03-15T00:06:20Z

Jdar:

=== This is important and necessary. ===

After installing replicator-G and running it for the first time, a .replicatorg directory will be created in your home directory (without notification). You'll need to replace the machines.xml file in the secret ~/.replicatorg directory with the following code (or at least add in the part about Andy's Cupcake).

On Windows XP, replicatorG v23 doesn't seem to recognize a machines.xml place in ~/.replicatorg folder. Instead, add Andy's makebot info to the makerbot.xml file, located in the machines folder of your replicatorg install.

On OSX, Instead, add the machines from Andy's makebot info to the cupcake.xml or makerbot.xml file, located in the machines folder of your replicatorg install (/Users/myname/Applications/replicatorg/machines/). Be sure you install ALL the necessary folders into a folder in Applications.)

The machines.xml file describes how the machine is physically set up to replicator-G. The important difference between the Andy's version and the regular version is that Andy replaced the z-axis screws on his bot with better ones. The new screws are great for stability, but they have a different thread pitch from default, resulting in a different height traveled per rotation. The machines.xml file quantifies that travel for the build software.

A new stepper controller was installed on the makerbot. It uses pololu stepper controllers setup in 1/16 microstepping configuration. You will want to use the following block for the machines.xml so the scale values are correct for the 1/16 settings. The changes are made in the <geometry> section of the definition for Andy's cupcake.

1/16 microstepping (4 axis controller)
<pre>
<?xml version="1.1" encoding="utf-8"?>
<machines>

<machine>
<name>3-Axis Simulator</name>
<geometry type="cartesian">
<axis id="x" length="300" maxfeedrate="1000" scale="11.4485"/>
<axis id="y" length="300" maxfeedrate="1000" scale="11.4485"/>
<axis id="z" length="300" maxfeedrate="100" scale="320"/>
</geometry>
<tools>
<tool name="Pinch Wheel Extruder v1.1" type="extruder" material="abs" motor="true" floodcoolant="false" mistcoolant="false" fan="true" valve="false" collet="false" heater="true"/>
</tools>
<clamps></clamps>
<driver name="null"> 
<speedup>20</speedup> 
</driver>
</machine>

<machine>
<name>Andy Walker's Cupcake with 4 axis board</name>
<geometry type="cartesian">
<axis id="x" length="300" maxfeedrate="5000" scale="94.139704"/>
<axis id="y" length="300" maxfeedrate="5000" scale="94.139704"/>
<axis id="z" length="300" maxfeedrate="150" scale="1256"/>
</geometry>
<tools>
<tool name="Pinch Wheel Extruder v1.1a" type="extruder" material="abs" motor="true" floodcoolant="false" mistcoolant="false" fan="true" valve="false" heatedplatform="true" collet="false" heater="true"/>
</tools>
<clamps></clamps>
<driver name="sanguino3g">


<rate>38400</rate>
<parity>8</parity>


<debuglevel>0</debuglevel>
</driver>
<warmup>
</warmup> 
<cooldown>
(Turn off steppers after a build.)
M18
</cooldown>
</machine>
</machines>
</pre>

1/2 microstepping configuration (makerbot stepper controllers)
<pre>
<?xml version="1.1" encoding="utf-8"?>
<machines>

<machine>
<name>3-Axis Simulator</name>
<geometry type="cartesian">
<axis id="x" length="300" maxfeedrate="1000" scale="11.4485"/>
<axis id="y" length="300" maxfeedrate="1000" scale="11.4485"/>
<axis id="z" length="300" maxfeedrate="100" scale="320"/>
</geometry>
<tools>
<tool name="Pinch Wheel Extruder v1.1" type="extruder" material="abs" motor="true" floodcoolant="false" mistcoolant="false" fan="true" valve="false" collet="false" heater="true"/>
</tools>
<clamps></clamps>
<driver name="null"> 
<speedup>20</speedup> 
</driver>
</machine>

<machine>
<name>Andy Walker's Cupcake</name>
<geometry type="cartesian">
<axis id="x" length="300" maxfeedrate="5000" scale="11.767463"/>
<axis id="y" length="300" maxfeedrate="5000" scale="11.767463"/>
<axis id="z" length="300" maxfeedrate="150" scale="157"/>
</geometry>
<tools>
<tool name="Pinch Wheel Extruder v1.1a" type="extruder" material="abs" motor="true" floodcoolant="false" mistcoolant="false" fan="true" valve="false" heatedplatform="true" collet="false" heater="true"/>
</tools>
<clamps></clamps>
<driver name="sanguino3g">


<rate>38400</rate>
<parity>8</parity>


<debuglevel>0</debuglevel>
</driver>
<warmup>
</warmup> 
<cooldown>
(Turn off steppers after a build.)
M18
</cooldown>
</machine>
</machines>
</pre>

[[Category:Makerbot]]
[[Category:Printing]]

BATMAN-Advanced Setup

2011-02-26T23:54:11Z

Jdar: updating with HIGHLY QUESTIONABLE EXPLICITNESS

== Compile and install BATMAN-Advanced ==
Download batman-adv and batctl.
Standard "make && sudo make install".

If no interface "wlan0" exists, check for a different wireless interface using 'ifconfig -a'

== Setup ad-Hoc network ==
# Disable NetworkManager
## Fedora: <pre># /etc/init.d/NetworkManager stop</pre>
## Ubuntu: <pre># stop network-manager</pre>
# Disable the firewall
## <pre># iptables -F</pre>
# <pre># ifconfig wlan0 down</pre>
# <pre># iwconfig wlan0 mode ad-hoc essid hacdc-batman channel 8</pre>
# <pre># ifconfig wlan0 up</pre>

== Setup BATMAN-Advanced ==
In the unpacked 'batman-adv' directory:
# <pre># insmod batman-adv.ko</pre>
# <pre># ./batctl if add wlan0</pre>
# <pre># ifconfig wlan0 mtu 1527</pre>
# <pre># echo bat0 > /sys/class/net/wlan0/batman_adv/mesh_iface</pre>
# <pre># cat /sys/class/net/wlan0/batman_adv/iface_status</pre> Should read "active".
# <pre># ifconfig wlan0 0.0.0.0</pre>???

Byzantium

2011-02-26T01:48:24Z

Jdar:

This project will be launched with a sprint on Feb 25-27, 2011.

Sprint 1

Goal - Reliably bridge two different and separate wireless networks without using existing internet infrastructure.

Design goals
1) There should be a webserver on each network.
2) Nodes in either network should be able to reach both webservers.
3) Nodes on one network should be able to talk to nodes on the other network and vice versa.
4) Networks should have at least 3-5 nodes each.

Tentative schedule is as follows:

Friday - 8:00pm Pizza and planning (any particular request should email me off list).
Saturday - 9:00am Start showing up
Saturday - 10:00am Divide into groups and start the sprint.
Sunday - 9:00am Start showing up.
Sunday - 10:00am Finish the sprint!
Sunday - Evening Debriefing (I'll be taking extensive notes to update the wiki).

Plans!
We're gonna have two teams each will implement a mesh network using some existing mesh protocol. One team will be working with BATMAN and the other with BABEL. Each network will use at least one openwrt device the rest will be laptops and netbooks.

from Wikipedia: [http://en.wikipedia.org/wiki/Byzantine_fault_tolerance#Origin Byzantine]

Byzantium

2011-02-26T00:45:06Z

Jdar:

This project will be launched with a sprint on Feb 25-27, 2011.

Sprint 1

Goal - Reliably bridge two different and separate wireless networks without using existing internet infrastructure.

Design goals
1) There should be a webserver on each network.
2) Nodes in either network should be able to reach both webservers.
3) Nodes on one network should be able to talk to nodes on the other network and vice versa.
4) Networks should have at least 3-5 nodes each.

Tentative schedule is as follows:

Friday - 8:00pm Pizza and planning (any particular request should email me off list).
Saturday - 9:00am Start showing up
Saturday - 10:00am Divide into groups and start the sprint.
Sunday - 9:00am Start showing up.
Sunday - 10:00am Finish the sprint!
Sunday - Evening Debriefing (I'll be taking extensive notes to update the wiki).

from Wikipedia: [http://en.wikipedia.org/wiki/Byzantine_fault_tolerance#Origin Byzantine]

Byzantium

2011-02-16T16:51:22Z

Jdar: initial info about the spring

This project will be launched with a sprint on Feb 25-27, 2011.

Brad will be putting the sprint information on the wiki in the coming days. If people willing to teach could put up information to help novices prepare.

Tentative schedule is as follows:

Friday - 8:00pm Pizza and planning (any particular request should email me off list).
Saturday - 9:00am Start showing up
Saturday - 10:00am Divide into groups and start the sprint.
Sunday - 9:00am Start showing up.
Sunday - 10:00am Finish the sprint!
Sunday - Evening Debriefing (I'll be taking extensive notes to update the wiki).

from Wikipedia: [http://en.wikipedia.org/wiki/Byzantine_fault_tolerance#Origin Byzantine]

Mesh Networking

2011-02-16T16:48:52Z

Jdar:

Meetings Thursdays at 7:30ish starting 10 Feb 2011
=Brainstorming=

==Official Project Page==
[[Byzantium | Byzantium]]

The notes below were used while formulating the project. Further notes available on the now-Ongoing project page.

==Directions==
Which way will we head with this?
*support [[Networking_Strategic_Simulation]]
*community wifi
*cold hard maxout of the current tech
*Development of communication devices with readily available (i.e., cheap) technology.
*Communication technology which lends itself to improvisational construction.

==What Next?==
After we have our direction what are we gonna do?
*define coverage
**building
**block
**neighborhood
**city
**intercity
**regional
**infinite (assuming it will grow with the technology's ability to support it)
*audience - who's gonna use this
*purpose - what will this be used for (surfing the web or just email/twitter/<insert favorite text service here>)
*Use case - circumstances under which this technology will usually be deployed
**ISP/ISP replacement
**disaster
**communication infrastructure failure
**censorship

==Aproaches==
===Mesh===
What will our approach to the network level of the mesh be?
*broadcast
*"actor" oriented - assume no knowledge in other nodes
*nested - roll with what exists and use it to connect seperate traditional nets
*Hybrid
**clients communicate using wifi with hubs
**hubs relay traffic using one of the mesh networking protocols
**IPv6 makes the addressing for this very sensible. address: [1st half highest node "subnet"][further refinement or subnets][last block device id unique within the subnet]

===Extension===
If we need to augment our mesh to cover our target area how will we do that?
*"same stuff but on a larger physical scale"
**mesh nodes with more broadcast power
**some mesh nodes also have point-to-point links with each other
***tight-beam RF
***optical
****laser
****incoherent light
*a higher order traditional network

==Crazy Ideas==
*viral node generation - present captive portals on carriers that require the user to become a "infected" and themselves present captive portals to other non infected devices (zombie smartphone apocalypse)
*make it easy and fun for people to join
**mesh networking app in appstores
**add something fun to make them want to install the app, like a game or a visualization
**as long as they play once in a while, they route traffic (tamagochi effect)
*one-stop shop router reflashing
**flash your Linksys WAP, automatically have mesh networking support active in the background
*TonidoPlug?
*datacomm over
**shortwave
***Note: requires more than two hams to participate
**FRS (been done before but would be an interesting experiment)
**GMRS (been done before but would be an interesting experiment)
**laser pointer with a photocell receiver
**incoherent light [http://ronja.twibright.com/ Ronja]
**Sneakernet with rsync-like functionality (project: mnemonic?)
**Slideshow
**One relatively large video screen
**One relatively decent webcam (not hard)
**Video screen displays sequences of 2D barcodes
**Computer with webcam reads and decodes barcodes
***Reminds me a bit of Conway's Game of Life as a network technology.
*Fidomail-like transfer and synchronization of data bundles
**dialup
**tight-beam datacomm of some kind
**sneakernet (project: mnemonic?)
**Cross-technology implementation
***Web forums
***Microblogs
***Blogs
***BBS software
*Automated sending and decoding of Morse code
**Might not be all that fast but would be easy to implement and fun to test the bandwidth of.
*How could we abuse SMS for this?
*Mobile nodes
**Someone sets up a (small) node in their car and drives around slowly.
**Set up in a backpack or under a coat
***On bicycle
***On rollerblades
***On skateboard
***ON UAV
***On a balloon

=Project=
==Goal==

==Spec==

==Journal==
[[MeshNetworkingMeeting_20110210]]

Mesh Networking

2011-02-16T16:48:09Z

Jdar:

Meetings Thursdays at 7:30ish starting 10 Feb 2011
=Brainstorming=

==Official Project Page==
[Byzantium | Byzantium]

The notes below were used while formulating the project. Further notes available on the now-Ongoing project page.

==Directions==
Which way will we head with this?
*support [[Networking_Strategic_Simulation]]
*community wifi
*cold hard maxout of the current tech
*Development of communication devices with readily available (i.e., cheap) technology.
*Communication technology which lends itself to improvisational construction.

==What Next?==
After we have our direction what are we gonna do?
*define coverage
**building
**block
**neighborhood
**city
**intercity
**regional
**infinite (assuming it will grow with the technology's ability to support it)
*audience - who's gonna use this
*purpose - what will this be used for (surfing the web or just email/twitter/<insert favorite text service here>)
*Use case - circumstances under which this technology will usually be deployed
**ISP/ISP replacement
**disaster
**communication infrastructure failure
**censorship

==Aproaches==
===Mesh===
What will our approach to the network level of the mesh be?
*broadcast
*"actor" oriented - assume no knowledge in other nodes
*nested - roll with what exists and use it to connect seperate traditional nets
*Hybrid
**clients communicate using wifi with hubs
**hubs relay traffic using one of the mesh networking protocols
**IPv6 makes the addressing for this very sensible. address: [1st half highest node "subnet"][further refinement or subnets][last block device id unique within the subnet]

===Extension===
If we need to augment our mesh to cover our target area how will we do that?
*"same stuff but on a larger physical scale"
**mesh nodes with more broadcast power
**some mesh nodes also have point-to-point links with each other
***tight-beam RF
***optical
****laser
****incoherent light
*a higher order traditional network

==Crazy Ideas==
*viral node generation - present captive portals on carriers that require the user to become a "infected" and themselves present captive portals to other non infected devices (zombie smartphone apocalypse)
*make it easy and fun for people to join
**mesh networking app in appstores
**add something fun to make them want to install the app, like a game or a visualization
**as long as they play once in a while, they route traffic (tamagochi effect)
*one-stop shop router reflashing
**flash your Linksys WAP, automatically have mesh networking support active in the background
*TonidoPlug?
*datacomm over
**shortwave
***Note: requires more than two hams to participate
**FRS (been done before but would be an interesting experiment)
**GMRS (been done before but would be an interesting experiment)
**laser pointer with a photocell receiver
**incoherent light [http://ronja.twibright.com/ Ronja]
**Sneakernet with rsync-like functionality (project: mnemonic?)
**Slideshow
**One relatively large video screen
**One relatively decent webcam (not hard)
**Video screen displays sequences of 2D barcodes
**Computer with webcam reads and decodes barcodes
***Reminds me a bit of Conway's Game of Life as a network technology.
*Fidomail-like transfer and synchronization of data bundles
**dialup
**tight-beam datacomm of some kind
**sneakernet (project: mnemonic?)
**Cross-technology implementation
***Web forums
***Microblogs
***Blogs
***BBS software
*Automated sending and decoding of Morse code
**Might not be all that fast but would be easy to implement and fun to test the bandwidth of.
*How could we abuse SMS for this?
*Mobile nodes
**Someone sets up a (small) node in their car and drives around slowly.
**Set up in a backpack or under a coat
***On bicycle
***On rollerblades
***On skateboard
***ON UAV
***On a balloon

=Project=
==Goal==

==Spec==

==Journal==
[[MeshNetworkingMeeting_20110210]]