Jump Data; Order Of Configuration And Sewing Data - SunStar SSP-WE/3.5 Instruction Manual

Jump Data

If two different sewing data exist, Jump data always exist between them
and is automatically created.
Upon initially creating sewing data as shown in the left
picture, Jump data is automatically created from the
origin. You can find that Jump data is automati-cally
created at the sewing data section too. And Jump data
is automatically deleted upon deleting sewing data.
And new Jump data is again created between the
deleted sewing data conforming to the front and back
sewing data. The Jump data cannot be edited and it
always indicates with a gray dotted line.

Order of Configuration and Sewing Data

The order of sewing data is created regardless of that of configuration data.
That is, the sewing data is always created accord-ing to
the constant order, and the configuration data is
connected with the sewing data regardless of the order.
For example, if four configuration data are created is the
left picture, it is assumed that the configuration data is
numbered with 1, 2, 3 and 4, and the sewing data with
[1], [2], [3] and [4]. If you create sewing data with
Configuration Data 4, Sewing Data [1] is created.
Therefore Sewing Data [1] includes Configuration Data
4. And, if you create Sewing Data again with
Configuration Data 3, it is automatically jumped with the
Sewing Data [1] created above and Sewing Data [2] is created. And Configuration Data 3 is
connected with Sewing Data [2]. If you create Sewing Data with all Configuration Data like this,
the Sewing Data is created according to the order shown in the above picture. And you can
select Replay Tool to find the creation order.
4[1]
3[2]
1[3]
2[4]
35