- Posts: 4402
Help Needed: Documenting models & protocols
- PhracturedBlue
-
Topic Author
- Offline
Less
More
29 Jan 2014 23:46 #19401
by PhracturedBlue
Help Needed: Documenting models & protocols was created by PhracturedBlue
I would like to create an article that contains a list of each protocol and a full list of models supported by it.
We should also list unsupported models/protocols
Obviously, I don't expect to list every single model/receiver.
I'm thinking something along the lines of:
Devo:
All Walkera Devo compatible helicopters (some examples)
RX701, RX801, RX802, RX1002, RX1201, RX1202
WK2801:
WK2601:
WK2401:
DSM2:
OrangeRx, Spektrum, Blade...
DSMX:
Spektrum, Blade...
etc, etc
I don't have the bandwidth (or knowledge) to create such a list.
The easiest for me is probably to create an article, and give someone (responsible) ownership of updating it. But I'd be open to a shared google-doc or something similar.
Mainly, I'd like something that can be made easily available from the main page, and which I don't personally need to maintain.
So there are 2 requests here:
1) Help fill in an initial list (can be done in this thread)
2) Find a volunteer (or 2 ) to help maintain it. On this I am unlikely to accept volunteers who haven't been around (and engaged) for a little while, but you are all welcome to help create the list and recommend additions to it.
We should also list unsupported models/protocols
Obviously, I don't expect to list every single model/receiver.
I'm thinking something along the lines of:
Devo:
All Walkera Devo compatible helicopters (some examples)
RX701, RX801, RX802, RX1002, RX1201, RX1202
WK2801:
WK2601:
WK2401:
DSM2:
OrangeRx, Spektrum, Blade...
DSMX:
Spektrum, Blade...
etc, etc
I don't have the bandwidth (or knowledge) to create such a list.
The easiest for me is probably to create an article, and give someone (responsible) ownership of updating it. But I'd be open to a shared google-doc or something similar.
Mainly, I'd like something that can be made easily available from the main page, and which I don't personally need to maintain.
So there are 2 requests here:
1) Help fill in an initial list (can be done in this thread)
2) Find a volunteer (or 2 ) to help maintain it. On this I am unlikely to accept volunteers who haven't been around (and engaged) for a little while, but you are all welcome to help create the list and recommend additions to it.
Please Log in or Create an account to join the conversation.
- oregonh20
-
- Offline
Less
More
- Posts: 7
30 Jan 2014 07:14 #19407
by oregonh20
Replied by oregonh20 on topic Help Needed: Documenting models & protocols
PB,
I'd be very interested in getting this rolling and maybe even maintain if you like... I'm actually starting on something like this for myself anyways in order to study the various RF protocol designs and implementations.
OH2
Steve
I'd be very interested in getting this rolling and maybe even maintain if you like... I'm actually starting on something like this for myself anyways in order to study the various RF protocol designs and implementations.
OH2
Steve
Please Log in or Create an account to join the conversation.
- victzh
-
- Offline
Less
More
- Posts: 1386
30 Jan 2014 07:34 - 30 Jan 2014 07:38 #19409
by victzh
Replied by victzh on topic Help Needed: Documenting models & protocols
As I most familiar with nRF24L01 based protocols, here is my compilation:
RF chip nRF24L01 (also nRF24L01+, Beken BK2421/BK2423, Si24R1)
HiSky (RCGroups info www.rcgroups.com/forums/showthread.php?t=1859830 )
Fixed pitch 4-channel
FBL70 (HFP80, V955)
FBL90 (HFP100, V944)
Collective pitch 6-channel
FBL80 (HCP80, V933)
FBL100 (HCP100, V922)
Micro Quad
FF120 (HMX120, Q-BOT micro)
WL-Toys V2x2 - Line of quads similar to V9x9, but with an accelerometer and nRF24L01 instead of A7105
V202 - micro quad
V252 - enhanced micro quad
V212 - mini quad
V222 - mini quad with camera
V262 - enhanced mini quad
Tactic SLT
All models with TX-R moniker (TX-Ready, www.tx-ready.com/ )
About 35 models including planes, helis, and quads
E.g., Axe 100 helis and 1SQ quads
Skyline
YD717
UDI
U816/U818 (work in progress)
ESky
ESky receivers (work in progress)
Bitcraze
Crazyflie (work in progress)
MJX
F45 V3 (work in progress)
RF chip nRF24L01 (also nRF24L01+, Beken BK2421/BK2423, Si24R1)
HiSky (RCGroups info www.rcgroups.com/forums/showthread.php?t=1859830 )
Fixed pitch 4-channel
FBL70 (HFP80, V955)
FBL90 (HFP100, V944)
Collective pitch 6-channel
FBL80 (HCP80, V933)
FBL100 (HCP100, V922)
Micro Quad
FF120 (HMX120, Q-BOT micro)
WL-Toys V2x2 - Line of quads similar to V9x9, but with an accelerometer and nRF24L01 instead of A7105
V202 - micro quad
V252 - enhanced micro quad
V212 - mini quad
V222 - mini quad with camera
V262 - enhanced mini quad
Tactic SLT
All models with TX-R moniker (TX-Ready, www.tx-ready.com/ )
About 35 models including planes, helis, and quads
E.g., Axe 100 helis and 1SQ quads
Skyline
YD717
UDI
U816/U818 (work in progress)
ESky
ESky receivers (work in progress)
Bitcraze
Crazyflie (work in progress)
MJX
F45 V3 (work in progress)
Last edit: 30 Jan 2014 07:38 by victzh. Reason: Formatting
Please Log in or Create an account to join the conversation.
- victzh
-
- Offline
Less
More
- Posts: 1386
30 Jan 2014 07:36 #19410
by victzh
Replied by victzh on topic Help Needed: Documenting models & protocols
And definitely the forum ate my (pretty lame, admittedly) formatting. May be it would be easier if you put some document to bitbucket for joint editing?
Please Log in or Create an account to join the conversation.
- SeByDocKy
-
- Offline
Less
More
- Posts: 1016
30 Jan 2014 07:53 #19411
by SeByDocKy
You can add using V2x2 protocols the JD JXD 385 and JD JXD 388 and some other X4 clones
Replied by SeByDocKy on topic Help Needed: Documenting models & protocols
victzh wrote: As I most familiar with nRF24L01 based protocols, here is my compilation:
RF chip nRF24L01 (also nRF24L01+, Beken BK2421/BK2423, Si24R1)
HiSky (RCGroups info www.rcgroups.com/forums/showthread.php?t=1859830 )
Fixed pitch 4-channel
FBL70 (HFP80, V955)
FBL90 (HFP100, V944)
Collective pitch 6-channel
FBL80 (HCP80, V933)
FBL100 (HCP100, V922)
Micro Quad
FF120 (HMX120, Q-BOT micro)
WL-Toys V2x2 - Line of quads similar to V9x9, but with an accelerometer and nRF24L01 instead of A7105
V202 - micro quad
V252 - enhanced micro quad
V212 - mini quad
V222 - mini quad with camera
V262 - enhanced mini quad
Tactic SLT
All models with TX-R moniker (TX-Ready, www.tx-ready.com/ )
About 35 models including planes, helis, and quads
E.g., Axe 100 helis and 1SQ quads
Skyline
YD717
UDI
U816/U818 (work in progress)
ESky
ESky receivers (work in progress)
Bitcraze
Crazyflie (work in progress)
MJX
F45 V3 (work in progress)
You can add using V2x2 protocols the JD JXD 385 and JD JXD 388 and some other X4 clones
Please Log in or Create an account to join the conversation.
- victzh
-
- Offline
Less
More
- Posts: 1386
30 Jan 2014 17:15 #19432
by victzh
Replied by victzh on topic Help Needed: Documenting models & protocols
Just get this document, add them and republish here - I don't know about JD and X4 clones. Do you mean Hubsan X4 clones, BTW? Aren't they using A7105 based protocol?
Please Log in or Create an account to join the conversation.
- SeByDocKy
-
- Offline
Less
More
- Posts: 1016
30 Jan 2014 19:26 #19434
by SeByDocKy
Victzh,
No both JXD are using the nRF24L01+ via the V2x2 protocol
Replied by SeByDocKy on topic Help Needed: Documenting models & protocols
victzh wrote: Just get this document, add them and republish here - I don't know about JD and X4 clones. Do you mean Hubsan X4 clones, BTW? Aren't they using A7105 based protocol?
Victzh,
No both JXD are using the nRF24L01+ via the V2x2 protocol
Please Log in or Create an account to join the conversation.
- VTdev
-
- Offline
Less
More
- Posts: 63
30 Jan 2014 19:56 - 30 Jan 2014 20:02 #19437
by VTdev
Replied by VTdev on topic Help Needed: Documenting models & protocols
DSM2/DSMX:
Here's a list of over 70 "bind and fly" products (meaning DSM compatible)
www.bindnfly.com/CompatibleProducts/
I'm not sure how fine a degree you need, but this can either be further categorized or expanded, depending on the need. For instance, the Vapor is a series. Anyway it's a start.
Here's a list of over 70 "bind and fly" products (meaning DSM compatible)
www.bindnfly.com/CompatibleProducts/
I'm not sure how fine a degree you need, but this can either be further categorized or expanded, depending on the need. For instance, the Vapor is a series. Anyway it's a start.
Last edit: 30 Jan 2014 20:02 by VTdev.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
-
- Offline
Less
More
- Posts: 4402
30 Jan 2014 20:05 #19438
by PhracturedBlue
Replied by PhracturedBlue on topic Help Needed: Documenting models & protocols
I put victzh's info here:
www.deviationtx.com/articles/29-supported-models-receivers
I don't want to use mercurial for this, as (a) it is more difficult to make visible from the website, and (b) I'd need to maintain it as far as merges, pull-requests, etc, which I'm hoping not to.
www.deviationtx.com/articles/29-supported-models-receivers
I don't want to use mercurial for this, as (a) it is more difficult to make visible from the website, and (b) I'd need to maintain it as far as merges, pull-requests, etc, which I'm hoping not to.
Please Log in or Create an account to join the conversation.
- oregonh20
-
- Offline
Less
More
- Posts: 7
30 Jan 2014 22:09 - 30 Jan 2014 22:19 #19440
by oregonh20
Replied by oregonh20 on topic Help Needed: Documenting models & protocols
This post possibly redundant?
Just saw PBs post.
PB, How should I proceed, if at all?
Obviously the focus would be on the Deviation communities needs primarily, but personally I also see a need for an organized and cross checked reference document, not just for the Deviation community, but for the RC groups needs at large. There seems to be a lot of misinformation out there.
If everyone is OK with it, I'll start getting this recorded in a basic google doc and we can transfer it to one owned by Deviation when we get one made. Yes/no/thoughts?
I can shoot for a format and let you guys add or pair as you see fit?
Againt thoughts or recomendations?
OH2
Just saw PBs post.
PB, How should I proceed, if at all?
Obviously the focus would be on the Deviation communities needs primarily, but personally I also see a need for an organized and cross checked reference document, not just for the Deviation community, but for the RC groups needs at large. There seems to be a lot of misinformation out there.
If everyone is OK with it, I'll start getting this recorded in a basic google doc and we can transfer it to one owned by Deviation when we get one made. Yes/no/thoughts?
I can shoot for a format and let you guys add or pair as you see fit?
Againt thoughts or recomendations?
OH2
Last edit: 30 Jan 2014 22:19 by oregonh20.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
-
- Offline
Less
More
- Posts: 4402
30 Jan 2014 22:18 #19441
by PhracturedBlue
Replied by PhracturedBlue on topic Help Needed: Documenting models & protocols
Honestly, I don't care. I want it to be readable and linked to the front page (which I haven't done yet for the article). A googleDoc is probably fine, and would allow multiple users to edit it easily.
Please Log in or Create an account to join the conversation.
Time to create page: 0.073 seconds
-
Home
-
Forum
-
General
-
General Discussions
- Help Needed: Documenting models & protocols