Makerfaire2025report

heroshot

Motivation

Since we had created something special, we wanted to create an opportunity for many people to see it. In making things, feedback itself gives creators many insights and becomes energy for the next project.

Application Submission

Schedule

gantt
    title Maker Faire Tokyo 2025 Schedule
    dateFormat  YYYY-MM-DD
    axisFormat  %m/%d

    section Exhibitor Recruitment
    Exhibitor Recruitment Start           :a1, 2025-04-24, 1d
    Exhibitor Recruitment Period           :a2, after a1, 2025-05-26
    Exhibitor Recruitment Deadline           :milestone, 2025-05-26, 0d

    section Exhibitor Selection & Payment
    Exhibitor Selection Results Announcement       :a3, 2025-05-27, 2025-07-03
    Exhibition Fee, Equipment, Power Payment :a4, after a3, 10d

    section Public Release & Sales
    Exhibitor Information Release & Advance Sales Start :a5, 2025-08-28, 1d
    Program Guide Release     :a6, 2025-10-01, 1d

    section Main Event
    Event Day 1 (12:00～18:00) :a7, 2025-10-04, 1d
    Event Final Day (10:00～17:00):a8, 2025-10-05, 1d

Date	Content	Notes
April 24, 2025	“Maker Faire Tokyo 2025” Exhibitor Recruitment Start	Exhibition application acceptance starts
May 26, 2025 (Mon) 13:00	Exhibitor Recruitment Deadline	Application deadline (strict)
Until July 3, 2025 (Thu)	Exhibitor Selection Results Announcement	Selected exhibitors will pay exhibition fees, equipment, power, tags, etc.
August 28, 2025	Exhibitor Information Release & Advance Ticket Sales Start	General public information release starts
October 1, 2025	Program Guide Release	Venue layout, stage events, workshop information, etc.
October 4, 2025 (Sat)	Event Day 1	Event time: 12:00～18:00 (entry until 30 minutes before end)
October 5, 2025 (Sun)	Event Final Day	Event time: 10:00～17:00 (entry until 30 minutes before end)

Application Details

Item No.	Item Name	Content
1-1	Exhibitor ID	M0212
1-2	Exhibitor Name	FabAcademy Node: Kannai
1-3	Representative Last Name	Ito
1-4	Representative First Name	Shintaro
1-5	Representative Email Address	-
2-1-a	Works	Dry Landscape Generator (XY Plotter / 60cm×60cm×40cm) 1 unit, Microcontrollers 4 units, Camera 1 unit, 24000mAh Mobile Battery, USB Cables 20 units
2-1-b	Equipment & Handouts	Laptop PCs 2 units, Transformer 1 unit, 15.6-inch Dual Mobile Display 1 unit, Work Introduction Panel (A2 size) 1 sheet, Work Introduction Panel (A3 size) 1 sheet, Flyers 200 copies, Fire-resistant Table Cloth 1 sheet, Garbage Bags 2 units, Transport Cardboard 1 unit, Hand Trucks 2 units, Acrylic Stand 1 unit
2-1-c	Dangerous Items (Tokyo Fire Prevention Ordinance Applicable Items)	None
2-1-d	Non-vehicle Lithium-ion Battery Carrying	3. Self-made lithium-ion batteries are exhibited or used in works/products
2-1-e	Details of Works with Lithium-ion Batteries	This work is an X-Y positioning arm that uses lithium-ion batteries as a power source. It creates dry landscapes using the X-Y positioning arm, and during the exhibition, it will be demonstrated on the table at regular intervals. Staff will be present during demonstrations to ensure safety management.
2-2	Planned Food Carrying	None
2-3	Required Maximum Power Capacity (W)	500
3-1-a	Delivery Method	Hand-carry, Yamato Takkyubin
3-1-b	Number of Delivery Items (Yamato Takkyubin)	3
3-2	Delivery Date (Planned)	10/3 (Fri) afternoon, 10/4 (Sat) 9:00～12:00
3-3	Pickup Method	Hand-carry, Yamato Takkyubin

Improvements

Rake improvements

The rake attachment, which had been unstable during the assignment, was redesigned with flexible 3D-printed joints so that it passively follows the movement on the sand.

STEP file: rake_v3.stp

Program

Based on the program developed for last year’s THE LONE ANGLER project, the code was modified to test the Karesansui functions without relying on a network.

Modifications:

• Swapped the motor A and C, run coreXY on motor B and C (Because of an issue on the motor A module while testing)
• Added a function to grade the sand garden
• Zeroing for Z motor (added in goToHome)
• Modified the UI for testing

Modular Things program

// Code_yuichi4
// warning: without a powered usb-hub, currentScale > 0.5 are likely to fail 
//
// Open browsers DevTools console with
//  cmd + shift + j (Linux)
//  ctrl + shift + j (win)
//  command + option + j (mac)
//

// UI用の要素を作成
const el = document.createElement("div");
el.style = `padding: 10px; font-family: sans-serif;`;

// UIのHTMLを追加（シンプル版）
el.innerHTML = `
  <div style="display: flex; flex-direction: column; justify-content: flex-end; height: 120px;">
    <img src="https://fabacademy.org/2025/labs/kannai/images/logo2022-tate-g.png" 
         alt="FabLab Kannai" 
         width="90" 
         style="margin: auto;">
  </div>

  <h1>RYOAN-JI XY 2024.9</h1>
  <p style="color: black;">FabAcademy2025 / Modular-Things coreXY</p>
  <hr>

  <!-- XY移動ボタン -->
  <div style="text-align: center; margin: 10px;">
    <button id="yPlus">✌️</button>
  </div>
  <div style="text-align: center; margin: 10px;">
    <button id="xMinus">👈</button>
    <button id="Home">🏠</button>
    <button id="xPlus">👉</button>
  </div>
  <div style="text-align: center; margin: 10px;">
    <button id="yMinus">👇</button>
  </div>

  <!-- Z移動（up/down） -->
  <div style="text-align: center; margin: 10px;">
    <button id="down">🔄</button>
    <button id="up">🧹</button>
  </div>

  <hr>
  <!-- 図形描画コマンド -->
  <div style="text-align: center; margin: 10px;">
    <button id="drawSquare">drawSquare</button>
    <button id="Draw">Draw</button>
    <button id="Grade">Grade</button>
    <!-- <button id="Test">test</button> -->
  </div>

  <hr>
  <p style="font-size: small; color: black;">
    Open DevTools console with<br>
    cmd + shift + j (Linux)<br>
    ctrl + shift + j (Win)<br>
    command + option + j (Mac)
  </p>
`;

// bodyに追加
document.body.appendChild(el);


//--------------------------------------
// Testボタンの処理
//--------------------------------------
/*
el.querySelector("#Test").addEventListener("click", () => {
  delay(100);
  test();
});

function test() {
  machine.setPosition([0, 0]);
  goTo(10, 10);
}
*/
//--------------------------------------
// CoreXYモーション制御
//--------------------------------------

// 同期モーションマシンを作成
const machine = createSynchronizer([motorC, motorB]); // motorC, motorBを使用

// XY移動関数
async function goTo(x, y) {
  console.log(`Moving to (${x}, ${y})`);
  await machine.absolute([-1 * (x + y), 1 * (x - y)]); 
}

//--------------------------------------
// 各UIボタンのイベント設定
//--------------------------------------
el.querySelector("#xPlus").addEventListener("click", () => xPlus());
el.querySelector("#xMinus").addEventListener("click", () => xMinus());
el.querySelector("#yPlus").addEventListener("click", () => yPlus());
el.querySelector("#yMinus").addEventListener("click", () => yMinus());
el.querySelector("#up").addEventListener("click", () => up());
el.querySelector("#down").addEventListener("click", () => down());
el.querySelector("#Home").addEventListener("click", () => goToHome());
el.querySelector("#drawSquare").addEventListener("click", () => { delay(100); drawSquare(); });
el.querySelector("#Grade").addEventListener("click", () => { delay(100); Grade(); });
el.querySelector("#Draw").addEventListener("click", () => { delay(100); draw(); });

// DOMにUIを追加
render(el);

//--------------------------------------
// モーター設定
//--------------------------------------
motorA.setCurrent(1);
motorA.setStepsPerUnit(1);
motorA.setAccel(10);

motorB.setCurrent(1);
motorB.setStepsPerUnit(3);
motorB.setAccel(20);

motorC.setCurrent(1);
motorC.setStepsPerUnit(9); // motorB とバランスするため
motorC.setAccel(20);

machine.setPosition([0, 0]); // 現在位置を (0,0) に設定
motorA.setPosition(0);

//--------------------------------------
// 動作関数群
//--------------------------------------

// 原点復帰処理
async function goToHome() {
  while (await motorA.getLimitState()) {
    motorA.relative(1, 500, 100);
    await delay(50);
  }
  motorA.relative(-25); //中立位置
  await delay(100);

  while (await motorC.getLimitState()) {
    // motorC.velocity(-10);
    // motorB.velocity(-10);
    motorC.relative(1, 800, 100);
    motorB.relative(-1, 800, 100);
    await delay(50);
  }
  while (await motorB.getLimitState()) {
    // motorC.velocity(-10);
    // motorB.velocity(10);
    motorC.relative(1, 800, 100);
    motorB.relative(1, 800, 100);
    await delay(50);
  }
  // motorC.velocity(0);
  // motorB.velocity(0);
  machine.setPosition([0, 0]);
  motorA.setPosition(0);
  await delay(100);

  // Backoff
  goTo(10, 10);
  await delay(1000);
}

//--------------------------------------
// XY移動系 (手動操作)
//--------------------------------------
function xPlus() {
  machine.setPosition([0, 0]);
  for (let i = 0; i < 10; i++) goTo(i, 0);
}

function xMinus() {
  machine.setPosition([0, 0]);
  for (let i = 0; i < 10; i++) {
    goTo(-i, 0);
    delay(200);
  }
}

function yPlus() {
  machine.setPosition([0, 0]);
  for (let i = 0; i < 10; i++) goTo(0, i);
}

function yMinus() {
  machine.setPosition([0, 0]);
  for (let i = 0; i < 10; i++) goTo(0, -i);
}

async function up() {
  motorA.relative(10);
  await delay(1000);
}

async function down() {
  motorA.relative(-10);
  await delay(1000);
}

//--------------------------------------
// 図形描画
//--------------------------------------
async function drawSquare() {
  // await goToHome();
  motorA.relative(24); //Down
  await delay(200);
  for (let i = 0; i < ptsSquare.length; i++) {
    await goTo(ptsSquare[i][0], ptsSquare[i][1]);
    await delay(200);
  }
  motorA.relative(-24); //UP
  await delay(200);
}

async function draw() {
  // await goToHome();
  motorA.relative(24); //Down
  await delay(200);
  for (let i = 0; i < pts.length; i=i+4) { //i++
    await goTo(pts[i][0], pts[i][1]);
    await delay(200);
  }
  motorA.relative(-24); //UP
  await delay(200);
}

// 均し
async function Grade() {
  // await goToHome();
  motorA.relative(-24); //UP (Grading)
  await delay(200);
  for (let i = 0; i < ptsGrade.length; i++) {
    await goTo(ptsGrade[i][0], ptsGrade[i][1]);
    await delay(200);
  }
  motorA.relative(24); //Down
  await delay(200);
}

//--------------------------------------
// 描画パターンの座標定義
//--------------------------------------
var ptsSquare = [[80, 20], [80, 80], [20, 50], [20, 20]];
var ptsStar   = [[20, 10], [30, 50], [40, 10], [10, 40], [50, 40], [20, 10]];
var ptsGrade  = [[221,245],[221,45],[197,45],[197,245],[173,245],[173,45],[149,45],[149,245],[125,245],[125,45],[101,45],[101,245],[77,245],[77,45],[53,45],[53,245],[29,245],[29,45]];
// Draw
var pts = [];

Drawing

A simple Grasshopper definition was created to convert a path into a point and ultimately into XY coordinates such as [0, 10], .... A useful feature called “Stream Contents” allows data from a panel to be streamed to a specified text file.

Grasshopper: Draw.gh

Preparations

Panel design and Booth planning

A2 and A3 panel explaining how the machine works and some photos of the 2 weeks process. We used Accea to print, which cost 5,500 JPY and was delivered in a few days in (overly) well packaging.

In Rhino, we laid everything out on a table to test whether it would fit in the space.

Reflections on the panels

Good points:

• It helps explain overview of how it (supposed to) work
• Some cues to engage for different audiences; AI, Karesansui, coreXY, Haiku etc.

Points to improve:

• Haiku generation was not self explanatory
• Overview in English could help increase interest among international audiences
• More descriptions about Fab Academy program, Machine building assignment and things we inherited from Fab network would have been helpful

Power setup

Because it found out that we can’t use power outlets, we decided to use the following mobile battery and DC-DC power supply, borrowed from Ito-san and Tamiya-san for each.

• Mobile battery: Anker 737 Power Bank
  • Input: 5V=3A
  • Output: USB-C: 5V=3A (Max. 140W)
  • Battery Capacity: 24,000mAh
• DC-DC power supply: DP100
  • This case, it was set as: CV (Constant voltage): 5V

Modular-things can be powered by mobile battery

It worked without any problems. On the day 2, the machine ran from 10am to 5pm with 61% battery power remaining.

Trouble shooting

Burned H-bridge circuit

During testing, the X and Y directions were observed to be jagged and unstable. It was later found that one of the H-bridge ICs and a 0.1 µF capacitor on the modular-stepper circuit had burned out (left image below). This was likely caused by an incorrect voltage setting when the mobile battery was first connected.

A replacement capacitor and IC were borrowed from Tamiya-san and installed. Since some of the surrounding traces were burned and peeled off, a 0.1 µF capacitor was connected to the adjacent 1 µF capacitor, additional solder was applied, and a short wire was used to make a temporary repair (right image). Surprisingly, the circuit functioned properly after the fix.

Broken limit switch pin while transportation

After the machine was transported to Tokyo Big Sight, it was found that a limit switch socket had broken. Fortunately, a suitable soldering station was available at the venue, and jump wires were soldered to restore the connection.

Anything that can go wrong will go wrong

Murphy’s law

Transportation

The machine was packed and secured on a handcart for transportation to Tokyo Big Sight by train.

Ref: JR East | Size and weight of luggage that can be carried on the train

Feedback

Member-wise Feedback Summary

Ito

• Overall positive reactions, people found it “interesting.”

• Main feedback:

• “It would be good to place stones” → If it draws lines avoiding those stones, it would create more natural and interesting movements.

• “If the cables were stainless steel, they would have more tension and look better.”
• Received many questions about “What is Fab Academy?”
• People were surprised that “this was made in 2 weeks/4 days.”
• Gemini model developers were also present at the venue.

Hayashi

• Many people said “the haiku was the most memorable” and “where did the haiku idea come from?”
• Many questions about motivation: “Why did you decide to make this work?”
• Interest in structural aspects: “Why is the rake wobbly?”

• Many visitors first looked at the panel to read the content, then approached us to talk.

• For the future, it would be good to design panels with “conversation starters” in mind.

• It served as a “hook” but may have been too brief in explanation.

• It would have been good to add an English summary (simple explanation).

• This time we targeted Japanese people, but it would be good to consider foreigners in the future.

Tamiya

• Some pointed out that “the haiku’s presence was a bit weak.”

• It would be good to have strong visual elements (something that stands out) to make the haiku more impressive.

• “It was somewhat unclear what this machine does.”

• There needs to be a way to convey the concept at a glance.

Reactions on X