Export to SPIDAcalc

The export writes one SPIDAcalc exchange file (.exchange.spida) for the job, with a measured design for every pole. Export after crews have synced and you’ve finished tracing.

Export the job

Open the job on the map

Click Export data in the map toolbar. In Choose export method, choose SPIDAcalc.

Review the readiness list

Cloneable builds the file from saved data and shows SPIDAcalc export readiness: what will be skipped or defaulted, and which SPIDAcalc version the file is written for. See Read the readiness list.

Download

Click Download .exchange.spida. Cloneable checks the job one more time before the file downloads.

If someone changed the job while the list was open, nothing downloads. You see The job changed since this check; review the new list and download again.

Read the readiness list

The header counts blockers and warnings. When there are none, the dialog says the file is ready to download.

Kind	What it means	What to do
Blocker	SPIDAcalc will reject or can’t resolve something, or a pole is left out.	Fix it and export again.
Warning	The file opens, but something was skipped, guessed or defaulted.	Check it. Fix it if the value matters to your design.
Information	Listed under Not exported: collected in Cloneable but SPIDAcalc has nowhere to put it, or the configuration fills it in.	Nothing to fix.

Click a row with a pole chip to fly the map to that pole, fix it, then export again. With blockers, the button reads Download anyway and asks you to confirm. Choose Review issues to go back.

If edits are still saving, or an edit didn’t save, you see Check again instead of Download. Wait a moment and click it. If an edit didn’t save, redo it, or reload the map to discard it.

Common blockers

Message mentions	Cause	Fix
No usable location	The pole has no GPS, so it isn’t exported.	Open the pole and give it a location.
Edits still saving, or an edit that did not save	The file would carry older values.	Click Check again. Redo a failed edit or reload the map.
Insulators that sit at one spot on an arm	SPIDAcalc’s analysis fails on stacked insulators.	In the tracer, use Move apart on the pole, or drag one along the arm.
Has no catalog part, pick one from the SPIDA catalog	An attachment has no part from your client file, and your client file has parts of that kind.	Open the pin in the tracer and pick the part.
An insulator SPIDAcalc won’t attach to a crossarm	The part picked for an arm insulator is a pole-mount type.	Pick the arm version of the insulator.
Truss with no moment capacity	SPIDAcalc stops Analyze on that pole.	Add the truss’s moment capacity to the client file and re-import it, or pick another truss.
Cannot be written for the chosen SPIDAcalc version	SPIDAcalc’s own conversion refuses the job for that version.	Choose a newer SPIDAcalc version in the configuration’s Project setup.

Common warnings

Message mentions	What happened	Fix
No catalog component, SPIDAcalc will prompt to map it	An attachment has no part, and your client file has none of that kind. SPIDAcalc asks you to pick one when it opens the file.	Pick the part in SPIDAcalc, or add it to your client file.
No pole type chosen, matched by height	Cloneable picked the catalog pole closest to the measured height.	Set the pole type on the pole.
No owner, exported as ‘Unknown’	The pole has no owner and there’s no default owner.	Set the owner on the pole.
Cross, in opposite order at the two poles	Two wires swap places in the span.	See Crossed wires.
Traced twice, or one pin holds two wires	A conductor was traced as two wires, or a landing is on the wrong pin.	Use Merge wires or remove the wrong landing in the tracer.
Not annotated on adjacent pole	A wire is on one pole but not the next.	Annotate it on the next pole, or end it on a dead-end.
Span skipped, endpoint unavailable	The span goes to a pole outside this job or with no GPS.	Add the pole to the job or give it a location.
Midspan with no saved height	A wire crossing on a midspan photo has no height yet.	Open the midspan card so the height saves.

The list also has sections you can skim:

Midspan heights: which reading each wire exports per span, and readings left out.
Bindings: how each SPIDAcalc value was found on your objects. Rows here usually mean a field was renamed or removed in the configuration.
Not exported: information only.

Open the file in SPIDAcalc

Use the same client file

Put the client file you built the configuration from in SPIDAcalc’s client files folder. The export names it, so SPIDAcalc matches each part.

Open the exchange file

In SPIDAcalc, open the .exchange.spida file you downloaded.

Check the model

Look over a few poles before you start designing. See below.

If SPIDAcalc asks which client part to use for an item, that part wasn’t in your client file. Pick it in SPIDAcalc, or fix it in Cloneable and export again. See Troubleshooting.

What to check after opening

Every pole is there, with the right label and tag.
Wires connect from pole to pole with no connectivity errors.
Heights look right against your field photos, including midspan heights.
Guys and anchors sit on the right side of the pole.
Analyze runs on a few poles before you design the whole job.

Then do your design and analysis in SPIDAcalc as usual.

Product guides

Tracing

Integrations

Exports

Export to SPIDAcalc

Export the job

Read the readiness list

Common blockers

Common warnings

Open the file in SPIDAcalc

What to check after opening

Product guides

Tracing

Integrations

Exports

​Export the job

​Read the readiness list

​Common blockers

​Common warnings

​Open the file in SPIDAcalc

​What to check after opening

Export the job

Read the readiness list

Common blockers

Common warnings

Open the file in SPIDAcalc

What to check after opening