Repository navigation
OpenECraft 0.1.1
·
64 commits
to master
since this release
Immutable
release. Only release title and notes can be modified.
- PV arrays on roofs: rows of solar modules on every roof shape, parallel to a slope
on rails and roof hooks or on a flat roof tilted or east-west on ballasted mounting
bases. The mounting material (rails, connectors, roof hooks, end and middle clamps,
mounting bases, ballast, wind deflectors) follows from the modules and goes into the
bill of materials with them; it comes from a mounting system of the parts database
or from generic parts. New shipped catalogslongiandjinkowith PV modules; the
check reports arrays across a ridge or off the roof, over roof windows or each other.
Commandsadd_pv_array,set_pv_array(panel layout). - PV strings: the modules of a PV array in series and in parallel as strings on the
MPP trackers of inverters and charge controllers, with their highest, mean and lowest
voltage, currents and power at the design cell temperatures; the report PV strings
lists them, the check reports strings above the input voltage of their inverter or the
system voltage of their modules, outside the MPP range, beyond the trackers or their
currents. Commandsadd_pv_string,set_pv_string,pv_strings
(panel layout). - Doors and windows open either way or slide: hinges at the left or right, opening
into or out of the room, or a sliding leaf; drawn so in the floor plan and the wall
view, the check keeps the way of sliding doors free. Commandset_wall_opening,
opensforadd_wall_opening. - Site in the navigator: the site at the root above the buildings shows the site
plan of all buildings or the whole plant in 3D; a click on a room keeps the 3D view or
shows its floor plan; new buildings and levels from the context menus. - Flush-mounted cables, wires and tubes in rooms: each line is laid surface-mounted,
flush-mounted in the walls or in the floor (a project default in the routing rules,
set per line in its properties or withset_laying). Flush-mounted lines run in slots
of a configurable depth along the installation zones, preset to those of DIN 18015-3
and editable (installation_zones), or down into the floor and along its zone.
Show › Installation zones shows the zones see-through, Show › Open walls and
floors sees through walls and floor slabs to the lines in them
(panel layout). - Stairs and roofs of buildings: stairs from level to level, straight, turned once
or twice at quarter landings, with a half landing or spiral, their steps from the
difference in height; flat, shed, gable, hip and pyramid roofs with roof windows. A
roof lower than the ceilings below it slopes them, also on several levels: rooms get
different heights at different places, their walls end under the slope, and the
check reports cabinets and wall items above it. Show › Whole building shows a
building in 3D with its floor slabs, stairs and roofs. Commandsadd_stair,
set_stair,add_roof,set_roof,add_roof_window,set_roof_window
(panel layout). - Outlets, switches and heating circuit manifolds in rooms: Insert › Outlets,
switches, heating places socket outlets, data and antenna outlets, switches, push
buttons and room thermostats at their mounting heights, heating circuit manifolds
(2 - 12 circuits) and single-room control boxes; generic parts and the new shipped
catalogsgiraandcosmo, more KNX push buttons inmdt. Example 16
(office_building) shows them with a stair and a roof. - Rooms onto levels in the navigator: in Enclosures and rooms rooms are dragged
onto a level of a building to stand on it; a selected level takes the rooms made with
New room, and the context menu of a level offers New room on this level
(panel layout). - Updates in the editor: when it starts, the editor looks for a new release on
GitHub in the background, downloads it, checks it againstSHA256SUMSand installs
it: the Windows setup runs silently when the editor is closed (Restart and update
in the status bar starts it again afterwards), an AppImage and the macOS apps are
replaced at once; packages of a distribution are only told of the new version.
Without a connection nothing waits. File › Help › Check for updates looks at any
time; Settings › Updates andOPENECRAFT_NO_UPDATE_CHECKswitch the check at start
off (installation). - Docker images of the servers: the parts server and the project server are
published asghcr.io/nilres/openecraft-parts-serverand
ghcr.io/nilres/openecraft-project-serverwith every release (<version>,latest)
and every push to master (edge);installer/docker/compose.yamlstarts both
(installation). - Directed T-junctions (target tracing): Insert › Connections › T-junction
places a junction where three wires meet that names the device the two wires of the
connection start from and the order of their targets, with four directions and four
variants each as in the connection symbols of EPLAN; the connection list, diagrams,
panel wiring and harnesses follow it, connections without one keep the schematic
order. The junction can be drawn as a dot without losing its routing, turns and
mirrors with the drawing, is kept in the project file and the undo history, and is
checked against its wires (Connection symbols check). Commandsadd_t_junction,
update_connection_symbolandlist_connection_symbolsfor the command line and the
MCP server (#96). - Corners for automatic wiring: Insert › Connections › Corner places a connection
symbol with two arms at a right angle; with Auto-connect on, connection points that
face the free arms of a corner or a T-junction are wired to it when the symbol or the
device is placed or moved, so a corner at the meeting point of two connections wires
both of them in. Commandadd_corner(withautoconnect), andautoconnecttakes
connection symbols too (#96). - Directed crossings and bridges: Insert › Connections › Crossing connects the two
wires crossing at its point (unconnected without one) and leads each end of its
vertical or horizontal line straight on first and across second, in two variants;
Bridge leads a connection from one side to the three others, the opposite side
first. Both follow the connection symbols of EPLAN, can be drawn as a dot and keep
their routing, and the check reports a connection its symbols wire in a loop. Commands
add_crossingandadd_bridge(#96). - Editor: wires attached to moved items stay square: they slide along their rails,
or get a jog where they cannot. Connection definition points and cable definition
lines stay on their wires. - 3D routing in cabinets without cable ducts: their wires are no longer laid
along the mounting plate (through the devices and each other) but routed in 3D from
connection point to connection point, like the wires of a room: clear of everything
by half their thickness, bent with their radius only, each on a way of its own. A
wire that finds no such way is reported as an error instead of being drawn. - 3D routing: a route leaves a connection point that lies inside the box of its
device straight through that box, never through another device to the room behind
it; its last bend may lie where the straight way into
its end begins; the straight way out of every connection point and cable entry stays
free until its own route is laid; a cable between two cabinets that stand in no
common room is routed to a cable entry in each of them; every cable takes an entry of
its own; in the 3D view a cable passing from one cable duct into the next keeps under
the cover of the first. - Bend radius in the 3D view: ways laid side by side change lanes on a slanting
piece of a stretch instead of a step at the corner (which was rounded with a radius
of a millimetre or two); a route is drawn straight out of its connection points, its
first corners moved onto that line, instead of with a kink onto the routing grid; a
jog shorter than the bends of its corners is an S-curve of the bend radius also where
the stretches before and after it lean; bends are drawn as fine arcs, so that ways
round one corner are not pushed apart where only their drawn arcs met; a cable ends
on its bend where its cores part right behind a corner. - 3D routing, crossings: routes that come together lie side by side, a route no
longer runs across another one (only on its own way out of a connection point, or
where it comes up to the device the other one ends at, and there it goes round the
other one too where that costs little); the way out of a connection point is shared
only by a route out of a point right beside it; of the wires of a cabinet as thick
as each other the shortest is routed first, so that between two devices the inner
conductors lie nearest to them and the outer ones go round them. Two wires that
still cross right at a device are lifted over each other more sharply than their
radius allows. - Cable entry flanges: the cables through one flange go through its membrane side
by side, each at a place of its own (the cable's thickness and a centimetre apart,
the free place nearest to where the cable heads) instead of all through its middle;
the cores of a cable part within the box of their ends, so that a core no longer
swings out past its terminal into the bars it sits on. - Busbar holders in the 3D view: drawn at the drilling positions of the plate (a
holder 25 mm from each end and every 250 mm) instead of every 400 mm, and moved
beside the devices that sit in the bars (current transformers the bars pass through)
instead of through them. The bars, their holders and the boxes of busbar terminals
and strip elements without a model were wound inside out: the view showed their
far faces, which flickered against the holders behind the bars and the plate. - Messages of the 3D routing: a message about a cable, hose or wire (not
routable, bends too tight, frozen route lost, hose too short) points at a connection
point of it: a double click in the messages pane jumps to the schematic. The 3D
view marks a cable, tube or wire that could not be routed (and so is not drawn)
with a red note at each of its ends, with the reason. - Busbar terminals in the 3D routing: each terminal of a strip across the bars is
a solid of its own: a wire to one of them goes round the others instead of through
them (a cable whose cores end at several of them comes up through those). Terminals
closer than 30 mm along the bars are entered from the front: their points facing a
neighbour leave to the front, as a wire has no way out between them. - Cores at busbar terminals: a cable ends clear of the device its cores go to,
and the cores to terminals one above the other on the bars pass the lower terminals
in front of them instead of through them. In example 13 the supply cable comes to
its busbar terminals from below, through a gland in line with them, instead of
looping round the field to come down onto them. - 3D routing, ends: a route comes into an end against the direction it leaves it
in also where the way out is a single cell (it could run past the connection point
and back into it); where the way straight out of an end is barred and the route
starts from the cell beside it, the way out must be long enough for an S-bend of the
bend radius onto that line; cable glands of the examples lie in line with the
connection points they serve. - Busbar systems: the systems of bayed enclosures that meet at their common side
are one system (devices on it are connected by its bars in either enclosure); a
section shorter than the system is wide lies along its bars; the connection points
of repeated accessories (a current transformer behind each pole of a strip) are told
apart by their number (2S1). - Parts: current transformer sets with their connection points (primaries through
from the bottom to the top, secondaries on a terminal block), the leads of the
transformers behind NH strips. - Examples 13 and 14 rebuilt so that every conductor can be laid: power flows
through the fields from one device into the next, busbar cross-sections run over
bars (transformer sets in the busbars, the distribution busbar through both cabinets,
coupling switches fed from busbar terminals), taps to small devices have their own
cross-sections; the string fuses of the generator junction box of example 11 stand
above their terminals. - Buildings: buildings with levels and shafts in the plant; rooms stand on the
levels and move with their building, shafts and links between buildings (cable
trench, conduit, cable bridge between building entries) carry routes from room to
room; devices go on the outside of the walls and on the roof; a Buildings pane with
a site plan, the pluginbuildingswith its commands, a check and example 15. - Servers: a very long project or manufacturer name no longer overflows the stack
of the access check (wildcards of grants and report blocks are matched without
recursion), and failed sign-ins with an empty user name are no longer counted twice
against the client. Two sign-ins of one user at the same time on the parts server
both keep their session, and a sign-in no longer brings back an account deleted or a
password changed meanwhile. Replies to review comments on the project server keep
the name of their author only while unchanged, so nobody writes under another name
by putting a reply before theirs. - MCP server: the project files of
batch_project_properties(files) and the
macro libraries ofgenerate_pages,update_macro_boxesand
generate_preplanning_pages(macros) must lie inOPENECRAFT_MCP_ROOTlike all
other files; folder ids of the vault tools are no longer taken for paths. - Parts server: importing parts that exist already (CSV, BMEcat, EPLAN XML) keeps
their data sheets, pictures and other files instead of removing them. - Project archives: documents and images of the same name are numbered inside
thefilesfolder (files/2 …) instead of in a folder2 filesof their own. - Use the DIN-rail clip position from imported mounting data when placing cabinet devices. Matching Beckhoff terminal housings and the EK1100 use the documented 63.8 mm rail datum.
- Snap cabinet devices flush to a nearby neighbor on the mounting plate while placing or moving a single module. The placement preview shows the snapped position.
- Show imported EPLAN artwork on cabinet fronts. An assigned front view takes priority, followed by a mounting representation and then a fitted overview illustration.
- Place successive imported PLC channels from a single card entry in the Insert center; when a card fills up, placement continues on a new device.
- Link PLC channels placed from the symbol library to their uniquely matching catalog article, so the physical card appears once in the cabinet's devices-to-place list. Opening an existing project or reimporting the article also recovers unassigned cards.
- Import Beckhoff analog signal and reference terminals as one PLC channel with a symbolic name such as U1, keeping both wire endpoints and the source data type.
- Import single-channel EPLAN digital I/O representations as native PLC points with editable addresses, physical terminal designations, and one parts-list entry per card.
- Reuse unchanged symbol drawings during part dragging and schematic rendering, including large imported EPLAN libraries.
- Import embedded 2D graphics from EPLAN window macros into the project symbol library. EDZ parts carry their converted variants and per-variant diagnostics through the parts server.
- Import additional SPECIAL contact forms and verified reciprocal potential transfers. Report unresolved source objects and their terminal designations per representation. Explicit reimport preserves placed wire endpoints and instance pin labels when compatible contacts are added.
Downloads
Check a download with sha256sum -c SHA256SUMS --ignore-missing.
Its origin (build provenance of this workflow) with gh attestation verify <file> --repo nilres/OpenECraft.
The licenses of the libraries and fonts the programs contain are in THIRD-PARTY-LICENSES.html.
Docker images
The parts server and the project server as containers (docs/installation.md):
docker pull ghcr.io/nilres/openecraft-parts-server:0.1.1
docker pull ghcr.io/nilres/openecraft-project-server:0.1.1The Windows setup is not code signed: SmartScreen asks for confirmation on first start (More info › Run anyway).
The macOS apps are not notarized: Gatekeeper asks for confirmation on first start (System Settings › Privacy & Security › Open Anyway).