Long time diverted to activities with higher priority,
now dusting off my LPS8Gateway for setup of interface to TTN_v3.
Power Supply defective, but that easy to remedy.
Red LED for power now on and blue LED flashing near Globe-symbol,
but no access possible through the IP-adresses originally set.
Reset by long press on Toggle-switch does not make any difference:
no change for the 2 LEDs
no appearance of ‘own’ WLAN, nor any IP-address upcoming on the local WLAN or LAN.
Hint appreciated how to get revived access the Gateway.
[Not yet tried to get access via the Fallback-IP]
Today also tried the way-out by means of Fallback-IP, but no luck …
No response from the LPS8 on any testing on IP-adresses or on ports in the range indicated in the manuals.
As indicated in red text in the manual, it is possible that Fallback_IP has been disabled (explaining why no reaction), but doubt very much that such setup is the case, because LPS8 was only used for initial, experimental setup for interface between sensor and TTN_v2.
Would also expect that Reset would re-enable this Fallback_IP.
Unless somebody knows a tric to enable Fallback_IP on this apparently ‘locked’ LPS8,
there seems no other conclusion than ‘end-of’very-short-life’ for this LPS8 and the need to purchase a replacement Gateway.
Does your network router see it as connected - will tell you if there is an associated IP address - you can then try to log in via that address?! Are you on Enet or WiFi? Have you tried the other connection type…
Have reset via the toggle-switch while powered.
But neither a short press&hold, nor long press&hold (>30s) does result in any difference signalled by the LEDs or at the ethernet-interfaces.
Have tried to access the LPS8 with test-PC at same LAN-segment, using IP_Scanner,
but within the designated IP-ranges no detection of new (or old) IP-identification which might be LPS8.
Also checked within designated IP-ranges at WLAN with a test_PC and wide-band with Wifi-scanner,
but no sign-of-life looking as LPS8.
Have tried to make cabled connection by means of Fallback_IP with laptop (as described in the manual), without luck.
Just pressing the toggle switch doesn’t reset it, you need to push it before applying power and then count the led flashes (5 I think) before releasing. Note that it will then be in a recovery mode with a different IP than the standard or fallback IP. This is described in the manual or wiki.
Did not find such procedure in the available manuals, nor by Google-search.
After looking in comparable descriptions, used this one, seeming appropriate:
Where is this different procedure in (which) manual and where in wiki?
[Preferred to read the complete text, for better/correct understanding].
Diverted by other projects, took a few years before restarting activities for LoraWAN.
Apparently meanwhile my LPS8 ‘died’ not of heavy use, but of neglect and change of the environment …
Anyway, now considering to change to the ‘improved version’ LPS8v2.
As layman reading the description for LPS8v2, comparing with LPS8, it looks as if with LPS8v2 it is possible to extract sensordata direct from that Gateway, not from TTN’s server. Is that correct interpretation?
If yes, what is simplest realisation for setting the sensor-node and the related read-out from the Gateway? Where related manual?
Not using TTN would make this off-topic for this forum.
Your apparent lack of enthusiasm for engaging with the manufacturer for basic information (qf, your bricked LPS8) is puzzling - are you hoping that a volunteer here will research the URL and post it for you?
May be heavily influenced by your comment in other thread wrt
“Power Supply defective, but that easy to remedy.”
Are you sure as it died it didnt do damage to the GW - it happens - even a transient issue that does not release the magic smoke but just causes problems thereafter… try the full reset also suggested in the thread - sounds like not only are you not looking for urls but also not reading/searching the available manuals, documetation, wiki’s, etc…
There are many GW’s on the market with an internal LNS option but as Nick says if you use these and don’t connect GW to the Community Network instead (never try ‘as well as’!) you are then off topic and not supported on the Community Forum… your call…
Not a lack of interest to link with TTN’s network; contrary, that is my aim, because then common faciltities & experience can be used.
But it is lack of experience (with the earlier setup was still in ‘learning curve’), and uncertain / lacking knowledge, even after reading the available manuals and descriptions.
Thinking about which options available before planning next action:
that takes some time …
Perhaps better located in the other thread, but for completeness:
arguments how I came to conclusions.
Why suspecting & replacing the PowerSupply (when again connected after long time)?
Power USB-cable for setup checked before and is OK
LED for Power on LPS8 is continuously on in combination with LED flashing on the PowerSupply, with rythm of flashing and level of light dependent on how the microUSB-connector was in the housing of the PowerSupply
LED of LPS8 is out when the LED on the PowerSupply is continuous.
=> might be sign that USB-interface/connector at side of PowerSupply is wobbly/defective
Using an alternative PowerSupply (elsewhere proven to be OK) gives LPS8 a steady Power-LED and flashing LED for ‘Globe’, which seems a sign that power entering the LPS8 now OK…
But next testing the various options for access to the LPS8, no entry found:
if no remote entry in view, what to ask from Dragino.com?
Not seeing any other signs of progress after various testing, tend to agree with Jeff that possibly the circuitry of the LPS8 has been hit and/or damaged.
Now checking the PowerSupply circuits within the LPS8, which has to be done most careful, not having schematics and considering the narrow traces => takes time.
If PowerSupply within LPS8 tested corrupt, then question:
how to repair (and worth to repair)?
If PowerSupply within LPS8 tested OK, the question:
how to get entry for testing of the processing?
That may be time to formulate questions to Dragino.com, because the onboard connector might be a useful entry for such testing.
Anyway a trade-off between further effort for test&repair (considering own skills & knowledge & tools) and purchase of new device.
For such purchase then various options and (not having the information) asking questions (in this thread) to explore some options.
To me seems a pragmatic approach taking some time,
but if somebody has ideas for better plan of attack, much appreciated to hear …
Note: in the ‘other thread’ GerbenvdBerg hinted on a different reset procedure, which I will try tomorrow.
As SystemEngineer with more than 35 years of experience (specialised in InterfaceEngineering) I only ask questions if I can properly formulate them ‘holistically’, not trickling ‘unmatured’ pieces:
that is after investigation of all possible aspects within global view…
Now just collecting information for that purpose (incl. testing where required & possible). I am in retirement, and therefore in no hurry …
So you are spinning the wheels of the volunteers on this forum by exploring the topic before asking the manufacturer for advice on restoring the LPS8.
There is the suggestion given above which you could ‘just try’ - finding a manual on ManualsLib seems a bit random when Dragino, whilst not the best organised body of information, has rather a lot of info on it’s website, it’s wiki, it’s download area, GitHub and DropBox.
If you want to cut to the chase of fixing the LPS8, that’s fine. But there is limited capacity amongst us all to contribute to the forum, so if this is a leisure activity you may not get such responsive help.
Unfortunately, those weblinks in Kilight’s message were part of earlier tests, without result.
This morning executed Gerben’s suggested approach for reset.
Has some different effect, because at power-up I see all LEDs flashing,
but then followed by ‘dead’ silence with only the red ‘Power’-LED on, and no further activity seen:
Checking with IP-scanner at (W)LAN, no signals looking like LPS8.
With WiFi-scanner no signal looking like LPS8.
Subsequent Power Off+On results in same situation as after other power resets:
red ‘Power’-LED steady on, and blue ‘Globe’-LED flashing.
=> Those other LEDs flashing at Gerben’s way of reset seems sign that still life in the LPS8,
but not yet the proper procedure.
No other approaches in view => ideas for reset/revival exhausted
=> Dragino has been contacted.
Looks like you are doing all by Wi-Fi? Have you tried direct wired enet connection to hub/router on same segment as management device (pc?). I recall one of my early LPS8’s being ‘sticky’ to a mobile phone hotspot I used to set it up. Even though operational on another link whenever I walked close by with phone/hotspot on it would jump to use that and then not recover back to wired or other wifi options when the hotspot went out of range (I often have iPad tethered to phone so I can do live coverage checks monitoring TTN console etc. so each time I left home office/lab the LPS8 would see the hotspot as I exited the building!). IIRC a firmware update fixed the problem (3-4 years back so vague!) along with shutting down the wifi on gw. It’s permanently on wired these days…
Certainly not “doing all on Wifi/WLAN”:
instead concentrating on LAN-entry, because of similar experiences like you describe.
WLAN-interface is nice for initial entry or for backdoor, but trying to suppress unexpected, unwanted interference from ‘outside agencies’. That risk is real, because (suburban) environment here is heavily occupied by 2.4GHz-traffic.
Is one of my setup goals, that once this LPS8 becomes operational, all ethernet-traffic for exchange & control is by LAN.
During testing, to cover all opportunities, each time after a reset experiment I look(ed) at WLAN for signs of life from LPS8, but no luck.
For WLAN and LAN not a shared router, because some routers play tricks between WLAN and LAN, but on purpose WLAN and LAN controlled by 2 different routers, to have IP-adressing firmly in hand.
The LPS8 continuously is at same LAN-ETH-switch as my testing PCs for shortest, direct, cabled route.
Concentrating on trying to get entry via the LAN-port, via the ‘usual’ IP-addresses incl. the Fallback_IP and each time looking with Advanced IP-scanner over wide range, trying to cover all IP-adresses at which LPS8 might pop up after reset, without success …
After Gerben’s way of reset I see at power-up 2 flashes of the red ‘ETH’- LED before the blue ‘Globe’-LED starts flashing, but unfortunately that’s all life detected for the LAN-port.
No flashing at all for the ‘Wifi’-LED: more reason to concentrate on LAN-functionality.
not of heavy use, but of neglect and change of the environment …