10O / 100

Status

Field	Value
Extension(s)	.10o, .100
Common ecosystem	Toyota embroidery format lead
Format family	Machine-specific file
Satin Studio status	Researching
Open / import	No
Export	No
Confidence	Low-medium.

What it is

10O and 100 are reported for Toyota embroidery machines in conversion and format lists.

Satin Studio direction

Research lead only.

Versions and variants

The two extensions may represent related Toyota encodings rather than aliases.

File identification notes

Reported details:

• .10o: unsigned x, y, control encoded stitches, with a separate .00o sidecar carrying color information.
• .100: four-byte records with two control bytes followed by signed x, y bytes.

These details need validation before Satin Studio probes or imports by extension.

Observed structure notes

• .10o has been observed as three-byte records in control, y, x order. control bit 0x20 negates X and bit 0x40 negates Y after the Y axis is inverted for embroidery coordinates.
• .10o command observations: low five bits 0x00 stitch, low five bits 0x10 jump, 0x8A start, 0x85 color change, 0x82 stop, 0x81 trim, and 0x87 end.
• .100 has been observed as four-byte records. Byte 0 carries command state, byte 2 is X, and byte 3 is Y. Values above 0x80 are treated as negative magnitude rather than ordinary two's complement in observed readers.
• .100 command observations: byte 0 0x61 stitches, byte 0 with bit 0x01 set jumps, and other non-end control states are commonly interpreted as color changes.

Structure sketch

The Toyota leads need separate record shapes:

struct Toyota10oStream<'a> {
    records: &'a [Toyota10oRecord],
}

struct Toyota10oRecord {
    control: u8,                       // bit 0x20 negates x; bit 0x40 negates y
    y: u8,
    x: u8,
}

enum Toyota10oCommand {
    Stitch,                            // control & 0x1F == 0x00
    Jump,                              // control & 0x1F == 0x10
    Start,                             // control == 0x8A
    Trim,                              // control == 0x81
    Stop,                              // control == 0x82
    ColorChange,                       // control == 0x85
    End,                               // control == 0x87
}

struct Toyota100Stream<'a> {
    records: &'a [Toyota100Record],
}

struct Toyota100Record {
    control0: u8,
    control1: u8,
    x_magnitude_or_signed: u8,          // observed negative-magnitude rule above 0x80
    y_magnitude_or_signed: u8,
}

What we still need

Toyota-format files, sidecar examples, and machine/software provenance.