Shop our Airplanes Products Drone Products Sales
Thread Tools
Dec 17, 2017, 10:13 PM
Quietly Scheming!!!
geekness's Avatar
github

https://github.com/olliw42/storm32bgc

Quote:
Originally Posted by davidbitton
where are the Eagle files and BOM?
Sign up now
to remove ads between posts
Dec 17, 2017, 10:37 PM
Wisconsin
Quote:
Originally Posted by geekness
When using the motors with inbuilt encoders (GBM5208H-200T), where do the wires from the encoders get hooked up to?
Do they need to go all the way back to the controller, or just back to the V2.5E motor module?
They solder onto the driver/encoder board. The nature of the NT system is the serial connection.
Dec 17, 2017, 10:45 PM
Wisconsin
If you are interested in being informed about the 3.3 group buy please respond to post 524 so I don't have to scan through the thread and miss someone.
Dec 17, 2017, 11:12 PM
Quietly Scheming!!!
geekness's Avatar
STorM32 v3.3m order list for mike_kelly (please copy and add):
Geekness, 3x (controller+motor modules+imu kits), Australia
OlliW, 1x, Germany
Mike Kelly 3x, US


Quote:
Originally Posted by geekness
Im interested in the group purchase of the V3.3 Controller.
Will also be interested in purchasing 3 motor boards too.
I assume the IMU is the one available on the ensys website? Or do we have to buy a full Storm32 NT kit?
--------------------------------------------------------
STorM32 v3.3m order list for mike_kelly (please copy and add):
Geekness, 2x, Australia
OlliW, 1x, Germany
Mike Kelly 3x, US
Dec 18, 2017, 01:58 AM
OlliW
@geekness:
you'll find renderings of the V2.5 round and square boards in this thread
for your convenience attached again

the precise dimensions you can read off from the Eagle .brd files
the diameter of the round is ca 29 mm
the square is ca 20 x 33 mm (not including the wings)

as mentioned repeatedly, when an external AS5048A encoder is to be used, the bottom side of the PCBs should not be populated
on the top side you can see this array of 6 rectangular solder pads in the "middle" of the board, that's where the wires to the encoder are soldered to
the square version is probably somewhat more useful for this configuration
Last edited by OlliW; Dec 18, 2017 at 02:06 AM.
Dec 18, 2017, 06:32 AM
Quietly Scheming!!!
geekness's Avatar
@OlliW thanks. Great information.

Do you know off by hand what the mounting hole centers are for each? I don't have eagle to open the design files.

Also, can you please confirm we don't connect pwm from the motors inbuilt encoder board to the T-STorM32 module. We only connect the SPI pins (vcc, gnd, miso, mosi, scl, scs).

Are these a direct connection, ie. miso-miso, mosi-mosi etc?


Quote:
Originally Posted by OlliW
@geekness:
you'll find renderings of the V2.5 round and square boards in this thread
for your convenience attached again

the precise dimensions you can read off from the Eagle .brd files
the diameter of the round is ca 29 mm
the square is ca 20 x 33 mm (not including the wings)

as mentioned repeatedly, when an external AS5048A encoder is to be used, the bottom side of the PCBs should not be populated
on the top side you can see this array of 6 rectangular solder pads in the "middle" of the board, that's where the wires to the encoder are soldered to
the square version is probably somewhat more useful for this configuration
Dec 18, 2017, 06:55 AM
OlliW
Quote:
Originally Posted by geekness
Do you know off by hand what the mounting hole centers are for each?
this I mentioned somewhere up to Mike
I think the minimum circle is 25mm, for M2 screws

Quote:
Originally Posted by geekness
Also, can you please confirm we don't connect pwm from the motors inbuilt encoder board to the T-STorM32 module. We only connect the SPI pins (vcc, gnd, miso, mosi, scl, scs).
yes, must be spi, not pwm, only spi is supported

Quote:
Originally Posted by geekness
Are these a direct connection, ie. miso-miso, mosi-mosi etc?
they follow the rules for spi
miso-mosi, mosi-miso, cs-cs, clk-clk
Dec 18, 2017, 10:28 AM
Quietly Scheming!!!
geekness's Avatar
Thanks again OlliW
Dec 20, 2017, 05:50 PM
Wisconsin
I could use a check-over. I had to guess on a number of items.
The NT logger I can't find enough to build a BOM.
The IMU I need the IC's and packages.
Dec 20, 2017, 10:59 PM
OlliW
see attached

I've also changed the 100nF to a cheaper version

the 33uF capacitor is a bit the weak thing, since rated only for 20V, so suitable only for 4S
some might want to see 6S, but I think for a first this should be perfectly fine

I've also briefly looked at the imu BOM, I think this is just copy&place from the other BOMs

good job, sir
and many thx for doing this
Dec 20, 2017, 11:56 PM
Wisconsin
Quote:
Originally Posted by OlliW
see attached

I've also changed the 100nF to a cheaper version

the 33uF capacitor is a bit the weak thing, since rated only for 20V, so suitable only for 4S

some might want to see 6S, but I think for a first this should be perfectly fine

I've also briefly looked at the imu BOM, I think this is just copy&place from the other BOMs

good job, sir
and many thx for doing this
If the 33u cap is the only thing stopping from being used on 6s then maybe we should do it right the first time?
TAJD336K035RNJ https://www.digikey.com/product-deta...35-1-ND/564767
But it is a SMC_D code?

Well somethings just need a BEC.
Did I get the right version of the encoder? IS C1 and SMC_C size? The Murata Resonator is package 3_SMD?

Thanks
Dec 21, 2017, 03:24 AM
OlliW
I have never tested 6S myself, but, yes, I believe it is just the this C
it must be SMC_C.
I know for a while that it is not easy to find in larger than 20V

yes, I checked the encoder
yes, C1 is SMC_C
well, the murata is the very same as for the v3.3m board, copy it over (I guess this NLP or whatever it was thing)
Dec 23, 2017, 08:28 AM
OlliW
look what has arrived me today:

I ordered v3.3m and v2.5E-sq boards from ShenZhen2U, to check their abilities and PCB quality. Some things to note:

funny:
* I've order 10 of each, and got 13 v3.3m and 17 v2.5-sq

good:
* the pcbs are cut out very precisely
* from visual inspection, the copper layers, stop layers, vias, pads, etc. look good

not so good:
* they were delivered just now, while I've ordered them the 25.11 and 29.11, respectively. They promised ca 7 days manufacturing (which they kept) and 7-9 days shipping (which they significantly failed)
* the print-on are of very low quality, and partially significantly misplaced. It's a while ago I have seen that poor printons. That's a bit disappointing, and for production layouts one probably should "simplify" them

since I obviously have not yet populated them, and likely won't in the next days (LOL), I can't comment on whether they actually work or not

I guess I do like the X wing shape, it's functional, and they fit well to e.g. the iFlight 2808, in both the encoder-on-pcb and the encoder in motor-housing configurations

EDIT: maybe one should ask for quotes from smart prototyping? I have quite good experience with their pcbs, and they too offer assembly
EDIT2: nah ... their ordering procedure looks complicated, and costly
Last edited by OlliW; Dec 23, 2017 at 02:24 PM.
Dec 23, 2017, 07:50 PM
Wisconsin
Not sure I guessed right on the IMU. It is not a cut and paste job because the Gimbal controller has 604 sized resisters for instance and the Motor controller has 603. What fits the IMU brd?
Dec 23, 2017, 11:37 PM
OlliW
there aren't any 604, only 603, if you read 604 it would be a missprint and should be 603

Dec 23, 2017, 11:56 PM
Wisconsin
Quote:
Originally Posted by OlliW
there aren't any 604, only 603, if you read 604 it would be a missprint and should be 603

Sorry I meant R0402 but the gimbal board I have using 402 and the Motor brd I have 603. So I used 603 for the IMU but then noticed the two boards are different.
Dec 24, 2017, 05:16 AM
OlliW
I'm not sure what "different" is supposed to mean, but to the best of my knowledge the v2.5E and NT imu use exactly the same parts, the NT imu is also 603
so you got a response from SZ2U, and they are somehow complaining with your 603 choice?
Dec 24, 2017, 09:30 AM
Wisconsin
Quote:
Originally Posted by OlliW
I'm not sure what "different" is supposed to mean, but to the best of my knowledge the v2.5E and NT imu use exactly the same parts, the NT imu is also 603
so you got a response from SZ2U, and they are somehow complaining with your 603 choice?
I went with your original NT 3.3 bom and it specifies resistors with a R0604 package while the BOM for the NT motor module specifies 603 packages for the resistors. So unless those two designations are really two names for the same package size there is something wrong. I just noticed in comparing the two spreadsheets. I don't want to send a correction to ShenZhen more than once.
Dec 24, 2017, 09:57 AM
OlliW
do not go with the BOM for the v3.3, forget about the v3.3 BOM
the thing I'm trying to say is that you should use the BOM of the v2.5E board, pick the R from there, and copy into the BOM for the NT imu
this is so becasue they both use the 603 pacaage size
Dec 24, 2017, 10:09 AM
Wisconsin
Quote:
Originally Posted by OlliW
do not go with the BOM for the v3.3, forget about the v3.3 BOM
the thing I'm trying to say is that you should use the BOM of the v2.5E board, pick the R from there, and copy into the BOM for the NT imu
this is so becasue they both use the 603 pacaage size
OK I did. So all ok.
Dec 24, 2017, 10:33 AM
Wisconsin
I looked at it again and I still think there might be one thing wrong C2 looks on the pcb to be a bigger size than C603?
Is the IC2 and IC3 right?
Dec 24, 2017, 09:58 PM
UAV Engineer, elab.co,jp
Hello all, specially Olliw,
Let me introduce myself, I'm Ali, UAV engineer based in Japan, working for www.elab.cp.jp. Where do I start ?
I have been following this thread for so long, I recently decided to jump in after getting approval from my boss and I liked the capabilities of the T-storm32. We custom make our drones in Japan, we are big promoter of DIY and open-source projects. We have many partners around the world ( China for custom made gimbal motors, and Japan for custom made pcb board) not so much interested in wholesale manufacturing nor advertisement If by any means you guys feel like I hijacked this post please let me know of it. That being said, my plan is to build a working kit and (standardized?) version of the T-storm32, since I noticed for example that the pcb boards are rare, write a guide about it and share it publicly, I can also make them and offer them for the general public (like ensys.lt) later too for those who are not technical.
Anyway, Some of my concerns are:
  • I come from an aerospace engineering background, I will really need some help from this community to assist me a bit the electronic parts. This whole T-storm started because I'm a hobbyist photographer who wanted to build his own camera gimbal...
  • If I understand correctly, the nt motor encoders do not come with AS5048 modules, so I first need these, mount them in the back of the gimbal motor, then connect them externally with the nt motor encoder
  • If so, I will send the encoder board schematics right away to make them (the motor v25E one). for the back of the gimbal motor, I will take care of it since I do CAD design here, I already looked for the rings magnet. Does anyone know where I find the same eagle file for the as5048a chips on a pcb board?
  • If I'm using the storm32 v1.3, does it mean I don't need the nt motor encoder module ?
  • May be a stupid question but why not incorporate the AS5048a inside those motor encoders ? my guess is space limitation ?

Thanks a lot everyone who is willing to help, PLEASE ask me any question if you have any...
Ali
Last edited by diamondx; Dec 25, 2017 at 02:55 AM.
Dec 25, 2017, 04:23 PM
Mari
Quote:
Originally Posted by OlliW
I hng)
Hi partners. I usually post at another thread but now my questions are about this specific thread. I hope somebody could help me.

I have a problem with my storm32 3D gimbal, it is a hakrc gimbal. The camera imu does not work now. It had been working for 2 years but the last weekend it died (rip, lol).

Now, I need a new camera imu and I have to buy one. I know that the piece is a mpu6050 and I do not know if a need an ordinary " mpu6050" or a specific "NT mpu6050".

I have been looking it for at www.olliw.eu and www.ensys.it and I do not find the specific nt mpu6050.

The questions are:

1.- Could my gimbal work with an ordinary mpu6050 (without being a NT mpu)? or I need a NT mpu as a camera imu?

2.- Where I can buy a NT mpu6050? Are they cheap?

Merry Christmas.

Thanks in advance.
Dec 26, 2017, 04:24 AM
OlliW
Quote:
Originally Posted by mike_kelly
I looked at it again and I still think there might be one thing wrong C2 looks on the pcb to be a bigger size than C603? Is the IC2 and IC3 right?
If IC2, IC3 were taken from the BOM of v2.5E, then they are correct
as regards the C's and R's, I'm totally confused now, maybe my memory has fooled me and I have given you quite misleading info, and it was good you had been so insisting
C2 indeed looks larger than the others in the top.png, so it could be either that they all 0603 and C2 is 0804, or they all are 0402 and C2 is 0603 ... I'm confused
sadly I currently can't check
I should be able to do so tomorrow evening, I'll tell then
sorry sir
Dec 26, 2017, 04:45 AM
OlliW
@diamondx:
welcome, sir
I see that you are a partner of ArduPilot, that's great, hopefully you consider renewing it

as regards electronics & hardware, I guess any help is highly appreciated, that's the biggest stumble stone, that those who might be interested in TSTorM32 can't get the hardware

you might have seen that mike_kelly is very actively working on getting the BOMs together in order to place an pcb assembly order with ShenZhen2U. If you think you could offer a better and/or cheaper alternative, it would be much appreciated if you could get into contact with him ASAP

Quote:
Originally Posted by diamondx
* I come from an aerospace engineering background, I will really need some help from this community to assist me a bit the electronic parts. This whole T-storm started because I'm a hobbyist photographer who wanted to build his own camera gimbal...
I guess many here will be willing to help you, including me. However, since it's by volunteers (including me), it is also kind of expected that you teach yourself a bit, e.g., the wiki should not be unfamiliar
(the wiki is maybe not the best structured one in the world, but it contains a lot of info)
also the thread might be checked
Quote:
Originally Posted by diamondx
* If I'm using the storm32 v1.3, does it mean I don't need the nt motor encoder module ?
for TSTorM32 you ALWAYS need three NT motor encoder modules. ALWAYS means ALWAYS

Quote:
Originally Posted by diamondx
* If I understand correctly, the nt motor encoders do not come with AS5048 modules, so I first need these, mount them in the back of the gimbal motor, then connect them externally with the nt motor encoder
there are two configurations:
(i) TL5012B encoder on the nt motor encoder module
(ii) AS5048A encoder connected per SPI to a v2.5E nt motor encoder module

Quote:
Originally Posted by diamondx
* Does anyone know where I find the same eagle file for the as5048a chips on a pcb board
there is no NT motor encoder module with AS5048A on the pcb, see previous answer, so no eagle files
the TLE5012B encoder is preferred over the AS5048A, so, if you want an encoder on the pcb then use the option (i) of the previous answer

Quote:
Originally Posted by diamondx
* May be a stupid question but why not incorporate the AS5048a inside those motor encoders ?
the TLE5012B encoder is preferred over the AS5048A, so, if you want an encoder on the pcb then use the option (i) of the answer before the previous answer
Dec 26, 2017, 08:58 AM
Registered User
STorM32 v3.3m order list for mike_kelly (please copy and add):
Geekness, 3x (controller+motor modules+imu kits), Australia
OlliW, 1x, Germany
Mike Kelly 3x, US
noradtux, 2x controller, 6x motor modules, Germany
Quote:
Originally Posted by geekness
STorM32 v3.3m order list for mike_kelly (please copy and add):
Geekness, 3x (controller+motor modules+imu kits), Australia
OlliW, 1x, Germany
Mike Kelly 3x, US
Dec 26, 2017, 09:05 AM
Registered User
Quote:
Originally Posted by noradtux
STorM32 v3.3m order list for mike_kelly (please copy and add):
Geekness, 3x (controller+motor modules+imu kits), Australia
OlliW, 1x, Germany
Mike Kelly 3x, US
noradtux, 2x controller, 6x motor modules, Germany
also still in for one, I can go three if that would help
Dec 26, 2017, 12:45 PM
Wisconsin
Quote:
Originally Posted by OlliW
If IC2, IC3 were taken from the BOM of v2.5E, then they are correct
as regards the C's and R's, I'm totally confused now, maybe my memory has fooled me and I have given you quite misleading info, and it was good you had been so insisting
C2 indeed looks larger than the others in the top.png, so it could be either that they all 0603 and C2 is 0804, or they all are 0402 and C2 is 0603 ... I'm confused
sadly I currently can't check
I should be able to do so tomorrow evening, I'll tell then
sorry sir
No problem. I just don't want to be the cause of a mistake. Tobe came back and said he can't read the .brd file for the Motor Module. What good is Git if you can't download a file without it being messed up. I responded to use the file you uploaded but he has not responded yet.
Dec 26, 2017, 12:51 PM
Wisconsin
Quote:
Originally Posted by pyratedivet
also still in for one, I can go three if that would help
Ok friends and neighbors boys and girls. First pass it looks like a complete set of gimbal controller brd, 3 motor modules and an IMU is going to less than $125. A few bucks more for encoders. If you are still interested please send me a pm with your city and zip.
Postal agreements are strange these days and I want to make sure there are no big surprises with postage.
Dec 26, 2017, 12:58 PM
Registered User
Quote:
Originally Posted by mike_kelly
Ok friends and neighbors boys and girls. First pass it looks like a complete set of gimbal controller brd, 3 motor modules and an IMU is going to less than $125. A few bucks more for encoders. If you are still interested please send me a pm with your city and zip.
Postal agreements are strange these days and I want to make sure there are no big surprises with postage.
Encoders are one of the main components no?
Still in but need to know what the final working set will cost
Dec 26, 2017, 04:01 PM
Wisconsin
Quote:
Originally Posted by pyratedivet
Encoders are one of the main components no?
Still in but need to know what the final working set will cost
Certainly encoders are the thrust of T-STorM32 but there are two ways to go.

One you can buy the encoder as part of the motor brd on our buy. But then you are required to find the right magnets and glue them to the motor shaft and figure out how to mount the encoder/driver brd so as to work with your gimbal arms. That is a non-starter for me.

Second is to buy motors that already have the right encoders installed, which is not a wide range mostly iFLight, and then use the Motor brds we are making without the encoder parts. The same brd has the motor drivers on one side and the encoder on the other side. Don't need encoders then you don't populate the encoder side.
Dec 26, 2017, 08:05 PM
Registered User
What is going to be the best way to get an sbus signal and 12v to the camera? Using more wires on the sliprings or specialised imu board?

How about a video feed back will an analog signal get too much interference. Is a hdmi feed possible somehow.

My end goal is to control a black magic micro cinema camera via sbus which can run on its own battery and power a vtx if needed but im trying to cut down on all the wiring on the gimbal as are most in this thread i imagine.
Dec 26, 2017, 09:18 PM
Wisconsin
Quote:
Originally Posted by l2smith2
What is going to be the best way to get an sbus signal and 12v to the camera? Using more wires on the sliprings or specialised imu board?

How about a video feed back will an analog signal get too much interference. Is a hdmi feed possible somehow.

My end goal is to control a black magic micro cinema camera via sbus which can run on its own battery and power a vtx if needed but im trying to cut down on all the wiring on the gimbal as are most in this thread i imagine.
The problem to keep in mind is that the slipring wires are very small, can't handle much current. You save some with the serial NT bus because you only need one set of signal and power. HDMI has a lot of wires. It would be worth looking into STorM to control the camera instead of S.bus because you will once again save wires.
Dec 26, 2017, 10:31 PM
Registered User
Quote:
Originally Posted by mike_kelly
The problem to keep in mind is that the slipring wires are very small, can't handle much current. You save some with the serial NT bus because you only need one set of signal and power. HDMI has a lot of wires. It would be worth looking into STorM to control the camera instead of S.bus because you will once again save wires.
The camera accepts sbus, pwm and lanc control. If there was some way or forwarding any of the needed signals from input into the storm control board out to the camera that would be ideal. I currently have a y lead for the sbus signal to control a storm32 and camera from one rx unit.
Dec 27, 2017, 02:35 AM
OlliW
Quote:
Originally Posted by pyratedivet
Encoders are one of the main components no?
Still in but need to know what the final working set will cost
we can't answer that
as explained repeatedly, you can choose the option to have the encoders on the NT motor encoder module, or you can choose to have them externally e.g. build into the motors
in the latter case you would buy the motors with builtin encoders yourself, and the cost of course depends on your choice of motors
there are not many types available: iFlight, Dualsky, so you might be able to estimate yourself
Dec 27, 2017, 10:50 AM
OlliW
@mike:
attached the BOM for the NT imu v2.11
two things:
* I forgot that for the v2.1 NT Imu I also moved to small, i.e. 0402 sized, parts. My recommendation should thus have been to take them from the v3.3 BOM, and not the v2.5E BOM. Sorry for the confusion. Good that you had been that insisting.
* for C1 I took a 0805 layout, but solder a 1206 = SMC_A sized capacitor on it. Manually this works very well. I guess you have to ask ZS2U if that is ok for them too.
Dec 27, 2017, 11:03 AM
Wisconsin
Quote:
Originally Posted by OlliW
@mike:
attached the BOM for the NT imu v2.11
two things:
* I forgot that for the v2.1 NT Imu I also moved to small, i.e. 0402 sized, parts. My recommendation should thus have been to take them from the v3.3 BOM, and not the v2.5E BOM. Sorry for the confusion. Good that you had been that insisting.
* for C1 I took a 0805 layout, but solder a 1206 = SMC_A sized capacitor on it. Manually this works very well. I guess you have to ask ZS2U if that is ok for them too.
Great I'll get that corrected and see if they can read the .brd files for both the Motor Modules and IMU.
Dec 27, 2017, 03:00 PM
OlliW
I've uploaded the "new" versions NT imu v2.11 and NT motor encoder v2.51E to the github repository

the changes are non functional, only improved parts identification, and some printon changed
Dec 27, 2017, 03:32 PM
OlliW
since this topic of the two supported configurations for the NT motor-encoder module and motor seems to cause so many headaches and confusions, I've created a drawing, which hopefully settles it once and for all:



For reference I here also collect statements made in previous posts (without proper reference, sorry):

T-STorM32 always need NT motor modules, the only freedom to choose is if the encoder should be also on the motor module, or separate and connected through wires with the motor module. If you want to "piggy pack" you need the encoders on the motor module

there are two configurations:

(i) TL5012B encoder on the nt motor encoder module

One you can buy the encoder as part of the motor brd on our buy. But then you are required to find the right magnets and glue them to the motor shaft and figure out how to mount the encoder/driver brd so as to work with your gimbal arms.

(ii) AS5048A encoder connected per SPI to a v2.5E nt motor encoder module

Second is to buy motors that already have the right encoders installed, which is not a wide range mostly iFLight, and then use the Motor brds we are making without the encoder parts. The same brd has the motor drivers on one side and the encoder on the other side. Don't need encoders then you don't populate the encoder side.

yes, must be spi, not pwm, only spi is supported
miso-mosi, mosi-miso, cs-cs, clk-clk

when an external AS5048A encoder is to be used, the bottom side of the PCBs should not be populated

on the top side you can see this array of 6 rectangular solder pads in the "middle" of the board, that's where the wires to the encoder are soldered to
the square version is probably somewhat more useful for this configuration
Last edited by OlliW; Dec 27, 2017 at 04:26 PM.
Dec 27, 2017, 11:02 PM
UAV Engineer, elab.co,jp
Quote:
I see that you are a partner of ArduPilot, that's great, hopefully you consider renewing it
The bonds are stronger years after years, one of the lead developer (Randy) actually live in japan, he comes to visit on Fridays.

Quote:
there are two configurations:
(i) TL5012B encoder on the nt motor encoder module
(ii) AS5048A encoder connected per SPI to a v2.5E nt motor encoder module
Thanks, that's one information I was missing, I didn't know TL5012 were implemented.

I have sent the schematics and brd files to one of the electric engineers. He will proceed making them. I will keep everybody updated on this !

Thanks everyone !

Diamondx (Ali )
Dec 27, 2017, 11:34 PM
Wisconsin
An additional note is that the comments on the driver/encoder boards actually now apply to the 3.3 gimbal controller board if used with NT or T-STorM32 because both use external driver modules. So with the 3.3v brd, which can be used for NT or T-STorM32, the new motor driver/encoder modules and the new IMU will be compatible with both.
Dec 29, 2017, 09:09 AM
OlliW

STorM32Link


a sneak preview into my lab:

STorM32Link: first demo of horizon drift compensation in high-g maneuvers

only for T-STorM32 !!!

My first attempts doing this actually date back 2 years or so. Things were working ... solala. For the cheap, badly build DIY gimbals many of use I found that the motor cogging is a really serious problem, as well as that the gimbals are rarely really square (which would enforce serious calibration). This is one of the untold stories for why even I eventually went with encoders. Anyway, T-STorM32 is existing for a long while now, and encoders enable achieving reasonable results now. I doubt I will spend time on trying to make this working/available also for the conventional STorM32. So, the bottom line:

Among others, this is a real advantage of T-STorM32 over the conventional STorM32 !

Currently it requires a DJI Naza V2, and a v3.3 STorM32 board, since it's making use of the DJI CAN bus. However, clearly, this hopefully will change in near future. I would be especially eager to also get it working with DJI N3's, and eventually ArduPilot.

I guess it would be cool to see this in effect also on planes.

Many thanks go to
* pavelsky, for his great job at re-engineering the DJI CAN bus protocol, and useful conversation
* meanwhile, for borrowing me a DJI Naza V2, without which all this would not be possible

T-STorM32: STorM32Link Horizon Drift Compensation, first demo (3 min 23 sec)
Last edited by OlliW; Dec 29, 2017 at 09:24 AM.
Dec 29, 2017, 03:47 PM
Registered User
Has the dji can bus changed with the newer gimbals for the inspire/osmo.
Dec 29, 2017, 04:44 PM
OlliW
this is a question, right?
I don't know. There appears to be zero info on the web. I figured that the N3 would be of more interest than the Inspire, I mean, it doesn't make sense to put a cheapo DIY gimbal on an Inspire, IMHO. Sadly, the protocol for the N3 seems not to be available either, but one could hope it's not too different from Naza and A2.
Dec 30, 2017, 11:06 AM
Quietly Scheming!!!
geekness's Avatar
Quote:
Originally Posted by l2smith2
What is going to be the best way to get an sbus signal and 12v to the camera? Using more wires on the sliprings or specialised imu board?

How about a video feed back will an analog signal get too much interference. Is a hdmi feed possible somehow.

My end goal is to control a black magic micro cinema camera via sbus which can run on its own battery and power a vtx if needed but im trying to cut down on all the wiring on the gimbal as are most in this thread i imagine.

HDMI requires 19 wires. The T-STorM32 requires 5 (from memory). I'm not sure what motor you're planning on using, but it would likely take a 12.7mm slip ring. The most wires I've found work that size slip ring is 18 wires.

In regards to sbus, you'll be able to send an sbus signal down the slipring wires, it should only take up a single wire.
Jan 01, 2018, 06:31 PM
Registered User
Quote:
Originally Posted by OlliW
this is a question, right?
I don't know. There appears to be zero info on the web. I figured that the N3 would be of more interest than the Inspire, I mean, it doesn't make sense to put a cheapo DIY gimbal on an Inspire, IMHO. Sadly, the protocol for the N3 seems not to be available either, but one could hope it's not too different from Naza and A2.
I picked up a cheap inspire for parts and i think i can get it up and running again with just some escs. (Went for a fresh water swim briefly)
Im not afraid to tinker with it to get a 3rd party gimbal working. Ill probably end up converting it to a pixhawk FC since it probably cant be trusted anymore. Also sick of dji go app updates grounding my undamaged inspire.
Jan 02, 2018, 03:10 PM
Registered User
Quote:
Originally Posted by geekness
HDMI requires 19 wires. The T-STorM32 requires 5 (from memory). I'm not sure what motor you're planning on using, but it would likely take a 12.7mm slip ring. The most wires I've found work that size slip ring is 18 wires.

In regards to sbus, you'll be able to send an sbus signal down the slipring wires, it should only take up a single wire.
A full HDMI cable is 19 wires, but their number can be reduced ...
Pin 14 - not used.
PIn 2,5,8,11 - Data Ground, on a short cable can be combined into 1 wire.
Pin 17- Ground, can be connected to ground Storm32.
Pin 18 - + 5v power, you can not transfer, if necessary, take from Storm32
Pin 15.16 - SCL / SDA, you can try to trick the camera using 24c02.
Pin 19 - HotPlug, you can also try not to use it.
Pin 13 - CEC, you can not use if you do not need sound.

total 19 - 9 = 10 pin for HDMI transmission, and 5 Pin for STORM32 = 15 Pin
if you use an 18-wire Slipring then there will still be 3 wires free.
The camera can be powered from the motor power line via the BEC.
controller version 3.3 can be installed not on Gimbal, but on board the copter / plane, then it will not need to pull control signals through the Slipring.
Jan 02, 2018, 09:27 PM
Registered User
Thanks for the pin info. Ill have to look into it some more.

From reading some other threads, it seems the dji cameras use some sort of network streaming through the gimbals.
Mucking around with the damaged inspire i could get the HD feed from the x3 camera without it seemingly having data coming from the flight controller. Perhaps its possible to feed the right video into lightbridge without needing a dji gimbal attached.
Ive seen that its possible to extract the video and use dji can commands to control the x3 gimbal from a teensy.
Ill just have to research more and tinker with it.
Jan 03, 2018, 02:30 AM
Quietly Scheming!!!
geekness's Avatar
@mike_kelly or @OlliW

Do you know the thickness of the motor module boards?
Thickness fully populated?
Thickness minus encoder?

Has any work been done to figure out the best distance away from the magnet the encoder should be?
Jan 03, 2018, 02:30 AM
Quietly Scheming!!!
geekness's Avatar
Quote:
Originally Posted by Gapey
A full HDMI cable is 19 wires, but their number can be reduced ...
Pin 14 - not used.
PIn 2,5,8,11 - Data Ground, on a short cable can be combined into 1 wire.
Pin 17- Ground, can be connected to ground Storm32.
Pin 18 - + 5v power, you can not transfer, if necessary, take from Storm32
Pin 15.16 - SCL / SDA, you can try to trick the camera using 24c02.
Pin 19 - HotPlug, you can also try not to use it.
Pin 13 - CEC, you can not use if you do not need sound.

total 19 - 9 = 10 pin for HDMI transmission, and 5 Pin for STORM32 = 15 Pin
if you use an 18-wire Slipring then there will still be 3 wires free.
The camera can be powered from the motor power line via the BEC.
controller version 3.3 can be installed not on Gimbal, but on board the copter / plane, then it will not need to pull control signals through the Slipring.
Very interesting information. makes me think.


Quick Reply
Message:

Thread Tools

Similar Threads
Category Thread Thread Starter Forum Replies Last Post
Cool T-STorM32: The best STorM32 ever !? OlliW Multirotor Drone Talk 2 Feb 21, 2017 05:02 PM