Sudo Room - User contributions [en]

Giant robot arm

2026-10-04T07:57:33Z

Jerkey:

<big>Yaskawa Motoman K10S</big>

[[File:Robot typing its name on a laptop.jpeg|750px|left|typing on a laptop]]
[[File:Robot_teasing_korl.jpg|thumb|right|robot in sudoroom]]
[[File:Giantrobot-getting.jpg|thumb|humans bringing the robot to sudoroom]]
[[File:Giant_robot_arm_where_it_came_from.jpg|thumb|as it was found]]
[[File:Robot_axes.jpg|robot axes and their directions]]
[[File:Robot home position.png|250px|robot homed position pose]]
[[File:SudoRoom Robot Art Painter!.png|thumb|You can even make the robot arm paint for you!]]
[[File:PXL 20261004 075250470.jpg|thumb| schematic capture of motor controller power board]]

= videos by Wade Bourne
* [https://spaz.org/~jake/robot/wadevids/robot%20draws%20a%20circle%20in%20a%20square.mp4 robot draws a circle in a square.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20redraws%20a%20circle%20in%20a%20square.mp4 robot redraws a circle in a square.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20types%20hello%20world%20on%20a%20laptop.mp4 robot types hello world on a laptop.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20typing%20its%20name%20on%20a%20laptop.mp4 robot typing its name on a laptop.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20writes%20hello.mp4 robot writes hello.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20writes%20hello%20backwards.mp4 robot writes hello backwards.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20carves%20a%20piece%20of%20foam.mp4 CAUTION: LOUD robot carves a piece of foam.mp4]

= what is it for? =

It's a six-axis CNC machine that is rated to move 10 kilograms around in any orientation, with 1mm accuracy.

= software for communicating with the robot from a regular computer =

[https://github.com/wbourne0/yasnac software written in Go by Wade Bourne]

[https://github.com/jerkey/yasnac software written by several people for working with the robot]

Use motofile and motocommand while the REMOTE button on the robot is lit up. To enable the REMOTE button, you must [https://sudoroom.org/wiki/Giant_robot_arm#enabling_relative_job_function_and_the_communications_option enable remote operation] first

Your computer must be connected to the robot over an [https://sudoroom.org/mediawiki/index.php?title=Giant_robot_arm&action=submit#Serial_port_pinout_to_connect_to_a_regular_PC_(DTE)_9-pin_socket RS232 serial cable]. [https://github.com/jerkey/yasnac/blob/master/remote/motofile motofile] lets you send job files to the robot, and [https://github.com/jerkey/yasnac/blob/master/remote/motocommand motocommand] lets you tell the robot what to do, as if you were pressing buttons on the control panels. [https://github.com/jerkey/yasnac/blob/master/remote/motomove motomove] can move the robot directly (without loading a job file) but it is poorly supported in the robot's firmware and was never considered complete by the manufacturer (they moved onto the MRC control system development for this) so use it with caution.

= documentation =
* [https://spaz.org/~jake/robot/479950-3-Programming_manual_v4-ocr.pdf programming manual] (searchable thanks to OCR)
* Homing https://pdfcoffee.com/erc-homing-pdf-free.html
* Collection of docs http://spaz.org/~jake/robot
* [http://spaz.org/~jake/robot/155493-INFORM-LANGUAGE.pdf INFORM Lanugage manual PDF] and another copy here [http://www.ro.feri.uni-mb.si/predmeti/robotizacija/inform.pdf INFORM PDF]
* [http://www.robot-forum.com/robotforum/yaskawa-motoman-robot-forum/motoman-k6sb-with-erc-controller/ Robotforum posts on the Yaskawa motoman k6sb with erc controller] ''talk to these people for the conversation''
* [https://spaz.org/~jake/robot/CACR-SR15SZ1SDY214-SERVOPACK-YASKAWA-MANUAL.pdf a modern replacement for the motor controllers] (aka a much more readable PDF about these motor drivers)
* [https://spaz.org/~jake/robot/CACR-SR-BB1.pdf an original PDF manual for the motor controllers] (but actually searchable thanks to OCR)

= enabling relative job function and the communications option =

Ben says:

"If I remember, press OP2, enter the magic code 24.#4.#2 then set these:

set SD079 to 1 for relative job (x,y,z coordinates)

set SD110 to 1 for data communication (remote mode)

and reboot the robot."

= Getting the robot working if it has forgotten its purpose =
* There is a battery inside the connector compartment of the robot arm, and another next to the computer boards on the door of the control cabinet. If the batteries go dead or are disconnected, the robot will act stupid and refuse to boot up with some dumb error screen like this:
<code>
ERROR NO. ERROR STATUS
SV1: 1 00 0000_0000
2 00 0000_0000
3 01 0000_0001
SV2: 1 00 0000_0000
2 00 0000_0000
3 05 0000_0010
SV3: 1 00 0000_0000
2 00 0000_0000
3 00 0000_0000
SV4: 1 00 0000_0000
2 00 0000_0000
3 00 0000_0000
</code>
This probably means the battery in the robot arm itself (behind the connectors) is dead. You might have to short Batt0 to RESET for 30 minutes or something before putting in a new battery and re-homing?
https://www.robot-forum.com/robotforum/thread/20910-motoman-yasnac-erc-k6sb1-make-abs-data-error/

* Homing https://pdfcoffee.com/erc-homing-pdf-free.html basically, pose the robot as shown above, press OP2, press 0 eight times, ENTER, and then you can tell it that it's presently homed. You can also home fewer than all axes by selecting which axes you want to home, before pressing the button for "Setting" which is how you tell it to save the present position. As of 2022/12/7 the absolute encoder values for SLURBT are: 5771,30829,-25795,-792,66,-1047. IF the physical limit switch (for example on the S axis) is hit, you have to HOLD the "overrun" bypass button next to the serial port while booting up and CAREFULLY jogging S- or S+ to fix that problem, and then you can let go of the button.
* There is a switch inside the control cabinet on the edge of the CPU1 card which puts it into [https://spaz.org/~jake/pix/2022-05/20220531_205509.jpg MAINT mode (switch up)] or [https://spaz.org/~jake/pix/2022-05/20220531_213820.jpg PARAM mode (switch down)], normally the switch is in the middle. Hard-power cycling the robot is how you reboot it. [https://spaz.org/~jake/pix/2022-05/20220531_221354.jpg picture of switch location] [https://spaz.org/~jake/pix/2022-05/20220531_205222.jpg close-up picture of switch]
* Homing the robot is easy compared to getting the robot to be in the mood to be homed, especially after replacing the memory batteries. Don't be like this guy: https://www.robot-forum.com/robotforum/thread/14021-erc-k6sb-make-abs-data/ [https://spaz.org/~jake/robot/MotomanERChomePosition.pdf the PDF mentioned therein: MotomanERChomePosition.pdf]
* after the robot is working, you will have to remind it that you paid for all the deluxe options, like rectangular coordinates and remote access serial stuff. The "magic code" is 24.#4.#2 and the instructions for entering it are above, recounted by Ben.
* If the robot wakes up to a MAKE ABS DATA error it's probably having trouble communicating with some of the position encoders on the motors. The ABSolute position encoders are backed up by a battery and they can get into a state where they don't work right, that's what's described in the previous links is to get them to cooperate.
* <s>The controller wants to see eight position encoders. Six motors of the robot, a 7th giant heavy motor/gearbox assembly on the floor, and an 8th simulated by an arduino hanging by the wires from the circuitboard inside the cabinet.</s> We formerly used [https://github.com/jerkey/yasnac_fakery hardware to get it to boot up without errors], but moving jumpers on one of the circuit cards allowed it to be content with only the 6 axes of the arm itself.
= Electrical components =

*[http://pdf.datasheetcatalog.com/datasheet/MitsubishiElectricCorporation/mXvttst.pdf TM10T3B-H Thyristor module PDF]

*[http://irtfweb.ifa.hawaii.edu/~tcs3/tcs3/vendor_info/DeltaTau/manuals_0311/ACC-8D%20OPTION%209.PDF ACC-8D20 option PDF manual] 33 page manual on ???

* [http://irtfweb.ifa.hawaii.edu/~tcs3/tcs3/vendor_info/DeltaTau/manuals_0311/ACC-8D%20OPTION%209.PDF encoder datasheet] (pdf)(for different encoders?)

* [http://servo-repair.com/documents/yaskawa/CACR-SR.pdf Yaskawa CACR-SR Manual] (PDF) <------- this is totally what we have, absolute encoders and CACR servopacks

* [http://servo-repair.com/documents.php Servo Repair documents website]

http://www.yaskawa.co.jp/technology/img/tech/tech03_03_01.gif

http://ceeps.colostate-pueblo.edu/Engineering/RoboticsLaboratory/Motoman%20K3/PublishingImages/motoman04.gif

* http://www.youtube.com/watch?v=osErRS4m4S8#t=55
Servo contactor wiring notes: coil 160 ohms, connector CN2 pins 2 and 6. CN2:6 is also on relay socket and CN5:7, assumed common.
CN2:2 goes to CN5:8 and on to CN2CN:4 (near main on/off switch) where it gets jumped to CN2CN:3 by RLY12

= Coordinate conversion and 3d model =

https://github.com/sudoroom/sudo-robot-arm

= Cool Projects =
== Drawing with the Robot Arm Project ==

Substack and Jake went ahead and hacked the robot (see the [https://sudoroom.org/drawing-with-the-robot-arm/ blog post] ). now you can upload simple drawings and get it to draw for you.
* Get an image file (PNG) and convert it to SVG [http://image.online-convert.com/convert-to-svg free convert to SVG web app]
* Take the SVG and convert it to INFORM http://substack.neocities.org/svg2inform.html (thanks Substack!)
* Go to SudoRoom, chat with the right hackers, learn to calibrate (safety first!!!) and then let the robot do the drawing for you!

* Cheers! Cheers! More thanks to Jake for learning how to fake the serial disk https://github.com/jerkey/yasnac/blob/master/src/fakedisk.py

[[File:SudoRoom Robot Art Painter!.png|painting with the SudoRoom Robot arm <3 it's so good to learn from other people!]]

15:25 <@Rab> No small matter unfortunately, unless you get really imaginative on the CAM side and utilitize the robot's axes of movement in very simple ways.
15:27 <@Rab> I think it'll probably need to be somebody's brilliant custom CAM because open-sores CAM is pretty seriously limited, and more than 3-axis commercial CAM is insanely expensive.
15:28 <@Rab> PyCAM might be a start, that's what I'll use if I do anything 3D.
15:38 <@Rab> Autodesk Fusion 360 includes Autodesk's 3+2 CAM, which is probably the best and most usable CAM you'll find anywhere for zero dollars. But fuck that proprietary cloud shit.
15:42 <@Rab> CAM is one of those software applications which is so hard, anybody skilled enough to do it right also wants to get paid. That's a direct challenge to Sudo Room BTW.
15:45 <@Rab> You could join ##linuxcnc on feenode and see if anybody has any ideas.

= Serial port pinout to connect to a regular PC (DTE) 9-pin socket =
{| class="wikitable" style="margin:auto, text-align:left"
|-
! DB25 pins !! DE9 holes !! Signal (DE9 end) !! RJ45 pin#
|-
| 2 || 2 || RX || 2
|-
| 3 || 3 || TX || 3
|-
| 4 || 1 || DCD || 1
|-
| 5 || 4 || DTR || 4
|-
| 7 || 5 || GND || 5
|}
[[Category:Projects]]
[[Category:Diagnostics]]
[[Category:Diagnostics]]

File:PXL 20261004 075250470.jpg

2026-10-04T07:55:38Z

Jerkey: Schematic capture of power supply board for motor controllers

== Summary ==
Schematic capture of power supply board for motor controllers

Odroid

2026-10-02T20:37:21Z

Jerkey: Created page with "== ODROID-XU4 Single Board Computer with Quad Core 2GHz A15, 2GB RAM, USB 3.0, Gigabit == odroid-xu4 * fractalmess in discord says [https://www.amazon.com/dp/B0163GEA64 "so i have like a shit load of these (amazon link)"] * maybe 50 or so * they are in the spectro box , but these are brand new in the box , ping me if you want one or i just just plop a load of em over at sudo for a good time * Brand HARDKERNEL * Operating System Linux * CP..."

== ODROID-XU4 Single Board Computer with Quad Core 2GHz A15, 2GB RAM, USB 3.0, Gigabit ==
[[File:Odroid-xu4.jpg|thumb|odroid-xu4]]
* fractalmess in discord says [https://www.amazon.com/dp/B0163GEA64 "so i have like a shit load of these (amazon link)"]
* maybe 50 or so
* they are in the spectro box , but these are brand new in the box , ping me if you want one or i just just plop a load of em over at sudo for a good time
* Brand HARDKERNEL
* Operating System Linux
* CPU 2 GHz Cortex
* Integrated Graphics Coprocessor Mali-T628 MP6
* Memory Storage Capacity 2 GB
* Personal computer design type Mini PC
* Ram Memory Installed Size 2 GB
* Model Name LYSB0163G

File:Odroid-xu4.jpg

2026-10-02T20:31:03Z

Jerkey:

TAZ 4

2026-09-24T20:50:44Z

Jerkey:

Sudoroom has a TAZ 4 3d printer, that was donated in 2022. It should not be confused with the older [[TAZ|TAZ 3]] 3d printer, which didn't work very well as a 3D printer.

According [https://download.lulzbot.com/TAZ/4.0/documentation/current/manual/TAZ_4_Manual.pdf PDF Manual for the TAZ 4] <big>'''the Nozzle diameter is 0.35mm'''</big> (same as the TAZ3 which our extruder is from)

<big>'''This printer's extruder is setup to use 3mm diameter filament'''</big>, which is usually set as 2.85mm in the slicer. The manual says "it is highly recommended to take multiple measurements from along a length of the filament and use the average." but trial and error is probably more effective to find the right value.

<big>'''Print volume is X: 298 by Y: 275 by Z: 250 '''</big>according to [https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/Marlin_TAZ4_1.0.0.1/Marlin/Configuration.h Configuration.h] in the firmware

[https://download.lulzbot.com/TAZ/4.0/ All files for the TAZ 4 from Lulzbot corporation]

<big>'''The following "start code" (set up in the slicer's printer profile) should be used with this printer in order to properly set extruder motor current:
<code>M907 E150</code>'''</big>

If we recompile the [https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/ firmware] we can put the correct default values for extruder motor current but that would be hard to do.

[[File:720px-Rambo-conn-all.jpg|thumb]]
The extruder head from the TAZ 3 was transferred onto the TAZ 4 which will presumably make a better 3D printer. The TAZ 3 was sold to a freak who wanted to use it to dispense cookie dough or something?
[[File:Taz4-3d-printer.jpg|720px]]

The TAZ 4 uses an [https://reprap.org/wiki/Rambo Ultimachine Rambo 1.3L main board] and here is the correct [[File:RAMBo_1.3L_Schematic.pdf|RAMBo_1.3L_Schematic]]
The original 14-pin "Extruder 0" connector on the TAZ4 was removed from "Aux Power Mosfet Output" (pins 5/red,6/black), E0 Heat (pins 12,13), E0 Fan (9/black,10/red) and Ground (pin 2), and E0 (3,7,11,14). The extruder harness from the TAZ3 was installed in it.

The TAZ 4 didn't work because both Fuse F2 and F3 on the RAMBO main board were missing. They're supposed to be [https://www.littelfuse.com/products/fuse-blocks-fuseholders-and-fuse-accessories/fuse-blocks/154.aspx Littelfuse OMNI-BLOK 154 series] and we didn't have any, so I stuck 5-amp [https://www.digikey.com/en/products/detail/littelfuse-inc/0466005-NR/521341 F1460CT-ND] in there since we have dozens of them in the FUSES bin: [[Image:Taz4_fuse_kludge.jpg|thumb|left]]

After installing the TAZ3 extruder, its motor was mostly skipping. The current needed to be adjusted. There are no tiny potentiometers to adjust on this RAMBO board, only a "digipot", which is controlled with the [https://marlinfw.org/docs/gcode/M907.html M907 command]

the default values are found in
[https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/Marlin_TAZ4_1.0.0.1/Marlin/Configuration_adv.h Configuration_adv.h]:<code>#define DIGIPOT_MOTOR_CURRENT {175,175,240,135,135} // Values 0-255 (RAMBO 135 = ~0.75A, 185 = ~1A)

pins.h:#define DIGIPOT_CHANNELS {4,5,3,0,1} // X Y Z E0 E1 digipot channels to stepper driver mapping</code>

Stuff-org

2026-09-12T01:59:16Z

Jerkey: /* sudoroom uses stuff-org written by Henner Zeller to track stuff in the space (and in the community) */

== sudoroom uses stuff-org written by Henner Zeller to track stuff in the space (and in the community) ==
[[File:Noisebridge-stuff-org.png|thumb]]

* it is live and can be accessed from the local wifi/network at [https://stuff.sudoroom.org https://stuff.sudoroom.org]
* Noisebridge [https://parts.noisebridge.net runs a version of this] but you can only edit if you're on the local network
* [https://github.com/sudoroom/stuff-org/tree/sudoroom we use a fork of the main repository, branch "sudoroom"]
* we use [https://github.com/jerkey/websnap websnap] to update the images '''make sure this cant be abused from outside the network'''
* it's running on junk.local under user "stuff"

== installation ==
* make a new user just for stuff-org and websnap
<pre>sudo adduser --disabled-password stuff --comment "stuff-org user"</pre>
* [https://go.dev/dl/ install golang] (as a user with sudo, not as user stuff)
<pre>
wget https://go.dev/dl/go1.24.1.linux-amd64.tar.gz # or current version
sudo tar -C /usr/local -xzf go1.24.1.linux-amd64.tar.gz
echo 'export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin' >> ~/.profile
echo 'export PATH=$PATH:/usr/local/go/bin' | sudo tee -a ~stuff/.profile
</pre>
* pull the repository, run make
sudo su stuff
source ~/.profile # idk why i had to do this to get golang to work
cd ; git clone https://github.com/sudoroom/stuff-org
cd stuff-org/stuff
git checkout sudoroom
make stuff
</pre>
* install nvm so we can have node
<pre>
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bash
exit
(now log back in)
nvm install --lts
</pre>
* install websnap (in home directory, not inside stuff-org)
<pre>
cd ; git clone https://github.com/sudoroom/websnap
cd websnap
npm install
</pre>

Thread:Talk:CHMT36/Archive article/reply

2026-07-17T05:25:29Z

Jerkey: Reply to Should we archive the page CHMT36?

Just change it to past tense and say the owner took it back. You can link to our other in-house fab stuff

Network

2026-06-24T02:13:15Z

Jerkey: /* LAN */ move bigtv static IP to outside of non-static IP range

__NOTOC__
''For more information about sudo room's systems in general, see [[Systems Administration]]''

The sudo room '''network''' provides internal networking, internet access, wireless service, and some externally accessible devices or services.

== Main PoE ethernet switch ===

* HP ProCurve 2910al-480-PoE+ switch [https://github.com/wwwhtml/hp-2910al-switch-firmware-upgrade/ How to manage / firmware update]
* username: manager or operator
* password: Ask juul or someone on the sysadmins list
* MAC address main switch: a0:b3:cc:ac:e7:c0
* MAC address backup switch (not turned on): c0:91:34:c4:12:00
* Port 1 is VLAN 1 untagged, acting as DHCP client, is management VLAN
* Management possible via HTTP (no SSL) or SSH
* Port 1 is for management, untagged no VLAN and requests an IP using DHCP (not plugged into anything right now)
* Port 2 and 3 are for tagged access to VLANs 2 and 3 (public and private)
* Ports 4 to 24 are for untagged access to VLAN 2 (public)
* Ports 25 to 48 are for untagged access to VLAN 3 (private)

== WAN ==

Internet access comes from LMI. The modem is connected through VDSL copper next to the Omni main electrical panels.

The modem is up in the rack area near '''saros''' (a desktop computer running Debian Stretch) which serves as the primary gateway router.

Our public IP is 142.254.26.9 aka '''room.sudoroom.org'''.

== LAN ==
* Wifi subnet: 100.64.64.0/22
** 100.64.64.2 to 100.64.64.49: static range
** 100.64.64.50 to 100.64.67.250: DHCP

This list of static IPs may not be complete. Before choosing a static IP, please use ping or nmap to check it first.

{| class="wikitable sortable blue_lines"
|+ Machines with static IPs
! style="width:120px;" data-sort-type="IPAddress" | IPv4 Address
! style="width:110px;" data-sort-type="IPAddress" | IPv6 or MAC Address
! style="width:110px;" | Assigned to
! class="unsortable" | Notes
! Who set it up?
|-
| 100.64.64.1
| 00:0d:b9:59:e4:b9
| sudogateway
| router/room.sudoroom.org
| [[User:juul|Juul]]
|-
| 100.64.64.11
| d0:39:72:18:59:06
| omnidoor
| beaglebone black controlling the door
| juul and jake
|-
| 192.168.42.3
| No IPv6 address
| No host name
| Dell PowerConnect 5324 24 port gigabit switch
| juul
|-
| 192.168.42.4
| No IPv6 address
| No host name
| Dell PowerConnect 5448 48 port gigabit switch
| juul
|-
| 192.168.42.10
|
| nodeconf.local
| The sudo mesh node configuration and build server
| Primarily [[User:Juul|juul]] and maxb
|-
| 100.64.65.66
| 84:25:19:71:bb:26
| SAMSUNG MX
| A printer in CCL that is naughty about avahi packets
| Dan of CCL and [[User:Jerkey]]
|-
| 100.64.64.88
| 00:21:b7:80:59:47
| ET0021B7805947.local
| [[Lexmark T654dn | Lexmark T654dn laser printer]]
| [[User:Jerkey|jerkey]]
|-
| 100.64.64.20
| 00:21:9b:1d:85:c1
| wasp.local
| [[Wasp.local| 3d printer desktop computer & giant_robot_arm serial host]]
| [[User:jake|jake]]
|-
| 100.64.64.30
| c4:54:44:3c:21:1e
| bigtv.local
| [[bigtv| fanless ChromeBox connected to the big TV above skÃ¼lgaard]]
| [[User:jake|jake]]
|-
| 100.64.64.29
| c0:8a:de:1d:59:b6
|
| ruckus_wifi_controller [https://github.com/sudoroom/ruckus-zonedirector1100-firmware-upgrade-process firmware upgrade process]
| daniel
|-
| 100.64.65.233
| c0:8a:de:2f:c1:80
|
| ruckus_wifi_accesspoint in "phat beets" room (termination is on 2nd floor top right of mess on beam)
| daniel
|-
|}

== Wireless Access Points (OUTDATED INFO) ==

All of the indoor wifi is being served up by [[Mesh/OmniWifi|TP-Link N750 routers modified for PoE]] running OpenWRT and configured as bridges with static IPs.

{| class="wikitable blue_lines"
!SSID
!Security
!Key
!MAC
!IP
!Channel
!Location
!Hardware
!Who set it up?
|-
|peoplesopen.net-omniroof
|open
|''n/a''
|Find Me
|100.64.64.4
|161 (5ghz)
|On flagpole on roof
|Ubiquiti NanoBeam
|[[User:Juul|juul]]
|-
|peoplesopen.net
|open
|''n/a''
|Find Me
|100.64.64.2
|11 (2.4ghz) and 36 (5ghz)
|Above entrance to CCL
|TP-Link N750
|[[User:Juul|juul]]
|-
|peoplesopen.net
|open
|''n/a''
|Find Me
|100.64.64.3
|6 (2.4ghz) and 165 (5ghz)
|middle of basement
|TP-Link N750
|[[User:Juul|juul]]
|-
|sudomesh
|open
|''n/a''
|Find Me
|192.168.42.18
|11
|zip-tied near server rack
|Ubiquiti Nanostation M2 Loco
|[[User:Juul|juul]]
|-
|Omni Ballroom
|open
|''n/a''
|Find Me
|192.168.42.19
|11
|Ballroom near stage
|Ubiquiti Picostation 2
|[[User:Maxb|maxb]]
}

[[Category:Network]]

Artemis

2026-06-01T21:28:54Z

Jerkey:

==Overview==
[[File:Flashforge artemis.webp|thumb|Flashforge Artemis blue 3d printer]]

'''Printer Name:''' Flashforge ARtemis

'''Preferred Slicer:''' [https://sudoroom.org/wiki/OrcaSlicer Orca Slicer]

'''Nozzle:''' 0.4mm

'''Bed Type:''' STextured

'''Filament:''' PLA, 1.75

==Status==
Being hacked starting 05/31/2026, see "next steps"

==hacking==
* Bottom cover held on by five 2.5mm hex-key M4 screws
* it was proprietary garbage so we hacked in by connecting directly to the mainboard serial port, 3.3v TX/RX at 115200 baud, and used the bootloader to get a root shell and reset the password. Then we enabled telnetd by renaming /etc/init.d/telnet to S23telnet
* we installed a newer busybox in /bin/ and made links to it including nc (netcat) and pgrep (not quite working though) so we can connect that serial port to a TCP/IP port and use the printer over the network
* method of getting the newer busybox binary on there was to put the file on the laser PC's web server folder and using "wget" which worked because https wasnt required
* MAC Address: 94:a4:08:a0:c0:c5
* IP: 100.64.64.158

[[File:Hacking signal-2026-06-01-122441 002.jpeg|thumb|connecting directly to the mainboard serial port]]
==next steps==
* printer motion controller is on /dev/tty/S2, baud rate 115200
* telnet in, kill the proprietary application that talks to the motion controller, and run <code>nc -l -p 1200 < /dev/tty/S2 > /dev/tty/S2</code>
* then on another computer, run <code>socat something something 100.64.64.158 port 1200 /dev/virtualSerialport</code> to create a serial port that actually just goes through the local network to the motion controller in this printer, and control it using pronterface or ideally octoprint running on the laser cutter computer

==Documentation==

==Printing Tips==

==Maintenance Log==
* Telnet enabled 5/31/26

File:Flashforge artemis.webp

2026-06-01T21:15:07Z

Jerkey: Flashforge Artemis 3d printer

== Summary ==
Flashforge Artemis 3d printer

File:Hacking signal-2026-06-01-122441 002.jpeg

2026-06-01T21:11:08Z

Jerkey: it was proprietary garbage so we hacked in by connecting directly to the mainboard serial port, 3.3v TX/RX at 115200 baud, and used the bootloader to get a root shell and reset the password to usually. Then enabled telnetd by renaming /etc/init.d/telnet to S23telnet

== Summary ==
it was proprietary garbage so we hacked in by connecting directly to the mainboard serial port, 3.3v TX/RX at 115200 baud, and used the bootloader to get a root shell and reset the password to usually. Then enabled telnetd by renaming /etc/init.d/telnet to S23telnet

Giant robot arm

2026-05-14T22:30:57Z

Jerkey:

<big>Yaskawa Motoman K10S</big>

[[File:Robot typing its name on a laptop.jpeg|750px|left|typing on a laptop]]
[[File:Robot_teasing_korl.jpg|thumb|right|robot in sudoroom]]
[[File:Giantrobot-getting.jpg|thumb|humans bringing the robot to sudoroom]]
[[File:Giant_robot_arm_where_it_came_from.jpg|thumb|as it was found]]
[[File:Robot_axes.jpg|robot axes and their directions]]
[[File:Robot home position.png|250px|robot homed position pose]]
[[File:SudoRoom Robot Art Painter!.png|thumb|You can even make the robot arm paint for you!]]

= videos by Wade Bourne
* [https://spaz.org/~jake/robot/wadevids/robot%20draws%20a%20circle%20in%20a%20square.mp4 robot draws a circle in a square.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20redraws%20a%20circle%20in%20a%20square.mp4 robot redraws a circle in a square.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20types%20hello%20world%20on%20a%20laptop.mp4 robot types hello world on a laptop.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20typing%20its%20name%20on%20a%20laptop.mp4 robot typing its name on a laptop.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20writes%20hello.mp4 robot writes hello.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20writes%20hello%20backwards.mp4 robot writes hello backwards.mp4]
* [https://spaz.org/~jake/robot/wadevids/robot%20carves%20a%20piece%20of%20foam.mp4 CAUTION: LOUD robot carves a piece of foam.mp4]

= what is it for? =

It's a six-axis CNC machine that is rated to move 10 kilograms around in any orientation, with 1mm accuracy.

= software for communicating with the robot from a regular computer =

[https://github.com/wbourne0/yasnac software written in Go by Wade Bourne]

[https://github.com/jerkey/yasnac software written by several people for working with the robot]

Use motofile and motocommand while the REMOTE button on the robot is lit up. To enable the REMOTE button, you must [https://sudoroom.org/wiki/Giant_robot_arm#enabling_relative_job_function_and_the_communications_option enable remote operation] first

Your computer must be connected to the robot over an [https://sudoroom.org/mediawiki/index.php?title=Giant_robot_arm&action=submit#Serial_port_pinout_to_connect_to_a_regular_PC_(DTE)_9-pin_socket RS232 serial cable]. [https://github.com/jerkey/yasnac/blob/master/remote/motofile motofile] lets you send job files to the robot, and [https://github.com/jerkey/yasnac/blob/master/remote/motocommand motocommand] lets you tell the robot what to do, as if you were pressing buttons on the control panels. [https://github.com/jerkey/yasnac/blob/master/remote/motomove motomove] can move the robot directly (without loading a job file) but it is poorly supported in the robot's firmware and was never considered complete by the manufacturer (they moved onto the MRC control system development for this) so use it with caution.

= documentation =
* [https://spaz.org/~jake/robot/479950-3-Programming_manual_v4-ocr.pdf programming manual] (searchable thanks to OCR)
* Homing https://pdfcoffee.com/erc-homing-pdf-free.html
* Collection of docs http://spaz.org/~jake/robot
* [http://spaz.org/~jake/robot/155493-INFORM-LANGUAGE.pdf INFORM Lanugage manual PDF] and another copy here [http://www.ro.feri.uni-mb.si/predmeti/robotizacija/inform.pdf INFORM PDF]
* [http://www.robot-forum.com/robotforum/yaskawa-motoman-robot-forum/motoman-k6sb-with-erc-controller/ Robotforum posts on the Yaskawa motoman k6sb with erc controller] ''talk to these people for the conversation''
* [https://spaz.org/~jake/robot/CACR-SR15SZ1SDY214-SERVOPACK-YASKAWA-MANUAL.pdf a modern replacement for the motor controllers] (aka a much more readable PDF about these motor drivers)
* [https://spaz.org/~jake/robot/CACR-SR-BB1.pdf an original PDF manual for the motor controllers] (but actually searchable thanks to OCR)

= enabling relative job function and the communications option =

Ben says:

"If I remember, press OP2, enter the magic code 24.#4.#2 then set these:

set SD079 to 1 for relative job (x,y,z coordinates)

set SD110 to 1 for data communication (remote mode)

and reboot the robot."

= Getting the robot working if it has forgotten its purpose =
* There is a battery inside the connector compartment of the robot arm, and another next to the computer boards on the door of the control cabinet. If the batteries go dead or are disconnected, the robot will act stupid and refuse to boot up with some dumb error screen like this:
<code>
ERROR NO. ERROR STATUS
SV1: 1 00 0000_0000
2 00 0000_0000
3 01 0000_0001
SV2: 1 00 0000_0000
2 00 0000_0000
3 05 0000_0010
SV3: 1 00 0000_0000
2 00 0000_0000
3 00 0000_0000
SV4: 1 00 0000_0000
2 00 0000_0000
3 00 0000_0000
</code>
This probably means the battery in the robot arm itself (behind the connectors) is dead. You might have to short Batt0 to RESET for 30 minutes or something before putting in a new battery and re-homing?
https://www.robot-forum.com/robotforum/thread/20910-motoman-yasnac-erc-k6sb1-make-abs-data-error/

* Homing https://pdfcoffee.com/erc-homing-pdf-free.html basically, pose the robot as shown above, press OP2, press 0 eight times, ENTER, and then you can tell it that it's presently homed. You can also home fewer than all axes by selecting which axes you want to home, before pressing the button for "Setting" which is how you tell it to save the present position. As of 2022/12/7 the absolute encoder values for SLURBT are: 5771,30829,-25795,-792,66,-1047. IF the physical limit switch (for example on the S axis) is hit, you have to HOLD the "overrun" bypass button next to the serial port while booting up and CAREFULLY jogging S- or S+ to fix that problem, and then you can let go of the button.
* There is a switch inside the control cabinet on the edge of the CPU1 card which puts it into [https://spaz.org/~jake/pix/2022-05/20220531_205509.jpg MAINT mode (switch up)] or [https://spaz.org/~jake/pix/2022-05/20220531_213820.jpg PARAM mode (switch down)], normally the switch is in the middle. Hard-power cycling the robot is how you reboot it. [https://spaz.org/~jake/pix/2022-05/20220531_221354.jpg picture of switch location] [https://spaz.org/~jake/pix/2022-05/20220531_205222.jpg close-up picture of switch]
* Homing the robot is easy compared to getting the robot to be in the mood to be homed, especially after replacing the memory batteries. Don't be like this guy: https://www.robot-forum.com/robotforum/thread/14021-erc-k6sb-make-abs-data/ [https://spaz.org/~jake/robot/MotomanERChomePosition.pdf the PDF mentioned therein: MotomanERChomePosition.pdf]
* after the robot is working, you will have to remind it that you paid for all the deluxe options, like rectangular coordinates and remote access serial stuff. The "magic code" is 24.#4.#2 and the instructions for entering it are above, recounted by Ben.
* If the robot wakes up to a MAKE ABS DATA error it's probably having trouble communicating with some of the position encoders on the motors. The ABSolute position encoders are backed up by a battery and they can get into a state where they don't work right, that's what's described in the previous links is to get them to cooperate.
* <s>The controller wants to see eight position encoders. Six motors of the robot, a 7th giant heavy motor/gearbox assembly on the floor, and an 8th simulated by an arduino hanging by the wires from the circuitboard inside the cabinet.</s> We formerly used [https://github.com/jerkey/yasnac_fakery hardware to get it to boot up without errors], but moving jumpers on one of the circuit cards allowed it to be content with only the 6 axes of the arm itself.
= Electrical components =

*[http://pdf.datasheetcatalog.com/datasheet/MitsubishiElectricCorporation/mXvttst.pdf TM10T3B-H Thyristor module PDF]

*[http://irtfweb.ifa.hawaii.edu/~tcs3/tcs3/vendor_info/DeltaTau/manuals_0311/ACC-8D%20OPTION%209.PDF ACC-8D20 option PDF manual] 33 page manual on ???

* [http://irtfweb.ifa.hawaii.edu/~tcs3/tcs3/vendor_info/DeltaTau/manuals_0311/ACC-8D%20OPTION%209.PDF encoder datasheet] (pdf)(for different encoders?)

* [http://servo-repair.com/documents/yaskawa/CACR-SR.pdf Yaskawa CACR-SR Manual] (PDF) <------- this is totally what we have, absolute encoders and CACR servopacks

* [http://servo-repair.com/documents.php Servo Repair documents website]

http://www.yaskawa.co.jp/technology/img/tech/tech03_03_01.gif

http://ceeps.colostate-pueblo.edu/Engineering/RoboticsLaboratory/Motoman%20K3/PublishingImages/motoman04.gif

* http://www.youtube.com/watch?v=osErRS4m4S8#t=55
Servo contactor wiring notes: coil 160 ohms, connector CN2 pins 2 and 6. CN2:6 is also on relay socket and CN5:7, assumed common.
CN2:2 goes to CN5:8 and on to CN2CN:4 (near main on/off switch) where it gets jumped to CN2CN:3 by RLY12

= Coordinate conversion and 3d model =

https://github.com/sudoroom/sudo-robot-arm

= Cool Projects =
== Drawing with the Robot Arm Project ==

Substack and Jake went ahead and hacked the robot (see the [https://sudoroom.org/drawing-with-the-robot-arm/ blog post] ). now you can upload simple drawings and get it to draw for you.
* Get an image file (PNG) and convert it to SVG [http://image.online-convert.com/convert-to-svg free convert to SVG web app]
* Take the SVG and convert it to INFORM http://substack.neocities.org/svg2inform.html (thanks Substack!)
* Go to SudoRoom, chat with the right hackers, learn to calibrate (safety first!!!) and then let the robot do the drawing for you!

* Cheers! Cheers! More thanks to Jake for learning how to fake the serial disk https://github.com/jerkey/yasnac/blob/master/src/fakedisk.py

[[File:SudoRoom Robot Art Painter!.png|painting with the SudoRoom Robot arm <3 it's so good to learn from other people!]]

15:25 <@Rab> No small matter unfortunately, unless you get really imaginative on the CAM side and utilitize the robot's axes of movement in very simple ways.
15:27 <@Rab> I think it'll probably need to be somebody's brilliant custom CAM because open-sores CAM is pretty seriously limited, and more than 3-axis commercial CAM is insanely expensive.
15:28 <@Rab> PyCAM might be a start, that's what I'll use if I do anything 3D.
15:38 <@Rab> Autodesk Fusion 360 includes Autodesk's 3+2 CAM, which is probably the best and most usable CAM you'll find anywhere for zero dollars. But fuck that proprietary cloud shit.
15:42 <@Rab> CAM is one of those software applications which is so hard, anybody skilled enough to do it right also wants to get paid. That's a direct challenge to Sudo Room BTW.
15:45 <@Rab> You could join ##linuxcnc on feenode and see if anybody has any ideas.

= Serial port pinout to connect to a regular PC (DTE) 9-pin socket =
{| class="wikitable" style="margin:auto, text-align:left"
|-
! DB25 pins !! DE9 holes !! Signal (DE9 end) !! RJ45 pin#
|-
| 2 || 2 || RX || 2
|-
| 3 || 3 || TX || 3
|-
| 4 || 1 || DCD || 1
|-
| 5 || 4 || DTR || 4
|-
| 7 || 5 || GND || 5
|}
[[Category:Projects]]
[[Category:Diagnostics]]
[[Category:Diagnostics]]

Meetings

2026-04-27T00:29:18Z

Jerkey: typo in link to march 29 meeting

Sudoroom's official meetings are twice a month (second Thursdays at 7pm, and last Sundays at 4pm). They are bureaucratic, sometimes fun, and usually more functional than rumored. We try to handle conflicts respectfully.

TODO: Some more info on <pre>sudo make meeting --excellence TRUE</pre>

[https://meet.waag.org/turtlesturtlesturtles ONLINE JITSI PORTAL]

== Etherpad ==

We keep our agenda on an etherpad. The etherpad is projected on a big screen for everyone to see. Anyone who knows the URL can collaboratively edit it on their laptop. After the meeting, its contents are copied to our wiki - that's how we keep record. Then we clear it for the next meeting and people can add items throughout the week. Ideally someone posts a summary to the mailing list, but that doesn't always happen.

Unfortunately, in the past our etherpad has caught the attention of online troll dens who like to overwhelm it and make it unusable. For this reason, we don't post the address online. Sorry! '''These addresses''' had been used in the past, and '''are obsolete''':

* https://pad.riseup.net/p/sudoroommeeting

See [[Meeting template]] when starting a new meeting!

== Future meeting topics ==

Add them at this etherpad: https://pad.riseup.net/p/sudo-proposals

== Archive ==

Each old meeting gets its own page, and we link to them here.

{| class="wikitable sortable collapsible"
! colspan="3"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | new member interviews
! class="unsortable" | comments
|-
| [[ Meeting Notes 2026-03-29|2026-03-29]]
|
| short meeting. We need more monthly $$ contributions!
|-
|-
| [[ Meeting Notes 2026-02-22|2026-02-22]]
|
| Member Matters, Name tags
|-
|-
| [[ Meeting Notes 2026-02-12|2026-02-12]]
|
|-
|-
| [[Meeting Notes 2026-01-25|2026-01-25]]
|
| matrix, thursday party once a month, new members, overdue for board member elections, finances, emailing lapsed members results
|-
|-
| [[Meeting Notes 2026-01-15|2026-01-15]]
|
| Emailing lapsed members,Member Matters migration,Discourse forum for sudoroom, events, new member applications
|-
|-
| [[Meeting Notes 2025-12-28|2025-12-28]]
|
| money, Member Matters, communication, recurring member meetings, wiki meeting, SR member conflict, new members
|-
|-
| [[Meeting Notes 2025-10-12|2025-10-12]]
|
| Member Matters, membership
|-
|-
| [[Meeting Notes 2025-09-14|2025-09-14]]
|
| back door progress, budget, Membership approvals and process discussion, events, fundraising
|-
|-
| [[Meeting Notes 2025-07-16|2025-07-16]]
|
| apartheid free comunities pledge, weekly finance report back labor
|-
| [[Meeting Notes 2025-05-28|2025-05-28]]
|
| Membership, Apartheid Free Zone proposal, new events
|-
|-
| [[Meeting Notes 2025-05-14|2025-05-14]]
|
| Nonprofit Organizing meeting
|-
|-
| [[Meeting Notes 2024-12-11|2024-12-11]]
|
| member voting quorum for new bylaws decided
|-
|-
| [[Meeting Notes 2024-11-21|2024-11-21]]
|
| creating new bylaws, clearing out space for CC, need to remove items below stairwell
|-
|-
| [[Meeting Notes 2024-08-21|2024-08-21]]
|
| discussing new CALLI/EB PREC lease
|-
|-
| [[Meeting Notes 2024-06-12|2024-06-12]]
|
| williams proposal for new projects in sudoroom
|-
|-
| [[Meeting Notes 2024-03-27|2024-03-27]]
|
| alex steps down as delegate, draft new collective requirements
|-
|-
| [[Meeting Notes 2024-03-06|2024-03-06]]
|
| omni bylaw discussion (majority to majority + 1), wheelchair lift gate plans
|-
|-
| [[Meeting Notes 2024-02-28|2024-02-28]]
|
| approve bylaw changes and deb gives collective membership. fundraising requests
|-
|-
| [[Meeting Notes 2024-02-21|2024-02-21]]
|
| another recap meeting. call for SR volunteers for maker fair on 25th and for the fundraising wg
|-
|-
| [[Meeting Notes 2024-02-14|2024-02-14]]
|
| CAST meeting recap, Deb Gives collective app, laser class march 13
|-
|-
| [[Meeting Notes 2024-01-31|2024-01-31]]
|
| PP collective app, omni officer nominations, ed update
|-
|-
| [[Meeting Notes 2024-01-24|2024-01-24]]
|
| Jamal hiring contract, peoples programs proposal, Missey, CIM, land trusts, LLC update
|-
|-
| [[Meeting Notes 2024-01-17|2024-01-17]]
|
| foreclosure worst outcome, alex voted delegate
|-
|-
|-
| [[Meeting Notes 2024-01-10|2024-01-10]]
|
| accountability, bans, omni executive director discussion
|-
|-
|-
| [[Meeting Notes 2024-01-03|2024-01-03]]
|
|
|-
|-
| [[Meeting Notes 2023-12-27|2023-12-27]]
|
| PP co-ownership proposal, future imaginations
|-
|-
| [[Meeting Notes 2023-12-20|2023-12-20]]
|
| PP proposal and counterproposals in advance of omni meeting
|-
|-
| [[Meeting Notes 2023-12-13|2023-12-13]]
|
| PP proposal, proposal to set up LLC
|-
|-
| [[Meeting Notes 2023-11-02|2023-11-02]]
|
| omni collective statement and finances
|-
|-
| [[Meeting Notes 2023-10-05|2023-10-05]]
|
| informal, how to make sudoroom more welcoming, delegate position and duties
|-
| [[Meeting Notes 2023-09-27|2023-09-27]]
|
|
|-
| [[Meeting Notes 2023-09-20|2023-09-20]]
|
|
|-
| [[Meeting Notes 2023-09-06|2023-09-06]]
|
|
|-
| [[Meeting Notes 2023-08-02|2023-08-02]]
|
| event planning
|-
| [[Meeting Notes 2023-07-05|2023-07-05]]
|
| cnc router, organizing ourselves
|-
| [[Meeting Notes 2023-06-07|2023-06-07]]
| none
| member stats, save omni, keeping space clean, event ideas
|-
| [[Meeting Notes 2023-03-01|2023-03-01]]
| Our big March Meeting
| Plans for March
|-
| [[Meeting Notes 2023-01-25|2023-01-25]]
| low stakes meeting
| proposals for working groups (let's keep this updated at [[Working_Groups|Working Groups]]
|-
| [[Meeting Notes 2023-01-11|2023-01-11]]
| Start of the new year
| proposals for working groups (let's keep this updated at [[Working_Groups|Working Groups]]
|-
| [[Meeting Notes 2022-04-06|2022-04-06]]
| Arthur Eva PWM PB
| Four new members, plus two proposals
|-
| [[Meeting Notes 2021-06-02|2021-06-02]]
| kabirdas
| electrical and ventilation
|-
| | [[Meeting Notes 2021-05-26|2021-05-26]]
|
| Reopening, project and event ideas
|-
| [[Meeting Notes 2021-05-19|2021-05-19]]
| Nik
| Reopening, access control, computers
|-
| [[Meeting Notes 2021-05-12|2021-05-12]]
|
| Sudo Room decides to continue existing and stuff
|-
| [[Sudoroom_Meeting_2019_04_03|2019-04-03]]
|
| discussion & consensus about GCEA proposals & paying Jenny for bookkeeping
|-
| [[Meeting_Notes_2018-04-11|2018-04-11]]
| Rich
| Steve banned, omni proposals mentioned but not discussed
|-
| [[Meeting_Notes_2018-03-14|2018-03-14]]
| Tom Levine Andrew Vaziri
| Change to membership process passed, endorsing statement from The Village to City, discussion of conflict w/ Steve
|-
| [[Meeting_Notes_2018-01-10|2018-01-10]]
| Jacques Noah
| melissa and sierk as new omni delegates;
|-
| [[Meeting_Notes_2017-12-13|2017-12-13]]
| * Adam Bredenberg Melissa Crow Pato Adam Eric Jan
| discussion of finances, omni cafe proposal discussion
|-
| [[Meeting_Notes_2017-11-29|2017-11-29]]
|
| Another irregular meeting, with two topics of interest.
|-
| [[Meeting_Notes_2017-11-08|2017-11-08]]
|
|
|-
| [[Meeting_Notes_2017-11-01|2017-11-01]]
|
| Not a usual meeting date, but notes were taken.
|-
| [[Meeting_Notes_2017-08-13|2017-08-13]]
|
|
|-
| [[Meeting_Notes_2017-08-09|2017-08-09]]
| Kyle Matt Rayc
|
|-
| [[Meeting_Notes_2017-07-12|2017-07-12]]
|
|
|-
| [[Meeting_Notes_2017-05-10|2017-05-10]]
| Corey Travis
|
|-
| [[Meeting_Notes_2017-04-12|2017-04-12]]
|
|
|-
| [[Meeting_Notes_2017-03-08|2017-03-08]]
|
|
|-
| [[Meeting_Notes_2017-02-08|2017-02-08]]
|
|
|-
| [[Meeting_Notes_2017-01-25|2017-01-25]]
|
|
|-
| [[Meeting_Notes_2017-01-11|2017-01-11]]
|
|
|-
| [[Meeting_Notes_2017-01-04|2017-01-04]]
|
|
|-
| [[Meeting_Notes_2016-12-14|2016-12-14]]
|
|
|-
| [[Meeting_Notes_2016-11-16|2016-11-16]]
|
|
|-
| [[Meeting_Notes_2016-11-09|2016-11-09]]
|
|
|-
| [[Meeting_Notes_2016-10-12|2016-10-12]]
| Vienna
|
|-
| [[Meeting_Notes_2016-09-14|2016-09-14]]
| T Maes Evan Short
|
|-
| [[Meeting_Notes_2016-08-17|2016-08-17]]
|
|
|-
| [[Meeting_Notes_2016-08-10|2016-08-10]]
|
|
|-
| [[Meeting_Notes_2016-07-20|2016-07-20]]
|
|
|-
| [[Meeting_Notes_2016-07-13|2016-07-13]]
|
|
|-
| [[Meeting_Notes_2016-06-15|2016-06-15]]
| Eric Wen-qing Alex Yvonne
|
|-
| [[Meeting_Notes_2016-06-08|2016-06-08]]
| Tim Chris Lindsey
|
|-
| [[Meeting_Notes_2016-05-11|2016-05-11]]
| James Corey Benjamin Huang
|
|-
| [[Meeting_Notes_2016-04-27|2016-04-27]]
| Elliot
|
|-
| [[Meeting_Notes_2016-04-20|2016-04-20]]
| Syd
|
|-
| [[Meeting_Notes_2016-04-13|2016-04-13]]
| Abhiram Pete Forsyth Dirty Bill Chris Jamie
|
|-
| [[Meeting_Notes_2016-04-06|2016-04-06]]
| Jacob Jason
|
|-
| 2016-03-30
|rowspan=6 colspan=2 align=center|We totally flaked for the entire month of March.
|-
| 2016-03-23
|-
| 2016-03-23
|-
| 2016-03-16
|-
| 2016-03-09
|-
| 2016-03-02
|-
| [[Meeting_Notes_2016-02-24|2016-02-24]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-17|2016-02-17]]
| bstack
|
|-
| [[Meeting_Notes_2016-02-10|2016-02-10]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-03|2016-02-03]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-27|2016-01-27]]
| Jay
|
|-
| [[Meeting_Notes_2016-01-20|2016-01-20]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-13|2016-01-13]]
|
| cancelled-ish
|-
| [[Meeting_Notes_2016-01-06|2016-01-06]]
| nathan Nick
|
|-
| [[Meeting_Notes_2015-12-30|2015-12-30]]
| Charley
|
|-
| 2015-12-23
|
| no signs of having happened
|-
| [[Meeting_Notes_2015-12-16|2015-12-16]]
| Daisy
|
|-
| [[Meeting_Notes_2015-12-09|2015-12-09]]
|
|
|-
| [[Meeting_Notes_2015-12-02|2015-12-02]]
| Max
|
|-
| [[Meeting_Notes_2015-11-25|2015-11-25]]
|
| didn't really happen, blame thanksgiving
|-
| [[Meeting_Notes_2015-11-18|2015-11-18]]
| morgan
|
|-
| [[Meeting_Notes_2015-11-11|2015-11-11]]
| Kwaku Gracie Micolah
|
|-
| [[Meeting_Notes_2015-11-04|2015-11-04]]
| dane
|
|-
| [[Meeting_Notes_2015-10-28|2015-10-28]]
| Andrew
|
|-
| [[Meeting Notes 2015-10-21|2015-10-21]]
| Merry
|
|-
| [[Meeting Notes 2015-10-14|2015-10-14]]
| Alex Lef Mari
|
|-
| [[Meeting Notes 2015-10-07|2015-10-07]]
| Tom Daron
|
|-
| [[Meeting Notes 2015-09-30|2015-09-30]]
|
| Insufficient critical mass
|-
| [[Meeting Notes 2015-09-23|2015-09-23]]
| Ari
|
|-
| [[Meeting Notes 2015-09-16|2015-09-16]]
| david
|
|-
| [[Meeting Notes 2015-09-09|2015-09-09]]
|
|
|-
| [[Meeting Notes 2015-09-02|2015-09-02]]
| Benji
|
|-
| [[Meeting Notes 2015-08-26|2015-08-26]]
|
|
|-
| 2015-08-19
|
| nobody showed up
|-
| [[Meeting Notes 2015-08-12|2015-08-12]]
|
|
|-
| [[Meeting Notes 2015-08-05|2015-08-05]]
|
|
|-
| [[Meeting Notes 2015-07-29|2015-07-29]]
|
|
|-
| [[Meeting_Notes_2015-07-22|2015-07-22]]
|
|
|-
| [[Meeting_Notes_2015-07-15|2015-07-15]]
|
|
|-
| [[Meeting_Notes_2015-07-08|2015-07-08]]
|
|
|-
| [[Meeting_Notes_2015-07-01|2015-07-01]]
|
|
|-
| [[Meeting_Notes_2015-06-24|2015-06-24]]
|
|
|-
| [[Meeting_Notes_2015-06-17|2015-06-17]]
|
|
|-
| [[Meeting_Notes_2015-06-10|2015-06-10]]
|
|
|-
| [[Meeting_Notes_2015-06-03|2015-06-03]]
|
|
|-
| [[Meeting_Notes_2015-05-27|2015-05-27]]
|
|
|-
| [[Meeting_Notes_2015-05-20|2015-05-20]]
|
|
|-
| [[Meeting_Notes_2015-05-13|2015-05-13]]
|
|
|-
| [[Meeting_Notes_2015-05-06|2015-05-06]]
|
|
|-
| [[Meeting_Notes_2015-04-29|2015-04-29]]
|
|
|-
| [[Meeting_Notes_2015-04-22|2015-04-22]]
|
|
|-
| [[Meeting_Notes_2015-04-15|2015-04-15]]
|
|
|-
| [[Meeting_Notes_2015-04-08|2015-04-08]]
|
|
|-
| [[Meeting_Notes_2015-04-01|2015-04-01]]
|
|
|-
| [[Meeting_Notes_2015-03-25|2015-03-25]]
|
|
|-
| [[Meeting_Notes_2015-03-18|2015-03-18]]
|
|
|-
| [[Meeting_Notes_2015-03-11|2015-03-11]]
|
|
|-
| [[Meeting_Notes_2015-03-04|2015-03-04]]
|
|
|-
| [[Meeting_Notes_2015-02-25|2015-02-25]]
|
|
|-
| [[Meeting_Notes_2015-02-18|2015-02-18]]
|
|
|-
| [[Meeting_Notes_2015-02-11|2015-02-11]]
|
|
|-
| [[Meeting_Notes_2015-02-04|2015-02-04]]
|
|
|-
| [[Meeting_Notes_2015-01-28|2015-01-28]]
|
|
|-
| [[Meeting_Notes_2015-01-21|2015-01-21]]
|
|
|-
| [[Meeting_Notes_2015-01-14|2015-01-14]]
|
|
|-
| [[Meeting_Notes_2015-01-07|2015-01-07]]
|
|
|-
| [[Meeting_Notes_2014-12-31|2014-12-31]]
|
|
|-
| [[Meeting_Notes_2014-12-24|2014-12-24]]
|
|
|-
| [[Meeting_Notes_2014-12-17|2014-12-17]]
|
|
|-
| [[Meeting_Notes_2014-12-10|2014-12-10]]
|
|
|-
| [[Meeting_Notes_2014-12-03|2014-12-03]]
|
|
|-
| [[Meeting_Notes_2014-11-26|2014-11-26]]
|
|
|-
| [[Meeting_Notes_2014-11-19|2014-11-19]]
|
|
|-
| [[Meeting_Notes_2014-11-12|2014-11-12]]
|
|
|-
| [[Meeting_Notes_2014-11-05|2014-11-05]]
|
|
|-
| [[Meeting_Notes_2014-10-29|2014-10-29]]
|
|
|-
| [[Meeting_Notes_2014-10-27|2014-10-27]]
|
| Board of Directors Meeting
|-
| [[Meeting_Notes_2014-10-22|2014-10-22]]
|
|
|-
| [[Meeting_Notes_2014-10-15|2014-10-15]]
|
|
|-
| [[Meeting_Notes_2014-10-08|2014-10-08]]
|
|
|-
| [[Meeting_Notes_2014-10-01|2014-10-01]]
|
|
|-
| [[Meeting_Notes_2014-09-24|2014-09-24]]
|
|
|-
| [[Meeting_Notes_2014-09-17|2014-09-17]]
|
|
|-
| [[Meeting_Notes_2014-09-10|2014-09-10]]
|
|
|-
| [[Meeting_Notes_2014-09-03|2014-09-03]]
|
|
|-
| [[Meeting_Notes_2014-08-27|2014-08-27]]
|
|
|-
| [[Meeting_Notes_2014-08-20|2014-08-20]]
|
|
|-
| [[Meeting_Notes_2014-08-13|2014-08-13]]
|
|
|-
| [[Meeting_Notes_2014-08-06|2014-08-06]]
|
|
|-
| [[Meeting_Notes_2014-07-30|2014-07-30]]
|
|
|-
| [[Meeting_Notes_2014-07-23|2014-07-23]]
|
|
|-
| [[Meeting_Notes_2014-07-16|2014-07-16]]
|
|
|-
| [[Meeting_Notes_2014-07-09|2014-07-09]]
|
|
|-
| [[Meeting_Notes_2014-07-02|2014-07-02]]
|
| First meeting in our new space @ 4799 Shattuck!
|-
| 2014-06-25
|
| big moving day, no meeting notes
|-
| [[Meeting_Notes_2014-06-18|2014-06-18]]
|
|
|-
| [[Meeting_Notes_2014-06-11|2014-06-11]]
|
|
|-
| [[Meeting_Notes_2014-06-04|2014-06-04]]
|
|
|-
| [[Meeting Notes 2014-05-28|2014-05-28]]
|
|
|-
| [[Meeting Notes 2014-05-21|2014-05-21]]
|
|
|-
| [[Meeting Notes 2014-05-14|2014-05-14]]
|
|
|-
| [[Meeting Notes 2014-05-07|2014-05-07]]
|
|
|-
| [[Meeting Notes 2014-04-30|2014-04-30]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-23|2014-04-23]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-16|2014-04-16]]
|
|
|-
| [[Meeting Notes 2014-04-09|2014-04-09]]
|
|
|-
| [[Meeting Notes 2014-04-02|2014-04-02]]
|
| mostly reboot
|-
| [[Meeting Notes 2014-03-26|2014-03-26]]
|
|
|-
| [[Meeting Notes 2014-03-19|2014-03-19]]
|
|
|-
| [[Meeting Notes 2014-03-12|2014-03-12]]
|
|
|-
| [[Meeting Notes 2014-03-05|2014-03-05]]
|
| Special edition on reboot
|-
| [[Meeting Notes 2014-02-26|2014-02-26]]
|
|
|-
| [[Meeting Notes 2014-02-19|2014-02-19]]
|
|
|-
| [[Meeting Notes 2014-02-12|2014-02-12]]
|
|
|-
| [[Meeting Notes 2014-02-05|2014-02-05]]
|
|
|-
| [[Meeting Notes 2014-01-29|2014-01-29]]
|
|
|-
| [[Meeting Notes 2014-01-22|2014-01-22]]
|
|
|-
| [[Meeting Notes 2014-01-15|2014-01-15]]
|
|
|-
| [[Meeting Notes 2014-01-08|2014-01-08]]
|
|
|-
| [[Meeting Notes 2014-01-01|2014-01-01]]
|
|
|-
| [[Meeting Notes 2013-12-25|2013-12-25]]
|
|
|-
| [[Meeting Notes 2013-12-18|2013-12-18]]
|
|
|-
| [[Meeting Notes 2013-12-11|2013-12-11]]
|
|
|-
| [[Meeting Notes 2013-12-04|2013-12-04]]
|
|
|-
| [[Meeting Notes 2013-11-27|2013-11-27]]
|
|
|-
| [[Meeting Notes 2013-11-20|2013-11-20]]
|
|
|-
| [[Meeting Notes 2013-11-13|2013-11-13]]
|
|
|-
| [[Meeting Notes 2013-11-06|2013-11-06]]
|
|
|-
| [[Meeting Notes 2013-10-30|2013-10-30]]
|
|
|-
| [[Meeting Notes 2013-10-23|2013-10-23]]
|
|
|-
| [[Meeting Notes 2013-10-16|2013-10-16]]
|
|
|-
| [[Meeting Notes 2013-10-02|2013-10-02]]
|
|
|-
| [[Meeting Notes 2013-09-25|2013-09-25]]
|
|
|-
| [[Meeting Notes 2013-09-18|2013-09-18]]
|
|
|-
| [[Meeting Notes 2013-09-11|2013-09-11]]
|
|
|-
| [[Meeting Notes 2013-09-04|2013-09-04]]
|
|
|-
| [[Meeting Notes 2013-08-28|2013-08-28]]
|
|
|-
| [[Meeting Notes 2013-08-21|2013-08-21]]
|
|
|-
| [[Meeting Notes 2013-08-14|2013-08-14]]
|
|
|-
| [[Meeting Notes 2013-08-07|2013-08-07]]
|
|
|-
| [[Meeting Notes 2013-07-30|2013-07-30]]
|
|
|-
| [[Meeting Notes 2013-07-24|2013-07-24]]
|
|
|-
| [[Meeting Notes 2013-07-17|2013-07-17]]
|
|
|-
| [[Meeting Notes 2013-07-10|2013-07-10]]
|
|
|-
| [[Meeting Notes 2013-07-03|2013-07-03]]
|
|
|-
| [[Meeting Notes 2013-06-26|2013-06-26]]
|
|
|-
| [[Meeting Notes 2013-06-19|2013-06-19]]
|
|
|-
| [[Meeting Notes 2013-06-12|2013-06-12]]
|
|
|-
| [[Meeting Notes 2013-06-05|2013-06-05]]
|
|
|-
| [[Meeting Notes 2013-05-29|2013-05-29]]
|
|
|-
| [[Meeting Notes 2013-05-22|2013-05-22]]
|
|
|-
| [[Meeting Notes 2013-05-15|2013-05-15]]
|
|
|-
| [[Meeting Notes 2013-05-08|2013-05-08]]
|
|
|-
| [[Meeting Notes 2013-05-01|2013-05-01]]
|
|
|-
| [[Meeting Notes 2013-04-24|2013-04-24]]
|
|
|-
| [[Meeting Notes 2013-04-17|2013-04-17]]
|
|
|-
| [[Meeting Notes 2013-04-11|2013-04-11]]
|
|
|-
| [[Meeting Notes 2013-04-03|2013-04-03]]
|
|
|-
| [[Meeting Notes 2013-03-27|2013-03-27]]
|
|
|-
| 2013-03-20
|
| no notes?
|-
| [[Meeting Notes 2013-03-13|2013-03-13]]
|
|
|-
| [[Meeting Notes 2013-03-06|2013-03-06]]
|
|
|-
| [[Meeting Notes 2013-02-27|2013-02-27]]
|
|
|-
| [[Meeting Notes 2013-02-20|2013-02-20]]
|
|
|-
| [[Meeting Notes 2013-02-13|2013-02-13]]
|
|
|-
| [[Meeting Notes 2013-02-06|2013-02-06]]
|
|
|-
| [[Meeting Notes 2013-01-30|2013-01-30]]
|
|
|-
| [[Meeting Notes 2013-01-23|2013-01-23]]
|
|
|-
| [[Meeting Notes 2013-01-16|2013-01-16]]
|
|
|-
| [[Meeting Notes 2013-01-09|2013-01-09]]
|
|
|-
| [[Meeting Notes 2013-01-02|2013-01-02]]
|
|
|-
| [[Sudo room/12-26-2012 Meetup|2012-12-26]]
|
|
|-
| [[Sudo room/12-19-2012 Meetup|2012-12-19]]
|
|
|-
| [[Sudo room/12-12-2012 Meetup|2012-12-12]]
|
|
|-
| [[Sudo room/12-05-2012 Meetup|2012-12-05]]
|
|
|-
| [[Sudo room/11-28-2012 Meetup|2012-11-28]]
|
|
|-
| [[Sudo room/11-21-2012 Meetup|2012-11-21]]
|
|
|-
| [[Sudo room/11-14-2012 Meetup|2012-11-14]]
|
|
|-
| [[Sudo room/11-7-2012 Meetup|2012-11-07]]
|
|
|-
| [[Sudo room/10-31-2012 Meetup|2012-10-31]]
|
|
|-
| [[Sudo room/10-24-2012 Meetup|2012-10-24]]
|
|
|-
| [[Sudo room/10-17-2012 Meetup|2012-10-17]]
|
|
|-
| [[Sudo room/10-10-2012 Meetup|2012-10-10]]
|
|
|-
| [[Sudo room/10-03-2012 Meetup|2012-10-03]]
|
|
|-
| [[Sudo room/09-26-2012 Meetup|2012-09-26]]
|
|
|-
| [[Sudo room/09-19-2012 Meetup|2012-09-19]]
|
|
|-
| [[Sudo room/09-12-2012 Meetup|2012-09-12]]
|
|
|-
| [[Sudo room/09-05-2012 Meetup|2012-09-05]]
|
|
|-
| [[Sudo room/08-29-2012 Meetup|2012-08-29]]
|
|
|-
| [[Sudo room/08-22-2012 Meetup|2012-08-22]]
|
|
|-
| [[Sudo room/08-13-2012 Meetup|2012-08-13]]
|
|
|-
| [[Sudo room/08-08-2012 Meetup|2012-08-08]]
|
|
|-
| [[Sudo room/08-01-2012 Meetup|2012-08-01]]
|
|
|-
| [[Sudo room/07-25-2012 Meetup|2012-07-25]]
|
|
|-
| [[Sudo room/07-18-2012 Meetup|2012-07-18]]
|
|
|-
| [[Sudo room/07-11-2012 Meetup|2012-07-11]]
|
|
|-
| [[Sudo room/07-04-2012 Meetup|2012-07-04]]
|
|
|-
| [[Sudo room/06-27-2012 Meetup|2012-06-27]]
|
|
|-
| [[Sudo room/06-20-2012 Meetup|2012-06-20]]
|
|
|-
| [[Sudo room/06-13-2012 Meetup|2012-06-13]]
|
|
|-
| [[Sudo room/06-06-2012 Meetup|2012-06-06]]
|
|
|-
| [[Sudo room/05-30-2012 Meetup|2012-05-30]]
|
|
|-
| [[Sudo room/05-23-2012 Meetup|2012-05-23]]
|
|
|-
| [[Sudo room/05-16-2012 Meetup|2012-05-16]]
|
|
|-
| 2012-05-09
|
| no notes?
|-
| 2012-05-02
|
| no notes?
|-
| [[Sudo room/04-25-2012 Meetup|2012-04-25]]
|
|
|-
| 2012-04-18
|
| no notes?
|-
| 2012-04-11
|
| no notes?
|-
| 2012-04-04
|
| no notes?
|-
| 2012-03-28
|
| no notes?
|-
| 2012-03-21
|
| no notes?
|-
| 2012-03-14
|
| no notes?
|-
| 2012-03-07
|
| no notes?
|-
| 2012-02-29
|
| no notes?
|-
| [[Sudo room/02-22-2012 Meetup|2012-02-22]]
|
|
|-
| 2012-02-15
|
| no notes?
|-
| 2012-02-08
|
| no notes?
|-
| [[Sudo room/02-01-2011 Meetup|2012-02-01]]
|
|
|-
| [[Sudo room/01-25-2011 Meetup|2012-01-25]]
|
|
|-
| [[Sudo room/01-18-2011 Meetup|2012-01-18]]
|
|
|-
| [[Sudo room/01-11-2011 Meetup|2012-01-11]]
|
|
|-
| [[Sudo room/01-04-2011 Meetup|2012-01-04]]
|
|
|-
| [[Sudo room/12-28-2011 Meetup|2011-12-28]]
|
|
|-
| [[Sudo room/12-21-2011 Meetup|2011-12-21]]
|
|
|-
| [[Sudo room/12-14-2011 Meetup|2011-12-14]]
|
|
|-
| [[Sudo room/12-07-2011 Meetup|2011-12-07]]
|
|
|-
| [[Sudo room/First Wed Meetup|2011-11-30]]
|
| @ Cafe Mediterraneum
|-
| [[Sudo room/Initial Meeting| Initial Meeting]]
|
| 2011-11-18, 12pm @ Actual Cafe
|}

[[Category:SudoRoom Organization]][[Category:Meetings]]

Meeting Notes 2026-02-29

2026-04-27T00:27:50Z

Jerkey: Jerkey moved page Meeting Notes 2026-02-29 to Meeting Notes 2026-03-29: typo its march 29 not feb 29

#REDIRECT [[Meeting Notes 2026-03-29]]

Meeting Notes 2026-03-29

2026-04-27T00:27:50Z

Jerkey: Jerkey moved page Meeting Notes 2026-02-29 to Meeting Notes 2026-03-29: typo its march 29 not feb 29

'''Sudo Room Meeting - 29 March 2026 7pm-9pm'''

= Meeting Details =

== Roles ==
* Facilitator/s:
* Stacktaker:
* Timekeeper:
* Notetaker/s: Paige

== Attendees ==
* Paige, Peter, Michael

= Agenda =

== Check member applications ==
* added Matthew to the kanban. No one here is able to check payments
* Michael - suggestion for the kanban - add a field that has a link to their application email

== Finances ==

Finances sheet: https://docs.google.com/spreadsheets/d/1wACIGBvBytdvL2eqh5MlLRCg1fpzSaA7SrQIw88OVZg/edit?gid=875560151#gid=875560151

* Paige - we have been scraping by to pay rent. From spreadsheet you can see our monthly donations are less than we owe in rent each month. So we've only been able to pay by using savings/ money from people who did their payment for the whole year. To make rent, we should get ~$300 more in recurring monthly payments.

== Taxes ==
* Paige - I think:
** IRS 990EZ is due May 15 https://www.irs.gov/charities-non-profits/return-due-dates-for-exempt-organizations-annual-return
** California Franchise Tax Board - FTB 199N (e-Postcard) - also due May 15?
** California Attorney General — Registry of Charities and Fundraisers?
* Michael - Can we get a deduction for VAT/sales tax for our spendings?

== Cleanup day ==
We should schedule one

Meeting Notes 2026-03-29

2026-04-27T00:26:55Z

Jerkey: 2026 not 2025

Stuff-org

2026-04-21T18:50:39Z

Jerkey:

== sudoroom uses stuff-org written by Henner Zeller to track stuff in the space (and in the community) ==
[[File:Noisebridge-stuff-org.png|thumb]]

* it is live and can be accessed from the local wifi/network at [https://stuff.sudoroom.org https://stuff.sudoroom.org]
* Noisebridge [https://parts.noisebridge.net runs a version of this] but you can only edit if you're on the local network
* [https://github.com/sudoroom/stuff-org/tree/sudoroom we use a fork of the main repository, branch "sudoroom"]
* we use [https://github.com/jerkey/websnap websnap] to update the images '''make sure this cant be abused from outside the network'''

== installation ==
* make a new user just for stuff-org and websnap
<pre>sudo adduser --disabled-password stuff --comment "stuff-org user"</pre>
* [https://go.dev/dl/ install golang] (as a user with sudo, not as user stuff)
<pre>
wget https://go.dev/dl/go1.24.1.linux-amd64.tar.gz # or current version
sudo tar -C /usr/local -xzf go1.24.1.linux-amd64.tar.gz
echo 'export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin' >> ~/.profile
echo 'export PATH=$PATH:/usr/local/go/bin' | sudo tee -a ~stuff/.profile
</pre>
* pull the repository, run make
sudo su stuff
source ~/.profile # idk why i had to do this to get golang to work
cd ; git clone https://github.com/sudoroom/stuff-org
cd stuff-org/stuff
git checkout sudoroom
make stuff
</pre>
* install nvm so we can have node
<pre>
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bash
exit
(now log back in)
nvm install --lts
</pre>
* install websnap (in home directory, not inside stuff-org)
<pre>
cd ; git clone https://github.com/sudoroom/websnap
cd websnap
npm install
</pre>

CHMT36

2026-04-18T19:46:09Z

Jerkey:

'''Pick and place machine for populating PCB's with surface mount components'''

2026/04/16: This machine has been reclaimed by its owner and is gone

RELATED: Sudoroom's 3D printer can dispense solder paste like this one did: https://hackaday.com/2014/04/02/dispensing-solder-paste-with-a-3d-printer/

See it in action: https://www.youtube.com/watch?v=uTxdMl-Mct4

So exciting! https://www.youtube.com/watch?v=AuNQKG_SQ30

...ask jake, miloh, or captain morgan for info on how to use.

or contact Nick Pisarro! who made badges on this machine (from Eagle projects I think)
https://www.instagram.com/p/B0w-RHLp08l/

Python to convert kicad pos files to pick and place csv files
https://github.com/sudoroom/pos2pickandplace

Program to use diptrace EDA with the CHMT36VA:
https://github.com/hydra/pnpconvert

Project in process being updated to make use of pick'n place [[LM1877]]

[[File:CHMT36-Setup.jpg|800px]]

[[User:Thex|â…©]] ([[User talk:Thex|talk]]) 14:23, 23 December 2017 (PST)

http://www.charmhigh-tech.com/sale-8208765-chmt36-smt-smd-led-pick-and-place-machine-29-feeders-high-speed.html

https://github.com/sparkfunX/Desktop-PickAndPlace-CHMT36VA

Manuals for our machine:
http://www.spaz.org/~jake/pnp/

Sparkfun post about a similar machine CHMT36VA which has vision (ours does not have vision):
https://www.sparkfun.com/sparkx/blog/2594

CHMT36

2026-04-15T18:26:54Z

Jerkey:

'''Pick and place machine for populating PCB's with surface mount components'''

RELATED: Sudoroom's 3D printer can dispense solder paste like this one did: https://hackaday.com/2014/04/02/dispensing-solder-paste-with-a-3d-printer/

See it in action: https://www.youtube.com/watch?v=uTxdMl-Mct4

So exciting! https://www.youtube.com/watch?v=AuNQKG_SQ30

...ask jake, miloh, or captain morgan for info on how to use.

or contact Nick Pisarro! who made badges on this machine (from Eagle projects I think)
https://www.instagram.com/p/B0w-RHLp08l/

Python to convert kicad pos files to pick and place csv files
https://github.com/sudoroom/pos2pickandplace

Program to use diptrace EDA with the CHMT36VA:
https://github.com/hydra/pnpconvert

Project in process being updated to make use of pick'n place [[LM1877]]

[[File:CHMT36-Setup.jpg|800px]]

[[User:Thex|â…©]] ([[User talk:Thex|talk]]) 14:23, 23 December 2017 (PST)

http://www.charmhigh-tech.com/sale-8208765-chmt36-smt-smd-led-pick-and-place-machine-29-feeders-high-speed.html

https://github.com/sparkfunX/Desktop-PickAndPlace-CHMT36VA

Manuals for our machine:
http://www.spaz.org/~jake/pnp/

Sparkfun post about a similar machine CHMT36VA which has vision (ours does not have vision):
https://www.sparkfun.com/sparkx/blog/2594

Stuff-org

2026-04-14T23:14:43Z

Jerkey:

== sudoroom uses stuff-org written by Henner Zeller to track stuff in the space (and in the community) ==
[[File:Noisebridge-stuff-org.png|thumb]]

* Noisebridge [https://parts.noisebridge.net runs a version of this] but you can only edit if you're on the local network
* [https://github.com/sudoroom/stuff-org/tree/sudoroom we use a fork of the main repository, branch "sudoroom"]
* we use [https://github.com/jerkey/websnap websnap] to update the images '''make sure this cant be abused from outside the network'''

== installation ==
* make a new user just for stuff-org and websnap
<pre>sudo adduser --disabled-password stuff --comment "stuff-org user"</pre>
* [https://go.dev/dl/ install golang] (as a user with sudo, not as user stuff)
<pre>
wget https://go.dev/dl/go1.24.1.linux-amd64.tar.gz # or current version
sudo tar -C /usr/local -xzf go1.24.1.linux-amd64.tar.gz
echo 'export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin' >> ~/.profile
echo 'export PATH=$PATH:/usr/local/go/bin' | sudo tee -a ~stuff/.profile
</pre>
* pull the repository, run make
sudo su stuff
source ~/.profile # idk why i had to do this to get golang to work
cd ; git clone https://github.com/sudoroom/stuff-org
cd stuff-org/stuff
git checkout sudoroom
make stuff
</pre>
* install nvm so we can have node
<pre>
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bash
exit
(now log back in)
nvm install --lts
</pre>
* install websnap (in home directory, not inside stuff-org)
<pre>
cd ; git clone https://github.com/sudoroom/websnap
cd websnap
npm install
</pre>

Stuff-org

2026-04-14T20:13:56Z

Jerkey:

Stuff-org

2026-04-14T19:18:40Z

Jerkey: Created page with "== sudoroom uses stuff-org written by Henner Zeller to track stuff in the space (and in the community) == thumb * Noisebridge [https://parts.noisebridge.net runs a version of this] but you can only edit if you're on the local network * [https://github.com/sudoroom/stuff-org/tree/sudoroom we use a fork of the main repository, branch "sudoroom"] * we use [https://github.com/jerkey/websnap websnap] to update the images '''make sure this c..."

File:Noisebridge-stuff-org.png

2026-04-14T19:11:19Z

Jerkey:

Gpubox

2026-02-19T00:31:36Z

Jerkey: /* IPMI Setup */

= Hosted Services =
{| class="wikitable"
|+ On gpubox
|-
! Hostname:Port !! Description
|-
| [https://gpubox.local:8006/ gpubox.local:8006] || Proxmox admin
|-
| [http://dockerhost.local:3000/ dockerhost.local:3000] || Open WebUI (to play with LLMs)
|-
| [https://ipmi-compute-2-171.local/ ipmi-compute-2-171.local] || IPMI
|}

= gpubox Setup =

== Bare Metal Configuration ==

=== IPMI Setup ===
* Access IPMI via <pre>ipmitool</pre> with hostname <pre>ipmi-compute-2-171.local</pre>

Example commands:
<pre>
$ ipmitool -H ipmi-compute-2-171.local -U ADMIN -P pwd power status
Chassis Power is on
$ ipmitool -H ipmi-compute-2-171.local -U ADMIN -P pwd dcmi power reading
[shows electrical power presently being consumed by system]
</pre>

Soft shutdown (all this is necessary or it will just reboot):
<pre>
#!/bin/bash
IPMICOMMAND="ipmitool -U ADMIN -P $(cat ipmipass) -H ipmi-compute-2-171"
$IPMICOMMAND power soft
timeout 15 bash -c "while $IPMICOMMAND power status | grep on ; do
sleep 0.5
done"
$IPMICOMMAND power off
</pre>

=== Debian 13 and Proxmox 8 Installation ===
* Debian 13 install: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-13.3.0-amd64-netinst.iso
* Proxmox VE on that: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie
* Let it use DHCP to grab an IP address, then I changed it later when I set up vrb0
* Hostname gpubox
* Proxmox web ui available at: https://gpubox.local:8006
* apt install earlyoom && sudo systemctl enable --now earlyoom # prevent system crashes due to running out of RAM

== GPU Passthrough Configuration ==

=== BIOS/UEFI ===
* Enable VT-d (Virtualization Technology for Directed I/O) in BIOS on gpubox

=== Identify GPUs ===
Use the vendor ID (`10de`) and device ID (`1b06`) to identify GPUs. Both video cards and their associated audio device will show up.

<pre>
$ lspci -nnk | grep -A 3 'VGA'
04:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] (rev a1)
Subsystem: NVIDIA Corporation Device [10de:12a4]
Kernel modules: nvidiafb, nouveau
04:00.1 Audio device [0403]: NVIDIA Corporation TU102 High Definition Audio Controller [10de:10f7] (rev a1)
--
05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: PNY Device [196e:1213]
Kernel modules: nvidiafb, nouveau
05:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
--
08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3609]
Kernel modules: nvidiafb, nouveau
08:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
--
09:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1470]
Kernel modules: nvidiafb, nouveau
09:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
--
0c:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30)
Subsystem: Super Micro Computer Inc Device [15d9:0892]
Kernel driver in use: ast
Kernel modules: ast
--
84:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] [10de:1e04] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device [1458:37c4]
Kernel modules: nvidiafb, nouveau
84:00.1 Audio device [0403]: NVIDIA Corporation TU102 High Definition Audio Controller [10de:10f7] (rev a1)
--
85:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1)
Subsystem: eVga.com. Corp. Device [3842:6180]
Kernel modules: nvidiafb, nouveau
85:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1)
--
88:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1470]
Kernel modules: nvidiafb, nouveau
88:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
--
89:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3609]
Kernel modules: nvidiafb, nouveau
89:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
</pre>

=== VFIO Modules ===
* Create `/etc/modules-load.d/vfio.conf` with:
<pre>
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
</pre>

== NVIDIA Drivers on Host ==
We did have to install some drivers on gpubox, but we installed them again later on the VMs. This confuses me.

=== Edit /etc/apt/sources.list ===
<pre>
sed -i 's/main/main non-free contrib/g' /etc/apt/sources.list
apt update
apt install -y nvidia-driver nvidia-kernel-dkms
</pre>

== VM Templates & Cloning ==

=== Template VM ===
* Upload <pre>debian-13.3.0-amd64-netinst.iso</pre> to storage through the proxmox web ui
* Create a minimal Debian 13 template
** <pre>apt install -y ufw fail2ban curl git zsh sudo net-tools</pre>
** <pre>sudo apt update && sudo apt full-upgrade -y</pre>
* Make a user called <pre>deb</pre> with sudo
* Convert to template (Proxmox: VM > Convert to Template) with name: <pre>debian13-template</pre>

=== Clone VMs ===
* Clone the template for <pre>ollama-2080</pre> and future VMs that will house AI models
* **Pass GPU**: In VM settings, go to "Hardware" > "PCI" > "Raw" and select the GPU (use <pre>lspci</pre> IDs)
* Don't forget to change the new cloned VM's hostname
** <pre>sudo hostnamectl set-hostname ollama2080 --static</pre>

== Specific VM Configurations ==

=== ollama-2080 ===
* Install nvidia drivers https://www.xda-developers.com/nvidia-stopped-supporting-my-gpu-so-i-started-self-hosting-llms-with-it/
** Pin the driver version so you don't have to re-run the nvidia installer every time the kernel gets updated
* Install ollama with <pre>curl -fsSL https://ollama.com/install.sh | sh</pre>
* Use ollama to pull and run deepseek-r1:8b
* <pre>sudo ufw allow from 10.0.0.0/24 to any port 11434 proto tcp</pre>
* Verify: http://ollama.local:11434/ should show the message <pre>Ollama is running.</pre>

=== imgtotext ===
* Install ollama as above
* <pre>ollama run hf.co/noctrex/ZwZ-8B-GGUF:Q8_0</pre> from the page https://huggingface.co/noctrex/ZwZ-8B-GGUF (i pressed the image-to-text tag and looked at trending models)
* http://imgtotext.local:11434/ should show ollama is running

=== dockerhost ===
* Install Docker:
```
apt install -y docker.io
systemctl enable --now docker
```
* Add user <pre>docker</pre> to do docker stuff. Do NOT give <pre>docker</pre> sudo.

==== Install openwebui ====
* As the docker user, make directories <pre>~/git/openwebui</pre>
* Make a docker compose file at <pre>~/git/openwebui/docker-compose.yaml</pre>
** <pre>services:
open-webui:
build:
context: .
dockerfile: Dockerfile
image: ghcr.io/open-webui/open-webui:${WEBUI_DOCKER_TAG-main}
container_name: open-webui
volumes:
- open-webui:/app/backend/data
ports:
- ${OPEN_WEBUI_PORT-3000}:8080
environment:
- 'OLLAMA_BASE_URL=http://ollama-2080.local:11434'
- 'WEBUI_SECRET_KEY=secretkeyhere'
extra_hosts:
- host.docker.internal:host-gateway
restart: unless-stopped

volumes:
open-webui: {}
</pre>
** Eventually, we'll check this in to git.
* In <pre>~/git/openwebui</pre>, run <pre>docker compose up</pre>
** Note: newer docker uses <pre>docker compose</pre>, not <pre>docker-compose</pre>
* I had to do some hole-punching in ufw to get open-webui to see ollama2080
* Useful commands
** <pre>sudo ss -plnt # Lists ports this machine is listening on
ip -4 a # Get this machine's IP address on the local network
</pre>

=== ai-conductor ===
* TBD

=== if you're using a 1080 Ti or 1080 ===
<pre>sudo apt purge "*nvidia*"
sudo apt autoremove --purge
</pre>
then reboot.

== Key Commands ==

```
# Check GPU visibility in host
lspci -k | grep -A 2 "VGA"

# Verify VFIO modules loaded
lsmod | grep vfio

# Test NVIDIA driver
nvidia-smi # Should show GPU details

# Clone a template in Proxmox
qm clone <source_VM_ID> <new_VM_ID> --name "ollama-2080"
```

== Troubleshooting ==

* **GPU Not Visible**: Ensure VT-d is enabled in BIOS and the GPU is listed in `lspci`
* **Driver Issues**: Reinstall `nvidia-driver` and reboot
* **Permission Errors**: Add user to `docker` and `kvm` groups

Gpubox

2026-02-18T23:55:32Z

Jerkey: /* Bare Metal Configuration */

= Hosted Services =
{| class="wikitable"
|+ On gpubox
|-
! Hostname:Port !! Description
|-
| [https://gpubox.local:8006/ gpubox.local:8006] || Proxmox admin
|-
| [http://dockerhost.local:3000/ dockerhost.local:3000] || Open WebUI (to play with LLMs)
|-
| [https://ipmi-compute-2-171.local/ ipmi-compute-2-171.local] || IPMI
|}

= gpubox Setup =

== Bare Metal Configuration ==

=== IPMI Setup ===
* Access IPMI via <pre>ipmitool</pre> with hostname <pre>ipmi-compute-2-171.local</pre>

Example commands:
<pre>
$ ipmitool -H ipmi-compute-2-171.local -U ADMIN -P pwd power status
Chassis Power is on
$ ipmitool -H ipmi-compute-2-171.local -U ADMIN -P pwd dcmi power reading
[shows electrical power presently being consumed by system]
</pre>

=== Debian 13 and Proxmox 8 Installation ===
* Debian 13 install: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-13.3.0-amd64-netinst.iso
* Proxmox VE on that: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie
* Let it use DHCP to grab an IP address, then I changed it later when I set up vrb0
* Hostname gpubox
* Proxmox web ui available at: https://gpubox.local:8006
* apt install earlyoom && sudo systemctl enable --now earlyoom # prevent system crashes due to running out of RAM

== GPU Passthrough Configuration ==

=== BIOS/UEFI ===
* Enable VT-d (Virtualization Technology for Directed I/O) in BIOS on gpubox

=== Identify GPUs ===
Use the vendor ID (`10de`) and device ID (`1b06`) to identify GPUs. Both video cards and their associated audio device will show up.

<pre>
$ lspci -nnk | grep -A 3 'VGA'
04:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] (rev a1)
Subsystem: NVIDIA Corporation Device [10de:12a4]
Kernel modules: nvidiafb, nouveau
04:00.1 Audio device [0403]: NVIDIA Corporation TU102 High Definition Audio Controller [10de:10f7] (rev a1)
--
05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: PNY Device [196e:1213]
Kernel modules: nvidiafb, nouveau
05:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
--
08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3609]
Kernel modules: nvidiafb, nouveau
08:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
--
09:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1470]
Kernel modules: nvidiafb, nouveau
09:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
--
0c:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30)
Subsystem: Super Micro Computer Inc Device [15d9:0892]
Kernel driver in use: ast
Kernel modules: ast
--
84:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] [10de:1e04] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device [1458:37c4]
Kernel modules: nvidiafb, nouveau
84:00.1 Audio device [0403]: NVIDIA Corporation TU102 High Definition Audio Controller [10de:10f7] (rev a1)
--
85:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1)
Subsystem: eVga.com. Corp. Device [3842:6180]
Kernel modules: nvidiafb, nouveau
85:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1)
--
88:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1470]
Kernel modules: nvidiafb, nouveau
88:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
--
89:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3609]
Kernel modules: nvidiafb, nouveau
89:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
</pre>

=== VFIO Modules ===
* Create `/etc/modules-load.d/vfio.conf` with:
<pre>
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
</pre>

== NVIDIA Drivers on Host ==
We did have to install some drivers on gpubox, but we installed them again later on the VMs. This confuses me.

=== Edit /etc/apt/sources.list ===
<pre>
sed -i 's/main/main non-free contrib/g' /etc/apt/sources.list
apt update
apt install -y nvidia-driver nvidia-kernel-dkms
</pre>

== VM Templates & Cloning ==

=== Template VM ===
* Upload <pre>debian-13.3.0-amd64-netinst.iso</pre> to storage through the proxmox web ui
* Create a minimal Debian 13 template
** <pre>apt install -y ufw fail2ban curl git zsh sudo net-tools</pre>
** <pre>sudo apt update && sudo apt full-upgrade -y</pre>
* Make a user called <pre>deb</pre> with sudo
* Convert to template (Proxmox: VM > Convert to Template) with name: <pre>debian13-template</pre>

=== Clone VMs ===
* Clone the template for <pre>ollama-2080</pre> and future VMs that will house AI models
* **Pass GPU**: In VM settings, go to "Hardware" > "PCI" > "Raw" and select the GPU (use <pre>lspci</pre> IDs)
* Don't forget to change the new cloned VM's hostname
** <pre>sudo hostnamectl set-hostname ollama2080 --static</pre>

== Specific VM Configurations ==

=== ollama-2080 ===
* Install nvidia drivers https://www.xda-developers.com/nvidia-stopped-supporting-my-gpu-so-i-started-self-hosting-llms-with-it/
** Pin the driver version so you don't have to re-run the nvidia installer every time the kernel gets updated
* Install ollama with <pre>curl -fsSL https://ollama.com/install.sh | sh</pre>
* Use ollama to pull and run deepseek-r1:8b
* <pre>sudo ufw allow from 10.0.0.0/24 to any port 11434 proto tcp</pre>
* Verify: http://ollama.local:11434/ should show the message <pre>Ollama is running.</pre>

=== imgtotext ===
* Install ollama as above
* <pre>ollama run hf.co/noctrex/ZwZ-8B-GGUF:Q8_0</pre> from the page https://huggingface.co/noctrex/ZwZ-8B-GGUF (i pressed the image-to-text tag and looked at trending models)
* http://imgtotext.local:11434/ should show ollama is running

=== dockerhost ===
* Install Docker:
```
apt install -y docker.io
systemctl enable --now docker
```
* Add user <pre>docker</pre> to do docker stuff. Do NOT give <pre>docker</pre> sudo.

==== Install openwebui ====
* As the docker user, make directories <pre>~/git/openwebui</pre>
* Make a docker compose file at <pre>~/git/openwebui/docker-compose.yaml</pre>
** <pre>services:
open-webui:
build:
context: .
dockerfile: Dockerfile
image: ghcr.io/open-webui/open-webui:${WEBUI_DOCKER_TAG-main}
container_name: open-webui
volumes:
- open-webui:/app/backend/data
ports:
- ${OPEN_WEBUI_PORT-3000}:8080
environment:
- 'OLLAMA_BASE_URL=http://ollama-2080.local:11434'
- 'WEBUI_SECRET_KEY=secretkeyhere'
extra_hosts:
- host.docker.internal:host-gateway
restart: unless-stopped

volumes:
open-webui: {}
</pre>
** Eventually, we'll check this in to git.
* In <pre>~/git/openwebui</pre>, run <pre>docker compose up</pre>
** Note: newer docker uses <pre>docker compose</pre>, not <pre>docker-compose</pre>
* I had to do some hole-punching in ufw to get open-webui to see ollama2080
* Useful commands
** <pre>sudo ss -plnt # Lists ports this machine is listening on
ip -4 a # Get this machine's IP address on the local network
</pre>

=== ai-conductor ===
* TBD

=== if you're using a 1080 Ti or 1080 ===
<pre>sudo apt purge "*nvidia*"
sudo apt autoremove --purge
</pre>
then reboot.

== Key Commands ==

```
# Check GPU visibility in host
lspci -k | grep -A 2 "VGA"

# Verify VFIO modules loaded
lsmod | grep vfio

# Test NVIDIA driver
nvidia-smi # Should show GPU details

# Clone a template in Proxmox
qm clone <source_VM_ID> <new_VM_ID> --name "ollama-2080"
```

== Troubleshooting ==

* **GPU Not Visible**: Ensure VT-d is enabled in BIOS and the GPU is listed in `lspci`
* **Driver Issues**: Reinstall `nvidia-driver` and reboot
* **Permission Errors**: Add user to `docker` and `kvm` groups

TAZ 4

2026-02-15T04:08:08Z

Jerkey:

Sudoroom has a TAZ 4 3d printer, that was donated in 2022. It should not be confused with the older [[TAZ|TAZ 3]] 3d printer, which didn't work very well as a 3D printer.

According [https://download.lulzbot.com/TAZ/4.0/documentation/current/manual/TAZ_4_Manual.pdf PDF Manual for the TAZ 4] <big>'''the Nozzle diameter is 0.35mm'''</big> (same as the TAZ3 which our extruder is from)

<big>'''This printer's extruder is setup to use 3mm diameter filament'''</big>, which is usually set as 2.85mm in the slicer. The manual says "it is highly recommended to take multiple measurements from along a length of the filament and use the average." but trial and error is probably more effective to find the right value.

<big>'''Print volume is X: 298 by Y: 275 by Z: 250 '''</big>according to [https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/Marlin_TAZ4_1.0.0.1/Marlin/Configuration.h Configuration.h] in the firmware

[https://download.lulzbot.com/TAZ/4.0/ All files for the TAZ 4 from Lulzbot corporation]

<big>'''The following "start code" (set up in the slicer's printer profile) should be used with this printer in order to properly set extruder motor current:
<code>M907 E150</code>'''</big>

If we recompile the [https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/ firmware] we can put the correct default values for extruder motor current but that would be hard to do.

[[File:720px-Rambo-conn-all.jpg|thumb]]
The extruder head from the TAZ 3 was transferred onto the TAZ 4 which will presumably make a better 3D printer. The TAZ 3 will be converted for solder paste dispensing only
[[File:Taz4-3d-printer.jpg|720px]]

The TAZ 4 uses an [https://reprap.org/wiki/Rambo Ultimachine Rambo 1.3L main board] and here is the correct [[File:RAMBo_1.3L_Schematic.pdf|RAMBo_1.3L_Schematic]]
The original 14-pin "Extruder 0" connector on the TAZ4 was removed from "Aux Power Mosfet Output" (pins 5/red,6/black), E0 Heat (pins 12,13), E0 Fan (9/black,10/red) and Ground (pin 2), and E0 (3,7,11,14). The extruder harness from the TAZ3 was installed in it.

The TAZ 4 didn't work because both Fuse F2 and F3 on the RAMBO main board were missing. They're supposed to be [https://www.littelfuse.com/products/fuse-blocks-fuseholders-and-fuse-accessories/fuse-blocks/154.aspx Littelfuse OMNI-BLOK 154 series] and we didn't have any, so I stuck 5-amp [https://www.digikey.com/en/products/detail/littelfuse-inc/0466005-NR/521341 F1460CT-ND] in there since we have dozens of them in the FUSES bin: [[Image:Taz4_fuse_kludge.jpg|thumb|left]]

After installing the TAZ3 extruder, its motor was mostly skipping. The current needed to be adjusted. There are no tiny potentiometers to adjust on this RAMBO board, only a "digipot", which is controlled with the [https://marlinfw.org/docs/gcode/M907.html M907 command]

the default values are found in
[https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/Marlin_TAZ4_1.0.0.1/Marlin/Configuration_adv.h Configuration_adv.h]:<code>#define DIGIPOT_MOTOR_CURRENT {175,175,240,135,135} // Values 0-255 (RAMBO 135 = ~0.75A, 185 = ~1A)

pins.h:#define DIGIPOT_CHANNELS {4,5,3,0,1} // X Y Z E0 E1 digipot channels to stepper driver mapping</code>

TAZ 4

2026-02-15T04:02:18Z

Jerkey:

Sudoroom has a TAZ 4 3d printer, that was donated in 2022. It should not be confused with the older [[TAZ|TAZ 3]] 3d printer, which didn't work very well as a 3D printer.

According [https://download.lulzbot.com/TAZ/4.0/documentation/current/manual/TAZ_4_Manual.pdf PDF Manual for the TAZ 4] the Nozzle diameter is 0.35mm (same as the TAZ3 which our extruder is from)

Print volume is X: 298 by Y: 275 by Z: 250 according to [https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/Marlin_TAZ4_1.0.0.1/Marlin/Configuration.h Configuration.h] in the firmware

[https://download.lulzbot.com/TAZ/4.0/ All files for the TAZ 4 from Lulzbot corporation]

<big>'''The following "start code" (set up in the slicer's printer profile) should be used with this printer in order to properly set extruder motor current:
<code>M907 E150</code>'''</big>

If we recompile the [https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/ firmware] we can put the correct default values for extruder motor current but that would be hard to do.

[[File:720px-Rambo-conn-all.jpg|thumb]]
The extruder head from the TAZ 3 was transferred onto the TAZ 4 which will presumably make a better 3D printer. The TAZ 3 will be converted for solder paste dispensing only
[[File:Taz4-3d-printer.jpg|720px]]

The TAZ 4 uses an [https://reprap.org/wiki/Rambo Ultimachine Rambo 1.3L main board] and here is the correct [[File:RAMBo_1.3L_Schematic.pdf|RAMBo_1.3L_Schematic]]
The original 14-pin "Extruder 0" connector on the TAZ4 was removed from "Aux Power Mosfet Output" (pins 5/red,6/black), E0 Heat (pins 12,13), E0 Fan (9/black,10/red) and Ground (pin 2), and E0 (3,7,11,14). The extruder harness from the TAZ3 was installed in it.

The TAZ 4 didn't work because both Fuse F2 and F3 on the RAMBO main board were missing. They're supposed to be [https://www.littelfuse.com/products/fuse-blocks-fuseholders-and-fuse-accessories/fuse-blocks/154.aspx Littelfuse OMNI-BLOK 154 series] and we didn't have any, so I stuck 5-amp [https://www.digikey.com/en/products/detail/littelfuse-inc/0466005-NR/521341 F1460CT-ND] in there since we have dozens of them in the FUSES bin: [[Image:Taz4_fuse_kludge.jpg|thumb|left]]

After installing the TAZ3 extruder, its motor was mostly skipping. The current needed to be adjusted. There are no tiny potentiometers to adjust on this RAMBO board, only a "digipot", which is controlled with the [https://marlinfw.org/docs/gcode/M907.html M907 command]

the default values are found in
[https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/Marlin_TAZ4_1.0.0.1/Marlin/Configuration_adv.h Configuration_adv.h]:<code>#define DIGIPOT_MOTOR_CURRENT {175,175,240,135,135} // Values 0-255 (RAMBO 135 = ~0.75A, 185 = ~1A)

pins.h:#define DIGIPOT_CHANNELS {4,5,3,0,1} // X Y Z E0 E1 digipot channels to stepper driver mapping</code>

TAZ 4

2026-02-15T03:56:23Z

Jerkey:

Sudoroom has a TAZ 4 3d printer, that was donated in 2022. It should not be confused with the older [[TAZ|TAZ 3]] 3d printer, which didn't work very well as a 3D printer.

According [https://download.lulzbot.com/TAZ/4.0/documentation/current/manual/TAZ_4_Manual.pdf PDF Manual for the TAZ 4] the Nozzle diameter is 0.35mm (same as the TAZ3 which our extruder is from) and the bed size is X: 298 by Y: 280

[https://download.lulzbot.com/TAZ/4.0/ All files for the TAZ 4 from Lulzbot corporation]

<big>'''The following "start code" (set up in the slicer's printer profile) should be used with this printer in order to properly set extruder motor current:
<code>M907 E150</code>'''</big>

If we recompile the [https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/ firmware] we can put the correct default values for extruder motor current but that would be hard to do.

[[File:720px-Rambo-conn-all.jpg|thumb]]
The extruder head from the TAZ 3 was transferred onto the TAZ 4 which will presumably make a better 3D printer. The TAZ 3 will be converted for solder paste dispensing only
[[File:Taz4-3d-printer.jpg|720px]]

The TAZ 4 uses an [https://reprap.org/wiki/Rambo Ultimachine Rambo 1.3L main board] and here is the correct [[File:RAMBo_1.3L_Schematic.pdf|RAMBo_1.3L_Schematic]]
The original 14-pin "Extruder 0" connector on the TAZ4 was removed from "Aux Power Mosfet Output" (pins 5/red,6/black), E0 Heat (pins 12,13), E0 Fan (9/black,10/red) and Ground (pin 2), and E0 (3,7,11,14). The extruder harness from the TAZ3 was installed in it.

The TAZ 4 didn't work because both Fuse F2 and F3 on the RAMBO main board were missing. They're supposed to be [https://www.littelfuse.com/products/fuse-blocks-fuseholders-and-fuse-accessories/fuse-blocks/154.aspx Littelfuse OMNI-BLOK 154 series] and we didn't have any, so I stuck 5-amp [https://www.digikey.com/en/products/detail/littelfuse-inc/0466005-NR/521341 F1460CT-ND] in there since we have dozens of them in the FUSES bin: [[Image:Taz4_fuse_kludge.jpg|thumb|left]]

After installing the TAZ3 extruder, its motor was mostly skipping. The current needed to be adjusted. There are no tiny potentiometers to adjust on this RAMBO board, only a "digipot", which is controlled with the [https://marlinfw.org/docs/gcode/M907.html M907 command]

the default values are found in
<code>Configuration_adv.h:#define DIGIPOT_MOTOR_CURRENT {175,175,240,135,135} // Values 0-255 (RAMBO 135 = ~0.75A, 185 = ~1A)

pins.h:#define DIGIPOT_CHANNELS {4,5,3,0,1} // X Y Z E0 E1 digipot channels to stepper driver mapping</code>

CommunityInfra

2026-01-30T08:53:11Z

Jerkey: /* Hosted Services */

This page contains the description of the existing infra + information on ongoing experiments with hardware and software.
Like any other hackerspace, Sudoroom has its own rack.

== Rack ==

What is currently hosted at the space:

* DHCP server
* IP Phone
* Door server
* Experimental server (host: chocolate factory)

== Hosted Services ==

[[User: Unixjazz]] went to a chocolate factory in the city and rescued an HP server in excellent shape.
He fixed the controller, wiped the disks, updated firmwares, and installed the necessary software for self-hosting experiments at Sudoroom.
Below you will find information about the specs and what is currently running.

'''HP Proliant ML350p Gen8'''
* 2x E5-2690 2.9Ghz 20M Cache, 8.00 GT/s Intel® QPI – 8 Core Processors
* 256GB 12800R ECC RAM
* 3x 1TB SATA (7200) disks
* 1x HP P420i RAID Controller
* 2x 750W Power Supply
* iLO v2.82 (note: [https://www.reddit.com/r/sysadmin/comments/uw3avd/hp_proliants_ilo_4_reporting_issues_with_embedded/ "iLO Self-Test reports a problem with Embedded Flash/SD-CARD" this is a known hardware aging issue. Firmware updates and formatting can help temporarily, but long-term reliability requires board or chip replacement])

=== Server: Chocolate factory ===

You can spin our own services / VMs / containers with Proxmox.

{| class="wikitable"
|+ Machines
|-
! Host !! MAC !! IP: Port
|-
| chocolate-factory || 9C:8E:99:65:60:88 || 100.64.66.229
|-
| wireguard || bc:24:11:ad:4d:b5 || 100.64.66.248
|-
| openwebui || BC:24:11:79:07:94 || 100.64.66.25:8080
|}

=== Hosted services ===

Here are some of the services running now. The host is always available for everyone to play with. Get your credentials with [[User:Jake]], LF, Ivan and others at the space (in person). No services will be made available to the outside world (public inet). Wireguard access can be provided, though, if you are not physically at the space.

{| class="wikitable"
|+ Hosted services
|-
! IP:Port !! Description
|-
| 100.64.66.248:51820 || Wireguard server (on LXC)
|-
| 100.64.66.248:10086 || Wireguard admin (to create accounts)
|-
| 100.64.66.229:8006 || Proxmox admin (to manage the server)
|-
| 100.64.66.25:8080 || Language model server (to play with LLMs)
|}

=== Wishlist ===

* Get an older PCI Express GPU for speeding up the experiments with the local language models (for coding)
* Install Jitsi with automatic audio translation / caption and auth

=== Reminder ===

'''Do not run anything sensitive on this machine. No passwords, no personal info, nothing.'''

This is a sandbox machine without backup. It can and will break and change frequently.

The information about any updates will be posted here, however.

'''Enjoy !'''

Creality Ender-3 S1

2026-01-16T22:17:23Z

Jerkey: /* Overview */

==Overview==
'''Printer Name:''' Creality Ender-3 S1

'''Preferred Slicer:''' Orca Slicer

'''Nozzle:''' 0.4mm

'''Bed Type:''' Textured PEI Plate

'''Filament:''' PLA

'''Octoprint:''' http://100.64.64.197/ (this will only work if you're on the local network / wifi)

==Status==
Working as of 11/19/2025

==Printing Tips==
Use 0.20 Standard slice profile

==Documentation==
* [https://wiki.creality.com/en/ender-series Creality Wiki]

==Maintenance Log==
Levelled bed on 11/19/2025

Printing

2026-01-16T05:36:26Z

Jerkey:

= Overview =

= 3D printing =
[[File:Dual_printers.jpg|right|frameless|200px]]
Yes, we have 3D printers!

Tuesdays is our 3D-printing hack night. Please join us!

Check out our [[3D_Modeling|intro to 3D modeling]] and our [[Print_Gallery|gallery of prints]]!

== Working 3D Printers ==

* [[TAZ 4]] not to be confused with [[TAZ|TAZ3 which we no longer have]]
* [[Creality Ender-3 S1]]
* a Bambu on loan from A.

[[File:Seckit-go2.jpg|thumb|right|200px|Custom 3d Printer|link=Custom_3D_Printer]]

[[File:Image_10-17-23_at_7.51_PM.png |thumb|right|200px|link=Artillery_Sidewinder_X2| Artillery Sidewinder X2]]

[[File:3D Printing Dogs.png|printing more SudoKits with the 3D printer]]

== NON-working 3D Printers ==

* [[Artillery_Sidewinder_X2| Artillery Sidewinder X2]]
* [[Monoprice Mini V1]]
* [[Monoprice MP10]]
* [[Custom_3D_Printer]]
* [[Prusa Mini+|Prusa Mini+ was bought by an Octopus]]

= Laser and Inkjet =

* Black and white laser printer over the sewing area.
* Canon Pixma printer: [[CanonTS700]]
** it can print on regular paper, but its main purpose is to print on high-quality glossy paper and plastic.
** it can print on ID card-like material (small plastic cards)

= Other =

There is a [[Label_printer|Label printer]] connected to the [[Space_Server|Space server]] laptop.

Our [[CNC|CNC Mill]] is sorta like a "wood printer".

Printers that aren't at Sudo anymore:
* [[Brother_DCP-7020|Brother DCP-7020 laser printer]]
* [[Magicolor_2530DL|Konica Minolta Magicolor 2530DL]]
*[[Xerox Phaser 7400]] 12"x18" Color Laser for making color wax prints including [https://spaz.org/~jake/pyralux flexible circuitboards]
[[File:Xerox_Phaser_8500.jpg|thumb|Xerox_Phaser_8500.jpg]]
* A [[Type_A_Machine| Type-A Machine]]

[[Category:Tools]]

Printing

2026-01-16T05:35:50Z

Jerkey:

= Overview =

= 3D printing =
[[File:Dual_printers.jpg|right|frameless|200px]]
Yes, we have 3D printers!

Tuesdays is our 3D-printing hack night. Please join us!

Check out our [[3D_Modeling|intro to 3D modeling]] and our [[Print_Gallery|gallery of prints]]!

== Working 3D Printers ==

* [[TAZ 4]] not to be confused with [[TAZ|TAZ3 which we no longer have]]
* [[Creality Ender-3 S1]]
* a Bambu on loan from A.
* [[Prusa Mini+|Prusa Mini+ (bought by an Octopus)]]

[[File:Seckit-go2.jpg|thumb|right|200px|Custom 3d Printer|link=Custom_3D_Printer]]

[[File:Image_10-17-23_at_7.51_PM.png |thumb|right|200px|link=Artillery_Sidewinder_X2| Artillery Sidewinder X2]]

[[File:3D Printing Dogs.png|printing more SudoKits with the 3D printer]]

== NON-working 3D Printers ==

* [[Artillery_Sidewinder_X2| Artillery Sidewinder X2]]
* [[Monoprice Mini V1]]
* [[Monoprice MP10]]
* [[Custom_3D_Printer]]

= Laser and Inkjet =

* Black and white laser printer over the sewing area.
* Canon Pixma printer: [[CanonTS700]]
** it can print on regular paper, but its main purpose is to print on high-quality glossy paper and plastic.
** it can print on ID card-like material (small plastic cards)

= Other =

There is a [[Label_printer|Label printer]] connected to the [[Space_Server|Space server]] laptop.

Our [[CNC|CNC Mill]] is sorta like a "wood printer".

Printers that aren't at Sudo anymore:
* [[Brother_DCP-7020|Brother DCP-7020 laser printer]]
* [[Magicolor_2530DL|Konica Minolta Magicolor 2530DL]]
*[[Xerox Phaser 7400]] 12"x18" Color Laser for making color wax prints including [https://spaz.org/~jake/pyralux flexible circuitboards]
[[File:Xerox_Phaser_8500.jpg|thumb|Xerox_Phaser_8500.jpg]]
* A [[Type_A_Machine| Type-A Machine]]

[[Category:Tools]]

Printing

2026-01-16T05:34:11Z

Jerkey:

= Overview =

= 3D printing =
[[File:Dual_printers.jpg|right|frameless|200px]]
Yes, we have 3D printers!

Tuesdays is our 3D-printing hack night. Please join us!

Check out our [[3D_Modeling|intro to 3D modeling]] and our [[Print_Gallery|gallery of prints]]!

== Working 3D Printers ==

* [[TAZ 4]] not to be confused with [[TAZ|TAZ3 which we no longer have]]
* [[Creality Ender-3 S1]]
* a Bambu on loan from A.
* [[Prusa Mini+|Prusa Mini+ (bought by an Octopus)]]

[[File:Seckit-go2.jpg|thumb|right|200px|Custom 3d Printer|link=Custom_3D_Printer]]

[[File:Image_10-17-23_at_7.51_PM.png |thumb|right|200px|link=Artillery_Sidewinder_X2| Artillery Sidewinder X2]]

[[File:3D Printing Dogs.png|printing more SudoKits with the 3D printer]]

== NON-working 3D Printers ==

* [[Artillery_Sidewinder_X2| Artillery Sidewinder X2]]
* [[Monoprice Mini V1]]
* [[Monoprice MP10]]
* [[Custom_3D_Printer]]
* the old [[TAZ]], that should not be confused with the [[TAZ 4]]

= Laser and Inkjet =

* Black and white laser printer over the sewing area.
* Canon Pixma printer: [[CanonTS700]]
** it can print on regular paper, but its main purpose is to print on high-quality glossy paper and plastic.
** it can print on ID card-like material (small plastic cards)

= Other =

There is a [[Label_printer|Label printer]] connected to the [[Space_Server|Space server]] laptop.

Our [[CNC|CNC Mill]] is sorta like a "wood printer".

Printers that aren't at Sudo anymore:
* [[Brother_DCP-7020|Brother DCP-7020 laser printer]]
* [[Magicolor_2530DL|Konica Minolta Magicolor 2530DL]]
*[[Xerox Phaser 7400]] 12"x18" Color Laser for making color wax prints including [https://spaz.org/~jake/pyralux flexible circuitboards]
[[File:Xerox_Phaser_8500.jpg|thumb|Xerox_Phaser_8500.jpg]]
* A [[Type_A_Machine| Type-A Machine]]

[[Category:Tools]]

Artillery Sidewinder X2

2026-01-16T04:32:20Z

Jerkey:

[[File:Image_10-17-23_at_7.51_PM.png |thumb|right|200px|link=Artillery_Sidewinder_X2]]
==Status==

The printer is not working (July 12th 2025) -- see log below.

==Printing Tips==

* Occasionally (twice in ~20 jobs) this printer will go nuts while homing at the beginning of a print, and try to drive way out of bounds. It might (low confidence) ameliorate this to manually home from the menu each time before starting a job. Definitely watch it closely when starting a print, and be ready to shut it off.
* This printer works great with '''PLA''' filament. It should be '''1.75mm''' diameter. If you find a spool that has both of those on the label, very likely to work. As of 9/2024 there is a small blue spool floating around that definitely works.
* Small spools can hang off the clamp stuck on top the right support. 1KG and larger spools feed better from the built-in holder center-top, but you may need to adjust it to the correct width for the spool. The hex key needed to adjust the bracket should be in the "Tools" drawer next to the printer.
* The stock [https://github.com/prusa3d/PrusaSlicer PrusaSlicer] profiles for the Artillery X1 w/ Generic PLA seem to work pretty well. The Generic PETG profiles '''DO NOT''' work great with this printer; see below.

===PETG Printing===

[[File:Artillery-petg-settings.png|thumb]]

The attached screenshot shows some overrides for PETG printing.

The problems these are trying to solve are:
* Poor bed adhesion -- this is solved by the higher bed and first layer nozzle temps.
* Warping of long parts -- this is mostly solved by the high bed temp and disabling the fan; things cool slower and warp less.
* Stringy ooze everywhere -- this is vastly improved by the travel ramping mode, except in specific print areas where it's ineffective. Note that lower angles seemed to cause problems with colliding/dragging the print. Increasing the default retraction length did not help. Decreasing the non-first layer nozzle temp back to default or below might help.

==Documentation==

* [https://drive.google.com/file/d/1TL4KopbNGSTsDXNVoZi5nVtGNxXNqac4/view X2 Manual] -- note this may be an X1 not an X2. Couldn't find a currently working link to X1 manual.
* [https://www.youtube.com/watch?v=cHx3AgoPaG8 Bed leveling procedure]
** Leveling with the bed at print temperature will be more accurate; heating the extruder may help too, but not to full print temp because then it will drool and stick to the paper. BE CAREFUL, these things get very hot!
** You can test the leveling with this file: [[File:Bed_level.stl]].
** That's generated using [https://www.thingiverse.com/thing:34558/files this parametric design].

[[Category:3DPrinting]]

==Maintenance Log==

'''2025'''

;July 12
Problem with one of the axes not moving. CC ordered new motor driver, and someone ordered a new ribbon cable according to note on printer.

;April 10th (Kirk S)
Installed new 0.4 mm brass nozzle

'''2024'''

;Sep 14th (Chris W)
The printer went crazy while homing and made a big gouge in the bed. After rebooting, I did a very quick relevel and a few minutes of test printing, which seemed to go fine; but didn't have time for a thorough checkout. Recommend doing a careful leveling and test print before any big jobs.

;Sep 9th (Chris W)
Releveled the bed with things hot; first layers look even neater now, except out in the very corners, past the leveling zones; those seem to slope up a bit, so the first layer gets really thin out there.

;Sep 3rd (Chris W)
Did a bed leveling and getting MUCH better first-layer adhesion now. Results are still a little weird on my actual prints in the front-right corner, IDK what's up with that but problem seems mostly cosmetic now.

;Sep 1st (Chris W)
Had a print come loose from the bed several layers in, made a big mess and got some crap wrapped around the X axis driver. Once I got it cleaned out, it was clear it had screwed up the belt tension. I was able to retension the belt and it seems file now, though; a printed square peg still fits into a square hole both ways with the same tolerance as before. But if there are future X-calibration issues, might be the belt is damaged and needs replacing. I left the allen wrench I found for the tension adjustment in the tool drawer.

'''2023'''

Jake bought a new nozzle kit for it and it's been installed by Tim and is working great.

the new nozzle kit was https://www.ebay.com/itm/385701967616
"3D Printer Hotend Silicone Sleeve Repair Kit for Artillery Sidewinder X1"
$12.99 from bargainsofmaine (51,200) 99.9%

Network

2026-01-08T08:23:44Z

Jerkey: /* LAN */

__NOTOC__
''For more information about sudo room's systems in general, see [[Systems Administration]]''

The sudo room '''network''' provides internal networking, internet access, wireless service, and some externally accessible devices or services.

== Main PoE ethernet switch ===

* HP ProCurve 2910al-480-PoE+ switch [https://github.com/wwwhtml/hp-2910al-switch-firmware-upgrade/ How to manage / firmware update]
* username: manager or operator
* password: Ask juul or someone on the sysadmins list
* MAC address main switch: a0:b3:cc:ac:e7:c0
* MAC address backup switch (not turned on): c0:91:34:c4:12:00
* Port 1 is VLAN 1 untagged, acting as DHCP client, is management VLAN
* Management possible via HTTP (no SSL) or SSH
* Port 1 is for management, untagged no VLAN and requests an IP using DHCP (not plugged into anything right now)
* Port 2 and 3 are for tagged access to VLANs 2 and 3 (public and private)
* Ports 4 to 24 are for untagged access to VLAN 2 (public)
* Ports 25 to 48 are for untagged access to VLAN 3 (private)

== WAN ==

Internet access comes from LMI. The modem is connected through VDSL copper next to the Omni main electrical panels.

The modem is up in the rack area near '''saros''' (a desktop computer running Debian Stretch) which serves as the primary gateway router.

Our public IP is 142.254.26.9 aka '''room.sudoroom.org'''.

== LAN ==
* Wifi subnet: 100.64.64.0/22
** 100.64.64.2 to 100.64.64.49: legacy static range
** 100.64.64.50 to 100.64.67.250: DHCP
* Wired subnet: 192.168.0.0/16
** 192.168.1.2 to 192.168.41.254: unused for now
** 192.168.42.2 to 192.168.49.254: self assigned static range
** 192.168.50.1 to 192.168.200.254: DHCP

This list of static IPs may not be complete. Before choosing a static IP, please use ping or nmap to check it first.

By request, we can reserve an IP from the DHCP pool and/or forward ports for you. Please send the MAC address and/or desired ports to [mailto:sysadmins@omnicommons.org sysadmins@omnicommons.org]

{| class="wikitable sortable blue_lines"
|+ Machines with static IPs
! style="width:120px;" data-sort-type="IPAddress" | IPv4 Address
! style="width:110px;" data-sort-type="IPAddress" | IPv6 or MAC Address
! style="width:110px;" | Assigned to
! class="unsortable" | Notes
! Who set it up?
|-
| 100.64.64.1
| 00:0d:b9:59:e4:b9
| sudogateway
| router/room.sudoroom.org
| [[User:juul|Juul]]
|-
| 100.64.64.11
| d0:39:72:18:59:06
| omnidoor
| beaglebone black controlling the door
| juul and jake
|-
| 192.168.42.3
| No IPv6 address
| No host name
| Dell PowerConnect 5324 24 port gigabit switch
| juul
|-
| 192.168.42.4
| No IPv6 address
| No host name
| Dell PowerConnect 5448 48 port gigabit switch
| juul
|-
| 192.168.42.10
|
| nodeconf.local
| The sudo mesh node configuration and build server
| Primarily [[User:Juul|juul]] and maxb
|-
| 100.64.65.66
| 84:25:19:71:bb:26
| SAMSUNG MX
| A printer in CCL that is naughty about avahi packets
| Dan of CCL and [[User:Jerkey]]
|-
| 100.64.64.88
| 00:21:b7:80:59:47
| ET0021B7805947.local
| [[Lexmark T654dn | Lexmark T654dn laser printer]]
| [[User:Jerkey|jerkey]]
|-
| 100.64.64.20
| 00:21:9b:1d:85:c1
| wasp.local
| [[Wasp.local| 3d printer desktop computer & giant_robot_arm serial host]]
| [[User:jake|jake]]
|-
| 100.64.64.130
| c4:54:44:3c:21:1e
| bigtv.local
| [[bigtv| orange fanless PC connected to the big TV above skÃ¼lgaard]]
| [[User:jake|jake]]
|-
| 100.64.64.29
| c0:8a:de:1d:59:b6
|
| ruckus_wifi_controller [https://github.com/sudoroom/ruckus-zonedirector1100-firmware-upgrade-process firmware upgrade process]
| daniel
|-
| 100.64.65.233
| c0:8a:de:2f:c1:80
|
| ruckus_wifi_accesspoint in "phat beets" room (termination is on 2nd floor top right of mess on beam)
| daniel
|-
|}

== Wireless Access Points (OUTDATED INFO) ==

All of the indoor wifi is being served up by [[Mesh/OmniWifi|TP-Link N750 routers modified for PoE]] running OpenWRT and configured as bridges with static IPs.

{| class="wikitable blue_lines"
!SSID
!Security
!Key
!MAC
!IP
!Channel
!Location
!Hardware
!Who set it up?
|-
|peoplesopen.net-omniroof
|open
|''n/a''
|Find Me
|100.64.64.4
|161 (5ghz)
|On flagpole on roof
|Ubiquiti NanoBeam
|[[User:Juul|juul]]
|-
|peoplesopen.net
|open
|''n/a''
|Find Me
|100.64.64.2
|11 (2.4ghz) and 36 (5ghz)
|Above entrance to CCL
|TP-Link N750
|[[User:Juul|juul]]
|-
|peoplesopen.net
|open
|''n/a''
|Find Me
|100.64.64.3
|6 (2.4ghz) and 165 (5ghz)
|middle of basement
|TP-Link N750
|[[User:Juul|juul]]
|-
|sudomesh
|open
|''n/a''
|Find Me
|192.168.42.18
|11
|zip-tied near server rack
|Ubiquiti Nanostation M2 Loco
|[[User:Juul|juul]]
|-
|Omni Ballroom
|open
|''n/a''
|Find Me
|192.168.42.19
|11
|Ballroom near stage
|Ubiquiti Picostation 2
|[[User:Maxb|maxb]]
}

[[Category:Network]]

Membermatters

2026-01-07T23:07:13Z

Jerkey: /* to check the logs from the docker instance */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* https://backers.sudoroom.org/logs/django.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= Help us build and test =
* prioritized bugs: https://github.com/orgs/sudoroom/projects/1/views/1
* submit a bug: https://github.com/sudoroom/MemberMatters/issues
== Making a dev environment ==
(this assumes you already have git installed and docker setup!)
# `cd` to a directory you want to put the repo
# `git clone https://github.com/sudoroom/MemberMatters.git`
# `git checkout -b branch-name` to make a new branch based of the default (sudoroom)
# `touch /usr/app/django.log` (this is where the logs will go, and not creating it as a file seemed to create it as a dir which docker hated)
# `cd ./docker`
# `docker pull` (this make take a while)
# `docker up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker stop $(docker ps -q)` will stop all the containers by doing `docker stop` on all of the running containers (the -q flag lists by ID)

==== where I got to/next steps ====
# doing all that, and then going to localhost:8000 takes me to the BMS login page instead of sudoroom's. possibly, since on my setup i ran `docker pull membermatters/membermatters` initially before following the rest of those setups, that is what broke it - i would think that the config files (the database?) would supercede that
# there is also a dev.env file at the top of the repo that might be worth checking out. possible you could `docker run --env_file /path/to/dev.env` and it would use that env instead of the one in the [https://github.com/sudoroom/MemberMatters/blob/481e4bc8f4a3f614e05fcc98af74c9380c7a05a2/docker/docker-compose.yml#L33 docker-compose.yml] ? I don't know if there is a `docker compose` equivalent, need to keep poking at that

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

martin and ivan talked a bit about this 2026-01-06:
* subscription statuses can be: active (currently paying) / inactive (not paying)
* member status can be: active (currently a member) / inactive (not a member, but possibly still paying as a dono or something) / new (unsure, maybe we use this as 'signed up, but still pending endorsements/waiting period? what's the order of operations?) / or account only (signed up but not paying/no payment info in MM)

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up payment plans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''free accounts need billing info''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''need to edit dashboard, landing page''
# ''update welcome and alert emails''

Membermatters

2026-01-05T19:39:01Z

Jerkey: /* github */

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* <code>sudo less /var/lib/docker/containers/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227-json.log</code>
* https://backers.sudoroom.org/logs/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227-json.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..d6ce52564e8ae64975690107efbc2f1907ac1fb8 the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/compare/d6ce52564e8ae64975690107efbc2f1907ac1fb8..00918eda47d88d090c29c976410ae8036579d7ea the changes rechner and jake made to build our docker for postgres]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up payment plans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''free accounts need billing info''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''need to edit dashboard, landing page''
# ''update welcome and alert emails''

Membermatters

2026-01-05T04:43:37Z

Jerkey:

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* <code>sudo less /var/lib/docker/containers/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227-json.log</code>
* https://backers.sudoroom.org/logs/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227-json.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..sudoroom the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up payment plans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''free accounts need billing info''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''need to edit dashboard, landing page''
# ''update welcome and alert emails''

Membermatters

2026-01-05T03:15:19Z

Jerkey:

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* <code>sudo less /var/lib/docker/containers/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227-json.log</code>
* https://backers.sudoroom.org/logs/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227-json.log

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..sudoroom the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up payment plans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''free accounts need billing info''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''need to edit dashboard, landing page''
# ''update welcome and alert emails''

Membermatters

2026-01-05T02:30:11Z

Jerkey:

this is the notes for the membermatters installation

https://backers.sudoroom.org

= to create a new user =
* https://backers.sudoroom.org/register

= to check the logs from the docker instance =
* <code>sudo less /var/lib/docker/containers/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227/809f01cc9901740cc243b8772e479a6c50cb72e28cc81e307a6e4cd7bcfb0227-json.log</code>

= github =
* [https://github.com/sudoroom/MemberMatters/compare/db0724495a09731ec18db2ebe353931a08c256e2..sudoroom the changes juul made to add sendmail as an option]
* [https://github.com/sudoroom/MemberMatters/tree/sudoroom we are using the sudoroom branch in our docker]
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork

= we are not spam =
* emails sent by this system for people to validate their account, or reset their password, are important
* emails are being accepted by gmail (for now) but not by some other platforms, and maybe not for some gmail users?
* we should look for ways to find out why the emails are rejected by some servers
* we probably need to format the emails with plaintext and MIME to make them look normal to spam checkers
* Our server is postfix based, but yeah, postfix has very good logging on exactly what happens to each message. Though you as the sender can't know if it went into spam, only if it got outright rejected.
* emails to an MIT address were rejected by Microsoft: "Access denied, banned sending IP [198.199.116.180]. To request removal from this list please visit https://sender.office.com/ and follow the directions" and then Sean followed the directions and asked them to unblock our IP address
* we need to setup monitoring of emails that were outright rejected, and take action each time. Dealing with emails marked as spam will be more challenging unless people have access to the spam filter information on their receiving end.
* we need to encourage more and people to sign up to the new system as we make progress, AFTER setting up rejection monitoring

= certbot =
* juul used pipx to install, and then had to manually make a systemd job to check it twice a day

= MEMBERSHIP PROCESS- DISCUSSION =
ivan & anca working on this

=== I want to become a member!! Onboarding Steps ===
# Hang Out, attend an event, join lists, discord
# I Like this! - Fill out the Intent to Join Form!!!
# Attend the next meeting, and get endorsements
# Get a mentor!!

=== Setup payment on Member Matters ===
# Create an account, verify via email
# I'm on Sudo Humans, what do I do?
# I use PayPal, or checks, or Bitcoin. What do I do?

=== Get door access ===
# Get an email?
# How many door access systems will we have?

=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up payment plans

=== Pain points: We need to fix these issues ... later ===
# ''need to check for verification email from member matters''
# ''free accounts need billing info''
# ''get access card process needs work''
# ''members can see each others activities on member matters''
# ''need to edit dashboard, landing page''
# ''update welcome and alert emails''

Bigtv

2026-01-02T19:30:42Z

Jerkey:

presently a chromebox running linux, with limited disk space. Its purpose is to serve as a wall TV intercom for outside participation

it used to be an orange fanless PC running linux mint 20 but that disappeared...

the big HITACHI TV on the east wall in sudoroom
[[File:telescreen1.jpg|400px|thumb|right|BigTV]]
The TV was originally bolted to the wall in late 2015, connected to an early raspberry pi, logged into IRC chat!

In 2022 it got a new computer and improved scripts to make it work. Join the sudo-discuss list for more information!

this node package serves a local webapp that connects to a Jitsi server, while watching the number of participants in order to keep the monitor turned on when people are in the room:
https://github.com/sudoroom/jitsi-telepresence-portal/blob/main/src/App.jsx

commands in ~/bin include screen-on which unblanks the screensaver. screen-q queries the present settings.
there is a cron job keeping the dpms timeout (hardware screensaver) set to 300 seconds

not working right now: when [[sudobot]] (in irc) sees you, type !say something and it will cause this computer to speak

Custom 3D Printer

2025-12-04T08:59:48Z

Jerkey:

This seems to be a custom 3D printer that was donated in the summer of 2023

* [https://sudoroom.org/lists/hyperkitty/list/sudo-discuss@sudoroom.org/thread/Y2T3YOU5OBPD3U6DMMOKJ3CFRCLO6SLR/ email thread]

* Recently R came through and helped work on this with Avery, apparently it's a "VORON" 3d printer. Here are their notes:<code>
Octopus pro 1.0
klipper via mainsail
connect via ip
127.0.0.1

Printer CFG is currrently a hack and slash from another voron config
!LOOK AT THE SENSOR SECTION, CHECK THE BED SENSOR AND PINS. SERIOUSLY. IT IS IMPORTANT.!</code>

---------- Forwarded message ----------
Date: Tue, 25 Jul 2023 21:39:31 -0700
From: Scott Griffitts
Subject: Re: [sudo-info] 3D printer donation

Hey, Dropped off the printer with Toby and met a few folks who were excited,
skeptical, and questioning the printer. I figured I would share some info on
it.

Here is the page on the upgraded Z mod I did: https://seckit3dp.design/kit/triple-z

Here is the page for the main printer build: https://github.com/SecKit/SK-Go_SK-Mini

Here is some info on the firmware it can run: https://www.klipper3d.org/
(I think if you do some digging, you can find examples for the kinematic bed)

Here is the bed probe I
used: https://coex3d.com/products/bltouch-v3-1-automatic-bed-leveling-probe

The stepper motor board used is big tree tech octopus v1.0 with TMC2209 drivers

If you have any other questions let me know :)

Also,
If you guys need volunteers or anything, let me know. I’d love to help out with really
cool people like you guys.

Regards
Scott Griffitts

Uprint

2025-11-25T22:40:52Z

Jerkey:

# stratasys uprint SE 3d printer AKA "HP DesignJet 3D"
[[File:Designjet 3D-high-res-scenario-1.gif]]
[[File:Stratasys uprint se.png|300px]]

## links about printers like this
* [https://www.youtube.com/watch?v=gt1kzkMWpG4 stratasys uprint SE on youtube]
* [https://www.youtube.com/watch?v=uzeM71dRYnc22 HP designjet 3d on youtube]

## hacking the print cartridge ID chip
* https://www.reddit.com/r/3Dprinting/comments/xdh5c7/stratasys_filament_chip_hacking/
* https://github.com/bvanheu/stratasys
* https://github.com/slaytonrnd/CartridgeWriter
* Matthew Goodman's eepromTool-ds2433 code from: https://github.com/meawoppl/eepromTool-ds2433
* this one uses raspberry pi: https://haveblue.org/?p=1988
* but for uprint, it's more complicated re: https://haveblue.org/wp-content/uploads/2017/02/hp-designjet-3d-hack.pdf or locally at [[File:Hp-designjet-3d-hack.pdf]]

File:Hp-designjet-3d-hack.pdf

2025-11-25T22:40:02Z

Jerkey:

Uprint

2025-11-21T23:31:15Z

Jerkey: Created page with "# stratasys uprint SE 3d printer AKA "HP DesignJet 3D" File:Designjet 3D-high-res-scenario-1.gif 300px ## links about printers like this * [https://www.youtube.com/watch?v=gt1kzkMWpG4 stratasys uprint SE on youtube] * [https://www.youtube.com/watch?v=uzeM71dRYnc22 HP designjet 3d on youtube] ## hacking the print cartridge ID chip * https://www.reddit.com/r/3Dprinting/comments/xdh5c7/stratasys_filament_chip_hacking/ * https://github...."

File:Stratasys uprint se.png

2025-11-21T23:29:13Z

Jerkey:

File:Designjet 3D-high-res-scenario-1.gif

2025-11-21T23:26:09Z

Jerkey:

TAZ 4

2025-10-30T19:11:42Z

Jerkey:

Sudoroom has a TAZ 4 3d printer, that was donated in 2022. It should not be confused with the older [[TAZ|TAZ 3]] 3d printer, which didn't work very well as a 3D printer.

[https://download.lulzbot.com/TAZ/4.0/ Documentation for the TAZ 4 from Lulzbot corporation]

<big>'''The following start code should be entered until we can recompile the [https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/ firmware]
<code>M907 E150</code>'''</big>

[[File:720px-Rambo-conn-all.jpg|thumb]]
The extruder head from the TAZ 3 was transferred onto the TAZ 4 which will presumably make a better 3D printer. The TAZ 3 will be converted for solder paste dispensing only
[[File:Taz4-3d-printer.jpg|720px]]

The TAZ 4 uses an [https://reprap.org/wiki/Rambo Ultimachine Rambo 1.3L main board] and here is the correct [[File:RAMBo_1.3L_Schematic.pdf|RAMBo_1.3L_Schematic]]
The original 14-pin "Extruder 0" connector on the TAZ4 was removed from "Aux Power Mosfet Output" (pins 5/red,6/black), E0 Heat (pins 12,13), E0 Fan (9/black,10/red) and Ground (pin 2), and E0 (3,7,11,14). The extruder harness from the TAZ3 was installed in it.

The TAZ 4 didn't work because both Fuse F2 and F3 on the RAMBO main board were missing. They're supposed to be [https://www.littelfuse.com/products/fuse-blocks-fuseholders-and-fuse-accessories/fuse-blocks/154.aspx Littelfuse OMNI-BLOK 154 series] and we didn't have any, so I stuck 5-amp [https://www.digikey.com/en/products/detail/littelfuse-inc/0466005-NR/521341 F1460CT-ND] in there since we have dozens of them in the FUSES bin: [[Image:Taz4_fuse_kludge.jpg|thumb|left]]

<s>And now it turns on and mostly works, but the extruder stepper is mostly skipping. Most likely the current needs to be adjusted for the extruder stepper driver, which is something we have to read the manuals to figure out how to do</s> - there are no tiny potentiometers to adjust on this RAMBO board, only a "digipot".

The digipots are controlled with the [https://marlinfw.org/docs/gcode/M907.html M907 command]

the default values are found in
<code>Configuration_adv.h:#define DIGIPOT_MOTOR_CURRENT {175,175,240,135,135} // Values 0-255 (RAMBO 135 = ~0.75A, 185 = ~1A)

pins.h:#define DIGIPOT_CHANNELS {4,5,3,0,1} // X Y Z E0 E1 digipot channels to stepper driver mapping</code>

TAZ 4

2025-10-30T19:07:24Z

Jerkey:

Sudoroom has a TAZ 4 3d printer, that was donated in 2022. It should not be confused with the older [[TAZ|TAZ 3]] 3d printer, which didn't work very well as a 3D printer.

[https://download.lulzbot.com/TAZ/4.0/ Documentation for the TAZ 4 from Lulzbot corporation]

<big>'''The following start code should be entered until we can recompile the [https://download.lulzbot.com/TAZ/4.0/software/current/firmware/Marlin/ firmware]
<code>M907 E150</code>'''</big>

[[File:Taz4-3d-printer.jpg|thumb]]
The extruder head from the TAZ 3 was transferred onto the TAZ 4 which will presumably make a better 3D printer. The TAZ 3 will be converted for solder paste dispensing only

The TAZ 4 uses an [https://reprap.org/wiki/Rambo Ultimachine Rambo 1.3L main board] and here is the correct [[File:RAMBo_1.3L_Schematic.pdf|RAMBo_1.3L_Schematic]]
[[File:720px-Rambo-conn-all.jpg]]
The original 14-pin "Extruder 0" connector on the TAZ4 was removed from "Aux Power Mosfet Output" (pins 5/red,6/black), E0 Heat (pins 12,13), E0 Fan (9/black,10/red) and Ground (pin 2), and E0 (3,7,11,14). The extruder harness from the TAZ3 was installed in it.

The TAZ 4 didn't work because both Fuse F2 and F3 on the RAMBO main board were missing. They're supposed to be [https://www.littelfuse.com/products/fuse-blocks-fuseholders-and-fuse-accessories/fuse-blocks/154.aspx Littelfuse OMNI-BLOK 154 series] and we didn't have any, so I stuck 5-amp [https://www.digikey.com/en/products/detail/littelfuse-inc/0466005-NR/521341 F1460CT-ND] in there since we have dozens of them in the FUSES bin: [[Image:Taz4_fuse_kludge.jpg|thumb|left]]

<s>And now it turns on and mostly works, but the extruder stepper is mostly skipping. Most likely the current needs to be adjusted for the extruder stepper driver, which is something we have to read the manuals to figure out how to do</s> - there are no tiny potentiometers to adjust on this RAMBO board, only a "digipot".

The digipots are controlled with the [https://marlinfw.org/docs/gcode/M907.html M907 command]

the default values are found in
<code>Configuration_adv.h:#define DIGIPOT_MOTOR_CURRENT {175,175,240,135,135} // Values 0-255 (RAMBO 135 = ~0.75A, 185 = ~1A)

pins.h:#define DIGIPOT_CHANNELS {4,5,3,0,1} // X Y Z E0 E1 digipot channels to stepper driver mapping</code>

File:720px-Rambo-conn-all.jpg

2025-10-30T19:05:51Z

Jerkey: