Skip to main content
Most export problems show up in SPIDAcalc export readiness before you download, and many show earlier in the tracer’s Issues panel. This page covers the common ones and what you see in SPIDAcalc.

​
Setting up

SPIDAcalc support is switched on per organization. Contact Cloneable support.
Only organization admins can create configurations. Ask an admin to build it.
The builder needs your .client catalog. To bring a project in as a job, use Add job → Import from KML instead. See Import a SPIDAcalc project.
Re-importing a client file updates parts only. Build a new configuration from the new file to collect new forms. See When your client file changes.

​
Opening the file in SPIDAcalc

Cause: an attachment in the file isn’t a part in your client file. Either nobody picked a part for it in Cloneable, or the client file in SPIDAcalc isn’t the one the configuration was built from.Fix: put the same client file in SPIDAcalc’s client files folder. In Cloneable, open the attachment’s pin in the tracer and pick its part, then export again. The No catalog part issue lists every one.
Cause: the wire is a different type at its two ends, for example a primary at one pole and a neutral at the next. This usually means one pin is labeled with the wrong wire type.Fix: in the tracer, look for Crossed wires issues whose pins say Wrong type?. Click each ringed pin, check its type against the photo, and change the wrong one. Export again.
Cause: two wires are in one order at one pole and the opposite order at the next, so they cross in the span.Fix: open the issue in the tracer and click Swap them. See Crossed wires.
Cause: the pole photo isn’t calibrated, or heights aren’t on for the configuration.Fix: calibrate the pole’s measurement photo, or set the height by hand on the pin. The No height issue lists every one. Your admin can turn on Annotator heights (beta) in the configuration’s Project setup.
Cause: the truss’s part in your client file has no moment capacity table. SPIDAcalc stops Analyze on that pole.Fix: add the moment capacity in your client file, re-import it on the configuration’s Pick list step, and export again. Or pick another truss on the pin.
Cause: two insulators sit at the same spot on one arm.Fix: in the tracer, open the pole and click Move apart, then fine-tune the position on the arm.
Cause: the span runs to a pole that isn’t in this job, or to a pole with no GPS. Cloneable leaves it out and the readiness list says the span was skipped because an endpoint is unavailable.Fix: add the far pole to the job, or give it a location, and export again.
Cause: a wire crossing on a midspan photo has no saved height yet.Fix: open that midspan’s card in the tracer so the height saves, then export again.
Cause: no pole type was chosen, so Cloneable matched the catalog pole closest to the measured height.Fix: set the pole type on each pole, then export again.
Cause: the pole has no owner and the client file has no default owner, or the default owner was left out of the list.Fix: set the owner on the pole.

​
Downloading

Some edits were still saving, or one didn’t save. Wait a moment and click Check again. If an edit didn’t save, redo it, or reload the map to discard it.
Someone edited the job while the list was open, so nothing downloaded. Review the updated list and download again.
Check Not exported in the readiness list. It names what SPIDAcalc has nowhere to put, such as buildings and embedment. If you’re exporting for an older SPIDAcalc version, also check the Not in section.
Still stuck? Message us from the chat in Cloneable and include the job name and what the readiness list says.