<![CDATA[PAC and ID for SiPy + SiPy firmware update]]>I have the 1.0.0.b3 version of the update tool but I can't see SiPy listed in the devices.

According to the topic (SiPy details), I can find the PAC and ID through the update tool (which need to register my SiPy onto the Sigfox backend).

Can someone please confirm if I have the right version of the update tool and what I need to do to update my SiPy and find the PAC/ID?

Thank you.

]]>https://forum.pycom.io/topic/583/pac-and-id-for-sipy-sipy-firmware-updateRSS for NodeSun, 06 Sep 2026 11:12:38 GMTTue, 31 Jan 2017 22:37:07 GMT60<![CDATA[Reply to PAC and ID for SiPy + SiPy firmware update on Tue, 31 Jan 2017 22:37:07 GMT]]>I have the 1.0.0.b3 version of the update tool but I can't see SiPy listed in the devices.

According to the topic (SiPy details), I can find the PAC and ID through the update tool (which need to register my SiPy onto the Sigfox backend).

Can someone please confirm if I have the right version of the update tool and what I need to do to update my SiPy and find the PAC/ID?

Thank you.

]]>https://forum.pycom.io/post/3637https://forum.pycom.io/post/3637Tue, 31 Jan 2017 22:37:07 GMT<![CDATA[Reply to PAC and ID for SiPy + SiPy firmware update on Wed, 01 Feb 2017 00:02:23 GMT]]>The necessary update tool isn't ready yet, should be coming out soon.

Daniel from Pycom just posted an update about it: https://forum.pycom.io/topic/562/sipy-is-sigfox-ready/6

]]>https://forum.pycom.io/post/3639https://forum.pycom.io/post/3639Wed, 01 Feb 2017 00:02:23 GMT<![CDATA[Reply to PAC and ID for SiPy + SiPy firmware update on Wed, 01 Feb 2017 00:05:19 GMT]]>@jmarcelino
Is there any other way I can get the PAC and ID?

]]>https://forum.pycom.io/post/3640https://forum.pycom.io/post/3640Wed, 01 Feb 2017 00:05:19 GMT<![CDATA[Reply to PAC and ID for SiPy + SiPy firmware update on Wed, 01 Feb 2017 00:14:51 GMT]]>@sk
No, Sigfox only assigns ID/PAC combinations to certified hardware manufacturers so short of becoming one yourself you'll have to wait until Pycom is ready to distribute the ones they have.

Should really just be a few days now, just them getting the server in place. The most time consuming part - getting the SiPy through certification - was finished last Friday.

]]>https://forum.pycom.io/post/3641https://forum.pycom.io/post/3641Wed, 01 Feb 2017 00:14:51 GMT<![CDATA[Reply to PAC and ID for SiPy + SiPy firmware update on Wed, 01 Feb 2017 00:25:12 GMT]]>@jmarcelino Thank you. That's what I needed to know :)

]]>https://forum.pycom.io/post/3642https://forum.pycom.io/post/3642Wed, 01 Feb 2017 00:25:12 GMT