How to Connect Your Sensor (and Common Mistakes)

Though simple, customers may occasionally experience connectivity woes because they are connecting their sensor to their iPad incorrectly.

This article is intended to cover the most common ways customers have incorrectly connected their sensors to their iPads.

How to Connect your Sensor Correctly

But first, let's make sure you are connecting your sensor correctly.

  1. Locate your lightning cable or USB-C cable (depending on your iPad model). This is a short, black cable:

    Please note: the older, white cables manufactured for the original Structure Sensor will also work.

  2. Connect the sensor end of the cable to your sensor with the pins facing down. Gently but firmly connect it so as not to damage the pins. You will feel a click when the cable is fully inserted.

  3. Connect the lightning or USB-C end into your iPad.
  4. That's it! You're connected!

Common Mistakes

  • Do not try to connect your sensor to your iPad using the long, white charging cable. This cable is meant for charging the sensor, and every sensor ships with this cable. However, attempting to connect your sensor to your iPad using this cable will not work. Use this cable to charge your sensor and to connect ST02A models to Skanect 1.11.
  • Do not charge your cable using the lightning cable. These cables are only intended to carry data, not power. You will be unable to charge your sensor with them.
  • Do not connect your sensor using an adapter. If you ordered a USB-C cable accidentally, do not purchase a USB-C to lightning cable adapter. Your sensor will not work with this adapter. Instead, reach out to support to arrange an exchange for the correct cable. You can find additional cables for purchase on our accessories page.
  • Do not bend the cable at sharp angles. The wires within the cable are made to be resilient, but every material has a breaking point. Broken cables due to customers' carelessness are not covered under our manufacturer's warranty.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.