Eclipse-Pro
5.30.153
8/17/2026
SCN: 5374 — Release 5.30.153

New Features

  • Segment-Referenced Punch Patterns: shape punches can now be positioned relative to the profile itself (Web, Flange+, Flange-) instead of the machine centerline. Positions are resolved at solve time from the tooling's profile dimensions (fin width, leg heights), so the same pattern produces correct positions on any machine and tooling that can run it — including profiles with unequal flange heights. Configured from a new Segments tab on the Machine Shape Table:
    • Segment Aliases: map segment names from external design software (e.g. "Flange Left") to this machine's segments.
    • Bend Compensation: formed-to-flat corrections per bend. Direction rules record which way each flange bends for a tooling code; the corrections themselves are machine-wide, by gauge, side, and bend direction. Commission one CEE and one ZEE at a gauge and every other tooling code at that gauge inherits the values.
    • Commissioning Worksheet: enter known-good positions from a sample part and Eclipse calculates the bend compensation values for you, filing each one under the bend direction it belongs to.
  • Flat View: solution rows on the Punch Pattern screen now have a visualization of the flat blank exactly as the solver computes it — true to scale, with guide lines (strip edges, web, bends, flange tips) and per-hole details showing how each position was resolved. Also works on failed solutions as a diagnostic aid.
  • Shapes: punched holes can now be drawn at their true size and shape. A new Shapes page defines the geometry for each machine shape code and the Flat View, 3D formed view, and Machine Layout all draw the actual hole instead of a fixed-size marker. Shape codes without an entry keep the old nominal marker.
  • Tooling Code Patterns: a permanent pattern can now be added to every solution for a tooling code, chosen by a wildcard on the code itself (e.g. "Z6*", or an exact code, with the most specific match winning). Useful where the extra punches depend on the profile (triangles on ZEEs with different leg heights, for example) since each family gets its own pattern.

Improvements

  • Production Summary can now report by weight instead of length. The MEASURE header is a menu; picking Weight converts each production column (Total Good, Net Scrap, Reclaimed, Running Throughput) to pounds/kg using each product's own weight per foot, so a range covering a mix of light and heavy products totals correctly. OEE, Target, Availability, Speed and Yield stay length-based. The choice is remembered between visits and travels in the report link, so it also applies to a subscribed (emailed) Production Summary.
  • The Flat View and Machine Layout visualizations can be oriented to match how the machine physically sits on the floor (flow direction and operator side). The setting is remembered per machine and shared by all users.
  • Part Printing moved from its own machine tab to the Machine Shape Table, next to Tooling Code Patterns as it only ever applied to shape punching.
  • The "Verify coils when loaded" system preferences can now distinguish between Classic and Pro validation configs.
  • Eclipse Pro cloud services will be moving from eclipsepro.app to eclipsepro.online. Added a new External Services connectivity check.
  • XL Task Error Alerts are now hidden by default. Task Errors are still visible in the Run Block chart and production events. Alerts can be enabled in System Preferences.
  • Improved sorting of many reports.
  • Replaced remaining length entries with the multi-unit aware editor control in the Machine Shape Table, Material, and Tooling Details.
  • The Tooling list now uses the same grid as Punch Patterns: per-column filters, resizable and re-orderable columns, and no paging. Leg Height and Leg Height 2 were added as columns.
  • Hovering a tooling code now shows a preview, the same way material codes do: the tooling's fin width, leg heights and profile, plus the tools behind it on each machine. Where machines disagree on a value, that column appears in the machine table so the difference is visible. The Tooling column on the Orders list is now a link as well. Works on the Orders list, the Order screen, the order hover preview, and the Tooling Usage report.
  • Grid filters are remembered when using the back button after visiting details pages.
  • The Setup Configs and Tool Configs tabs on a machine now have a snapshot picker. Eclipse has always kept every configuration the controller reported, but only the most recent one was shown; you can now pick an earlier upload — labelled with its date, software version and library — and see the configs as they were then.
  • Coil Sync Improvements:
    • The Integration config can test the configuration without first saving.
    • DB2 is now supported by rewriting the named parameter query to positional parameters.
    • Can now convert weight to length if material is known.

Bug Fixes

  • Editing a punch pattern whose name is duplicated in Eclipse (copies differing only in casing) no longer modifies the other copy as well. Because Eclipse matches names case-insensitively, the header of every same-named copy was being overwritten, which could also make the wrong copy appear to be the most recent one.
  • Fixed viewing and editing Tooling Codes with special characters, including slashes (e.g. "ZEE 6 X 2-1/8 X 2-3/").
  • Errors from the Agent for a specific request (like an unmatched route) are now reported as request failures with detail, instead of "agent unavailable".
  • Fix a navigation menu rendering issue on certain tablets.
  • The Agent could fail to sync job changes on some sites, reporting "SQL expression is too complex" from Eclipse. The Agent now sizes its queries to what the site's database will accept, instead of assuming a fixed limit.
  • It was possible to enter an invalid shift times. This is fixed.
  • Express: when the connection to an XL controller is not stable, Express would reconnect to that controller several times a second. Express now backs off a flapping connection and reports how long each connection lasted in the comm log.