Wireless Button Addition

Important Note

• The wireless button requires battery installation, the battery model is CR927

• Return to the home page and click the + inside the red box in the image below
  Loading...
• After the interface below appears, press the wireless button with the battery installed once normally
• The wireless button's ID will be automatically generated in the red box; this ID is unique
  Loading...
• Enter the name you want for the button in the red box
  Loading...
• Click the first red box, and the second blue box will appear
  Loading...

Note

• Custom GCODE and API requests are controlled via wireless connection
• GPIO triggering is controlled via wired connection

Custom GCODE

• Customize GCODE; you can enter the code or macro name you need to execute in the red box, and AirClick will automatically send it to the printer for execution
  Loading...

Request API

• Klipper API Settings
• RRF API Settings
• BambuLab API Settings

1. Predefined APIs can implement custom macros, emergency stop, Klipper restart, firmware restart, system shutdown, etc.

Loading...

2. Custom API Explanation
   • All API reference documentation Moonraker API
   • method should be consistent with the method of the Moonraker API
   • params should be consistent with the params of the Moonraker API
3. Below is an example using the API to start printing a specified file
   • The image below is an example from the Moonraker official documentation
   Loading...
   • Below is an example of filling in the API for AirClick
   Loading...
4. Save this button to be able to start printing the specified file

1. Custom API Explanation
   • All API reference documentation RepRapFirmware HTTP API
   • Only GET request interfaces are supported
   • method should be consistent with the uri of the RRF HTTP API
   • params should be consistent with the url query of the RRF HTTP API
2. Below is an example using the API to delete a specified file or folder
   • The image below is an example from the RRF official documentation
   Loading...
   • Below is an example of filling in the API for AirClick
   Loading...
   • Here, the params need to convert the URL parameters to JSON format, e.g., /?aaaa=bbb&cccc=ddd
   • After conversion, it should be

     {
         "aaaa": "bbb",
         "cccc": "ddd"
     }

3. Save this button to be able to delete the specified file or folder

1. Predefined APIs can implement pause printing, cancel printing, LED control, etc.

Loading...

• For LED control, it is recommended to use automatic switching mode. In this mode, the LED status will be automatically detected and toggled, enabling one-click on/off.

2. Custom API Explanation
   • For BambuLab API, please refer to the relevant Github Open BambuAPI documentation
3. Below is an example using the API to set print speed
   • Below are the complete parameters sent via BambuLab LAN MQTT

     {
         "print": {
             "sequence_id": "0",
             "command": "print_speed",
             "param": "2" // Print speed level as a string
                          // 1 = silent
                          // 2 = standard
                          // 3 = sport
                          // 4 = ludicrous
         }
     }

   • The image below shows an example of filling in the API for AirClick
   Loading...
4. Save this button to be able to set the print speed

Trigger GPIO (Klipper Only)

• Triggering GPIO requires STM32F072 to be connected to Klipper

• For firmware flashing and connection, please refer to this document Firmware Flashing and Connection

• Ten IOs from PB0 to PB9 can be used. After properly flashing the firmware and connecting to Klipper, standard configuration is sufficient. Below is a reference configuration

  [mcu AirClick]
  serial: /dev/serial/by-id/usb-Klipper_stm32f072xb_AirClick-if00
  ### Need to search for USB ID and modify here
  
  [gcode_button _test]
  pin: ^!AirClick:PB0
  press_gcode:
      M118 PB0
  
  [gcode_button _test1]
  pin: ^!AirClick:PB1
  press_gcode:
      M118 PB1
  
  [gcode_button _test2]
  pin: ^!AirClick:PB2
  press_gcode:
      M118 PB2
  
  [gcode_button _test3]
  pin: ^!AirClick:PB3
  press_gcode:
      M118 PB3
  
  [gcode_button _test4]
  pin: ^!AirClick:PB4
  press_gcode:
      M118 PB4
  
  [gcode_button _test5]
  pin: ^!AirClick:PB5
  press_gcode:
      M118 PB5
  
  [gcode_button _test6]
  pin: ^!AirClick:PB6
  press_gcode:
      M118 PB6
  
  [gcode_button _test7]
  pin: ^!AirClick:PB7
  press_gcode:
      M118 PB7
  
  [gcode_button _test8]
  pin: ^!AirClick:PB8
  press_gcode:
      M118 PB8
  
  [gcode_button _test9]
  pin: ^!AirClick:PB9
  press_gcode:
      M118 PB9