-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sx126x support has any hope? #301
Comments
I'm happy to look at the reference code, but I don't have test hardware, or know of a suitable source yet.... |
@cstratton found the datasheet for me, thanks. It's not a big project to add support. Steps are:
I don't think any changes are needed in lmic*.c for this. It's all radio.c -> radio_sx127x.c and radio_sx126x.c. I imagine some HAL changes are needed; possibly the whole pinmapping structure has to change because it's 127x-ish. Next step is to figure out how to find the time (and the suitable reference platform)... |
Hi! Sorry for the late reply! Here is the link: Edit: oh i see you found it...well that seems others are interested as well ;) |
Hi! Is there any progress in the support of the 126x chipset? |
Nope, I don't have hardware, and I don't have budget... So unless we can get someone to offer MCCI support to do this, or someone else wants to do the work, it won't happen for a while. Sorry. Best regards, |
Hm, i think maybe we can sort this out. If i buy you two 1262 chip and send
to your address it could work?
Terry Moore <notifications@github.com> ezt írta (időpont: 2019. máj. 8.,
Sze 20:09):
… Nope, I don't have hardware, and I don't have budget... So unless we can
get someone to offer MCCI support to do this, or someone else wants to do
the work, it won't happen for a while. Sorry.
Best regards,
--Terry
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#301 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGKX7SMCQRUMPQAOR44BO23PUMJOLANCNFSM4HEDZWRQ>
.
|
Chips aren't sufficient, alas, we need working systems (CPU + chip + RF, etc.). There's also the issue of funding the engineering work and ongoing support. The cost is likely to be out of reach for an individual, but reasonable for a company. It could be crowd-sourced, I suppose, but I don't have the time to administer that kind of thing; and we spent my pro-bono budget for the year already on pi64.win. Drop me an email at tmm@mcci.com and we can discuss further if you're interested. |
Hi, |
@slavendam: Technically very possible. No funding. No notifications from MCCI's suppliers about the SX1276, which is what we use. As said above:
I can easily use the Heltec modules for reference. But without a business case to do this, my time is not available. I had no response to the quoted comment previously, so I assume that there is no commercial interest in this. MCCI can't fund it, and I can't fund this myself; the pandemic era has been challenging. Sorry to disappoint. If someone wants to volunteer to run a fundraising drive (via The Things Network NY, which is a non-profit), then it could be crowd sourced. But I don't have the time to run a crowdsourcing program. |
Hi! Is it possible that there will be support for the SX126x(especially 1262) chip? There is example for ping-pong comm between these chips but it would be quite difficult to implement lorawan into it for me to say the least...The example codes are quite hidden but i can share the links if someone would take a look at it.
The text was updated successfully, but these errors were encountered: