Jump to content
psander

Tetra initial setup, NOT firmware recovery

Recommended Posts

I purchased a WiFi Pineapple Tetra a while back, and unboxed after storing it for over a year.  Using the supplied Y-cable, I plug the micro-USB end into the Tetra's ETH port and both USB-A connections into a powered USB hub.  Only one of the ports on the hub lights up, the one with the plug having both cables attached.  (The light on the port with the plug connected to the single thin cable does not illuminate.)  In my Mac's Network Preferences, I named a new interface "Pineapple - Tetra".  That interface alternates between the "Unplugged" (cable not connected) and "Not Connected" (cable connected but computer does not have an IP address).  I observed it once briefly getting an IP address before going into the Unplugged state.  This is true even if I plug in the AC adaptor for power.   I did not hold the reset button while powering-up the Tetra.

I loaned the device to a friend who has set one up successfully in the past, and she says it doesn't work and I should return it.

I suspect a bad cable.  I don't see a replacement cable offered on the web site.  What do I do next?

 

Share this post


Link to post
Share on other sites

I think I've eliminated the cable.  I plugged in the AC adaptor, then used a standard USB-A to micro USB cable plugged into the Tetra's ETH1 port.  Same result as described above.  So the Tetra may be defective.

Share this post


Link to post
Share on other sites

I continued to experiment with the standard USB cable and the AC adaptor plugged in.  When I first apply power, a blue lamp flashes on the Tetra, and after a few seconds the network interface goes from the Unplugged to the Not Connected state.  Sometimes the blue lamp goes solid and after several more seconds the Mac interface gets a self-assigned IP address.    Then an amber lamp on the Tetra illuminates (the blue one extinguishes), and the Mac interface alternates between the Unplugged and Not Connected states.  Then all lamps on the Tetra extinguish, and after a few seconds the blue one starts flashing again and the process repeats.

It now appears that there is some instability in the Tetra's power supply.  This is a Tetra MK5.8.

Share this post


Link to post
Share on other sites
48 minutes ago, Jtyle6 said:

I used the Y cable first, as directed in the quick start card, as described in the initial problem statement.  I did try it again later, and no joy.  According to the cited article:

The recommended and only guaranteed power method is by using the included 12V DC adapter.

 

Share this post


Link to post
Share on other sites
56 minutes ago, psander said:

I used the Y cable first, as directed in the quick start card, as described in the initial problem statement.  I did try it again later, and no joy.  According to the cited article:

The recommended and only guaranteed power method is by using the included 12V DC adapter.

 

To make sure it is not a firmware issue, have you tried putting it in recovery mode? https://docs.hak5.org/hc/en-us/articles/360010471774-Firmware-Recovery

If it unstable in recovery mode with the 12 volt supply / y cable connected via USB ETH port than you possibly have a defective device.  It is not impossible that both your supply and y cable are bad but unlikely both are defective causing the issue.

Share this post


Link to post
Share on other sites

I followed the recovery procedure recommended by Cap_Sig.  After the second attempt, the Tetra presented its normal set-up interface.  After setting up, it presented its normal UI.  I'll leave it running for the day and see if it's still operating normally in 12 hours or so.

Thanks much for the help, Cap_Sig and Jtyle6!

Share this post


Link to post
Share on other sites
On 10/2/2019 at 12:19 PM, psander said:

I followed the recovery procedure recommended by Cap_Sig.  After the second attempt, the Tetra presented its normal set-up interface.  After setting up, it presented its normal UI.  I'll leave it running for the day and see if it's still operating normally in 12 hours or so.

Thanks much for the help, Cap_Sig and Jtyle6!

Glad to here it helped 👍

Please report back the status after testing. 

Share this post


Link to post
Share on other sites

I let it soak idle for about a day and a half, and its uptime says 1 day, 13 hours.  This isn't much of a test, but the lack of instability at this point using the factory firmware (v2.4.1) is promising.

Share this post


Link to post
Share on other sites
4 hours ago, psander said:

I let it soak idle for about a day and a half, and its uptime says 1 day, 13 hours.  This isn't much of a test, but the lack of instability at this point using the factory firmware (v2.4.1) is promising.

Good deal.  Stable updates of modules for firmware 2.6.1 are starting to be released so hopefully updating firmware to test will be an option for you soon.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...