I am confused as well. The page you link to states right at the top of the page:
Our IoT LoRa Node pHAT allows you to create an inexpensive LoRa node
It clearly states the hardware is for a node, not a gateway.
Given your earlier “join success” message there seems to be a gateway nearby. So you should see the join and and uplinks in the TTN console IF you registered the node in TTN, used the EUIs and Key listed during registration AND have the console data page open during transmission. (The console has no ‘memory’ of any earlier data exchanges,)
Now we’ve established you don’t have a gateway but that one is likely to be near enough to hear your device, next set of questions:
Did you register your device on the TTN console?
Which version of the console?
Can you see any in the Traffic / Live Data when you do a send on your device?
If you can give us a reasonably accurate indication of where you are, without giving us your address, we can show you where to look on the mapping tools for local gateways. We will need either a street or landmark within 100m of where you are.
You will do yourself a huge favour if you take a few minutes to read:
I am looking for an IoT node (Generic off the shelf) which can be connected to a control panel of a machine and send data/signals to any gateway via Lora Protocol.
Can you please help me by providing reputed company name.
Welcome to the Things Network Forum
We focus on TTN and the use of the LoRaWAN implementation. If you are looking to use LoRa only (RF phy solution with an associated proprietary or self generated protocol), then that is out of scope here. If you are looking to use LoRaWAN then your question is a bit ‘how long is a piece of string?’…we will need a lot more information to help you narrow your selections. What signals are you monitoring? Will you be doing any processing or analysis of those signals at the node - e.g. checking fluid levels or temperatures or positions etc. before then just sending an alarm or summaryy based on that analysis? What is your power source? Available $budget?, How often will the messages need to be sent etc… think hard on your requirements then come back when you something solid we can base any advice on. There are lots of folk on the Forum with a wide and varied level of experience who should be able to help you…
Have you researched LoRa/LoRaWAN and read associated documentation to determine the limits and use cases for the technology to see if it fits your needs? In addition, besides legal and technical constraints the use of the shared community resource that is TTN comes with additional limits and responsibilities - check the FUP (Fair Use Policy) - Forum search (top right) is a good place to start as is the thethings network and thethings industries documentation and guides
With recent site redesign think this is now the device repository, though I expect that is a subset where device profiles have been set up to assist registration process in TTS(CE) aka V3… haven’t check for a time…
Keep in mind that LoRaWan in general and The Things Network in particular is primarily geared towards low-bandwith measurement reporting. The capability for downlink control is very limited, in particular it’s not really possible to do so in a timely fashion.
To control industrial machinery, you’re really going to need to use some other technology.
The applicability of LoRaWan would be more to “nice to know” monitoring of autonomous, unattended setups, and maybe making desired but non-critical adjustments to the rules of a closed-loop control system. Eg, you wouldn’t send a command to open or close a valve, but you might ask a remote, autonomous feedback control system to switch between a more or less aggressive strategy for controlling the valve in response to its sensors.
I have the same problem of @symon .
I used a pi3 with Lora Node pHAT, it’s configured on TTN as application with the datas shows (DevEUI, etc…) by CLI.
If the join mode is OTAA, I can’t join at Lora Network (error 99), but if the join mode is ABP, I can join on the netowork, but on TTN I don’t show anything, why?
No …
because I thought that for trasmit datas on TTN I just need to use only a Lora Node, so I bought this LoraNode pHAT and following the getting started instruction, but I am new with LoraWAN Universe …
So, I need necessarily a Lora Gateway to trasmit on TTN?
Near to me there’s a gateway (but not the specific location, because it’s on of my university), but when I try to send a test message (from CLI) in ABP mode, the gateway received it, but on TTN console I don’t read nothing.
In OTAA mode the situation is worst, because my Lora Node don’t join on it and I don’t know why.
In ABP your node just sends and does not in any way know if the transmission has been received. It just reports the transmission is successful. Keep in mind LoRaWAN is not WiFi where the access point acknowledges receipt of data.
The join just initialized the module and did not send or receive any data either.
Given your the lack of data at TTN the most logical assumption is that the gateway does not receive your data.
Check the DevAddr and the keys, if those are right move closer to a known working gateway for testing. If possible contact the gateway owner and ask if they see your traffic in the life traffic on TTN.
