TD-1

Overview¶

AFC has the ability to grab data from multiple TD-1 devices that are connected to your printer. TD-1 devices can be connected inline with your PTFE tubes to capture data from all lanes, or multiple TD-1's can be added to capture data from specific units. AFC can also be setup to capture TD-1 data once filament is inserted into a lane and/or during startup PREP routine. Once this data is captured it will be sent to moonraker database to allow third-parties (like OrcaSlicer once support is added) to read what color, TD, mapping, material filament, etc. is in each lane, learn more about this feature here.

Note

More information about the TD-1 and TD-1S devices can be found on the AJAX-3D website.

Prerequisite¶

TD-1 firmware version on at least version 2.0.0, updating requires Hueforge v0.9.1.2 or newer.
After updating, run through lux and RBG calibration in Hueforge under TD-1 dropdown.
For TD-1 users, with version 2.0.0 firmware your ball bearing can be removed to reduce filament friction, but make sure to check Optical Button in Hueforge under TD-1 -> TD-1 Settings.

td1_optical_setting

PTFE Case¶

TD-1 PTFE case so that PTFE tubes can be connected to either side : makerworld link

Moonraker Setup¶

To communicate correctly with TD-1 devices, moonraker needs to be updated to at least v0.9.3-116-gb11a7915 and the following needs to be added to moonraker.conf file.

[td1]

Once added, restart the printer. Once restarted and TD-1 device is connected you will see Found TD-1 device connected to printer printed out in your console if everything is working correctly.

Calibration¶

To calibrate bowden length to TD-1 device run AFC_CALIBRATION and in the calibration section select Calibrate TD-1 Length then choose when lane to use for calibration. This calibration only needs to be done with one lane per TD-1 device. Once calibration starts, it will be slow as it takes time for TD-1 to update once filament is detected. Once calibration is done the afc_unload_bowden_length variable will automatically be updated. If it's not already in your config file it will be added to AFC_auto_vars.cfg file.

Other configuration values¶

To capture TD and color values when filament is loaded into a lane capture_td1_when_loaded needs to be set to True. This variable can be added to AFC, AFC_BoxTurtle/AFC_NightOwl/etc, AFC_Stepper/AFC_lane config sections. This only happens if a lane is not loaded to the toolhead and the hub is clear.
To capture TD and color during PREP startup sequence set capture_td1_data: True under AFC_prep in AFC.cfg file. This only happens if a lane is not loaded to the toolhead and the hub is clear.
If any error occurs during PREP AFC will not capture data upon first loading.
When using multiple TD-1 devices in system, use td1_device_id to specify which id belongs to a specific Unit or lane. This value can be added to AFC_BoxTurtle/AFC_NightOwl/etc, AFC_Stepper/AFC_lane config sections. If only using one device, this variable is not needed.

Macros¶

To manually grab TD and color for a lane use AFC_GET_TD_ONE_DATA which will create a popup to allow selection of which lane to grab the data from.
If filament is loaded to the toolhead when printer is restarted/first turned on, TD-1 will be in an error state. To fix this unload filament from toolhead with TOOL_UNLOAD and then run AFC_RESET_TD1 with correct id to reset TD-1. AFC will wait up to 30 seconds for reset to happen and will display message if reset was successful or unsuccessful.

Troubleshooting¶

If you think that your TD-1 is connected but AFC still cannot see your device, navigate to http://<printter_ip>/machine/td1/data to verify that you TD-1 device shows up here or not.

Example of moonraker detecting TD-1:

{
  "result": {
    "status": "ok",
    "devices": {
      "E6625877D318C430": {
        "td": null,
        "color": null,
        "scan_time": null
      }
    }
  }
}

If TD-1 does not show up in query, SSH into printer and list USB serial devices with:

ls /dev/serial/by-id/*

If TD-1 is detected you should see something like the following print out.

/dev/serial/by-id/usb-AJAX_3D_TD-1_E6625877D318C430-if00

TD1 shows up as waveshare when running lsusb¶

When first powering on your printer, if your TD1 shows up as waveshare when doing lsusb then you may need to add a boot delay by performing the following steps:

Note

If you have multiple blocks when running lsblk you may need to unplug your TD1 device and run lsblk again to see which block disappears as this would be the block for your TD1. If you have unplugged your TD1 while your printer is on, you will need to shutdown printer, plug TD1 back into your printer and turn back on for these steps to be performed.

From as fresh power up, SSH into printer
Run lsblk to find block to mount, eg /dev/sdb1.
Run sudo mkdir /mnt/pico, ignore step if this folder already exists
Run ls /mnt to verify folder was created
Run sudo mount /dev/sdb1 /mnt/pico replacing sdb1 with your correct drive block
Change directory into /mnt/pico folder cd /mnt/pico
List files in directory with ls and there should be a boot.py file that shows up
- Command to open and edit file sudo nano boot.py
```
import startUp

startUp.main()
```
Edit boot.py with nano or your favorite editor and verify it looks like the following:
```
import startUp
import time

time.sleep(10)

startUp.main()
```
Currently sleeping for 10 seconds seems to help with TD-1 starting correctly from an initial power-on
Shutdown printer sudo shutdown now and then turn printer back on, if the delay was enough then you should see your device show up something like below when running ls /dev/serial/by-id/*
```
/dev/serial/by-id/usb-AJAX_3D_TD-1_E6625877D318C430-if00
```
If your device is still not showing up as a AJAX usb device then redo steps 4-8 and increase sleep( currently set to 10 ) by 5-second increments until it shows up.