Juki#

Juki is the SMT line vendor whose feeder / placement system ManexCloud integrates with. The integration syncs part / MPN / reel data from ManexCloud into Juki so that lines can be programmed without manual re-entry.

What is synced#

• Items — part number, description, manufacturer, MPN.
• Reels — reel identity, MPN, brand, on-hand quantity.

JukiHelper.CreateNotExisting is the entry point that creates or updates items / reels via Juki’s URL-based API.

The escape-map trap#

Juki’s URL parser has a non-standard interpretation of certain characters (e.g. it decodes + as space, so an MPN like DS1818R-5-U+ becomes DS1818R-5-U and later V2_board_create lookups fail with “provided mpn is not present in the system”).

ManexCloud protects against this with the §§APIESCCHARnn§§ escape mechanism in JukiEscapeMap (MD-4586 and the follow-up patch under juki.patch / Jukiv2.patch). Any user-data field written to Juki (item_code, item_description, reel_itemcode, reel_partnumber, reel_brand) must be run through EscapeForJuki before being appended to the URL.

The current escape set covers the URL-sensitive punctuation Juki flagged: |, {, }, @, +, ., :, ;, <, =, >, ?. Extend the map if new failures surface — but always add on the Juki-vendor-verified side, not by trial and error.

There’s also TSQL/Juki_AVL_Duplicate_Cleanup.sql — a maintenance script that deduplicates AVL rows created by earlier iterations of the sync.

Business rules#

• Never send un-escaped user data to Juki — the escape map exists to protect against a real production failure mode.
• Manufacturer resolution is configurable — web.config JukiManufacturer chooses between Manufacturer_Name and PartMfgr as the source field.
• Sync should be idempotent: item_create_or_update is safe to re-run; reel_create is not (it will duplicate), so guard by checking Juki state first.

Where it lives#