New beta version of openXsensor (=openXvario)
Moderator: rainer
Re: New beta version of openXsensor (=openXvario)
The Gy-63 has a 2.2 k resistor to Vcc.
If there is no other sensor connected to Arduino, High level voltage on SCL (and SDA) will be VCC (so normally 5 v).
The Gy-521 has a 4.7 k to 3.3 Volt. If you connect Gy-521to Arduino and GY-63, the High level voltage will be somewhere between 3.3 and 5 volt (about 4.4 volt) while the datasheet of 6050 says that it should not exceed 3.3Volt.
The INT pin lets the 6050 generate an interrupt on Arduino when new data are available.
When Arduino get the interrupt, it stops doing his normal job and start reading the data from 6050.
oXs uses this principle in order to keep the max of cpu power for other tasks.
If there is no other sensor connected to Arduino, High level voltage on SCL (and SDA) will be VCC (so normally 5 v).
The Gy-521 has a 4.7 k to 3.3 Volt. If you connect Gy-521to Arduino and GY-63, the High level voltage will be somewhere between 3.3 and 5 volt (about 4.4 volt) while the datasheet of 6050 says that it should not exceed 3.3Volt.
The INT pin lets the 6050 generate an interrupt on Arduino when new data are available.
When Arduino get the interrupt, it stops doing his normal job and start reading the data from 6050.
oXs uses this principle in order to keep the max of cpu power for other tasks.
Re: New beta version of openXsensor (=openXvario)
Ahh ok, thanks.. What happened was that I didn't see before that the 521 has an INT pin
Sorry about that. Getting old I guess
Ok, I will try a voltage divider on the I2C pins to make sure the voltage stays at the 3.3V level. Will test and let you know.
Thank you..
João
Sorry about that. Getting old I guess
Ok, I will try a voltage divider on the I2C pins to make sure the voltage stays at the 3.3V level. Will test and let you know.
Thank you..
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
-
- Posts: 241
- Joined: Tue Jan 15, 2013 9:41 pm
- Country: -
Re: New beta version of openXsensor (=openXvario)
The Int pin on the accelerometer has to connect to oXs and you have a choice between digital pin 2 or 3 as described in the config.h and config description.h. If you are going to the trouble of doing a layout and adding resistors etc you might as well just drop a dual mosfet package on and do the level shifting properly. It is a tiny 6 pin device and takes very little space on the board. Look at the schematic posted for the GY-86 or GY-63 and you can see how the level shifter is wired.
http://www.thaieasyelec.com/downloads/E ... 86_SCH.jpg
http://www.mouser.com/ProductDetail/Fai ... UCgHpQw%3d
http://www.thaieasyelec.com/downloads/E ... 86_SCH.jpg
http://www.mouser.com/ProductDetail/Fai ... UCgHpQw%3d
Re: New beta version of openXsensor (=openXvario)
Thanks.. will have a look,, Just about to test with resistors.. It could be done with transistors too
The PCB has to be of the size of both GY-521 and GY-63 anyway, so plenty of space
João
The PCB has to be of the size of both GY-521 and GY-63 anyway, so plenty of space
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: New beta version of openXsensor (=openXvario)
Guys, is this correct if I have the 6050 connected?
#define VARIO_PRIMARY BARO_AND_IMU
Thanks
João
#define VARIO_PRIMARY BARO_AND_IMU
Thanks
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: New beta version of openXsensor (=openXvario)
This define is foreseen when you use a ppm signal (controlled on Tx) in order to select between 2 Vspeed.
Without ppm, if you want to get a Vspeed based on baro + IMU, you need to have this define
// --------- 9 - Data to transmit ---------
#define VSPEED_SOURCE BARO_AND_IMU // select between FIRST_BARO, SECOND_BARO , AVERAGE_FIRST_SECOND, AIRSPEED_COMPENSATED , BARO_AND_IMU or PPM_SELECTION
Re: New beta version of openXsensor (=openXvario)
Sorry but the description file is very vague about this
And I still don't understand. Is it correct as I have above or not?
This is what I have. Is it correct, or should I select "FIRST_BARO"??
And I still don't understand. Is it correct as I have above or not?
This is what I have. Is it correct, or should I select "FIRST_BARO"??
// ***** 4.5 - Vertical speeds calculations *****
#define VARIO_PRIMARY BARO_AND_IMU // select between FIRST_BARO, SECOND_BARO , AVERAGE_FIRST_SECOND, AIRSPEED_COMPENSATED , BARO_AND_IMU
#define VARIO_SECONDARY FIRST_BARO // select between FIRST_BARO, SECOND_BARO , AVERAGE_FIRST_SECOND, AIRSPEED_COMPENSATED , BARO_AND_IMU
#define SWITCH_VARIO_MIN_AT_PPM 10
#define SWITCH_VARIO_MAX_AT_PPM 90[/quote
By the way, ACC seems to be working as I managed to read the calibration values in terminal.
Also vario is working, so, that proves ACC is working??. The radio takes about a second to start beeping, but I see the Vspd numbers react much faster.. Need to tell Mike about this.. Maybe due to some averaging ersky9x might be doing??
Thanks
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: New beta version of openXsensor (=openXvario)
Ok, just read it better, it looks like it is correct.. Sorry about that..
Here is my config file in case you want to have a look.. I just have vario + IMU and 3 cells connected to it.
Thanks
João
Edit, I have a 820 ohm resistor from IMU data line to I2C lines, and 1K5 from data lines to ground.
On PCB will have 1K5 and 2K2..
The divider reduces the I2C level from 5 to around 3.3V
Here is my config file in case you want to have a look.. I just have vario + IMU and 3 cells connected to it.
Thanks
João
Edit, I have a 820 ohm resistor from IMU data line to I2C lines, and 1K5 from data lines to ground.
On PCB will have 1K5 and 2K2..
The divider reduces the I2C level from 5 to around 3.3V
- Attachments
-
- oXs_config.zip
- (4.51 KiB) Downloaded 195 times
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: New beta version of openXsensor (=openXvario)
In your config, you have
#define VSPEED_SOURCE FIRST_BARO
This means that Vspeed sent to Tx is calculated based on the data from the first baro (without taking into account the data from IMU).
It can be confusing but FIRST_BARO does not mean PRIMARY.
PRIMARY and SECONDARY are defined and used only when you want to be able select from Tx side between 2 Vpseeds ( e.g between uncompensated Vspeed and dte - available if you have an airspeed too)
If you want to get Vspeed based both on baro and imu (in order to reduce reaction time), you have to change the line as follow
#define VSPEED_SOURCE BARO_AND_IMU
#define VSPEED_SOURCE FIRST_BARO
This means that Vspeed sent to Tx is calculated based on the data from the first baro (without taking into account the data from IMU).
It can be confusing but FIRST_BARO does not mean PRIMARY.
PRIMARY and SECONDARY are defined and used only when you want to be able select from Tx side between 2 Vpseeds ( e.g between uncompensated Vspeed and dte - available if you have an airspeed too)
If you want to get Vspeed based both on baro and imu (in order to reduce reaction time), you have to change the line as follow
#define VSPEED_SOURCE BARO_AND_IMU
Re: New beta version of openXsensor (=openXvario)
Ahh, I missed that setting.. I thought only the other one above was necessary.. But still, I didn't see this setting
So I have to select BARO AND IMU on both vario configuration and data to transmit, right??
Thanks.
João
So I have to select BARO AND IMU on both vario configuration and data to transmit, right??
Thanks.
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: New beta version of openXsensor (=openXvario)
#define VSPEED_SOURCE BARO_AND_IMU
is in section 9 (= data to transmit)
This define is valid for all protocols. That is the reason why it is before 9.1 that is specific to Frsky; 9.2 that is Hott specific, ...
is in section 9 (= data to transmit)
This define is valid for all protocols. That is the reason why it is before 9.1 that is specific to Frsky; 9.2 that is Hott specific, ...
Re: New beta version of openXsensor (=openXvario)
Yes, it seems to be reacting even faster now.. It is nearly instantaneous most of the times. But sometimes when going up or down the steps in my house, I get the odd beep in the wrong direction. For example, it is beeping the UP tones when I walk upstairs, but then suddenly it beeps once the DOWN tone..
Of course, this needs to be built on the PCB now and tested in flight
About the other problem, I had to set the below setting as shown. I think adding the vario brought the false zero volt cell alarm at power ON again. Increasing the delay to 1500 seems to have fixed it..
João
Of course, this needs to be built on the PCB now and tested in flight
About the other problem, I had to set the below setting as shown. I think adding the vario brought the false zero volt cell alarm at power ON again. Increasing the delay to 1500 seems to have fixed it..
João
// prepare the telemetry data to be sent (nb: data are prepared but not sent)
if ( millis() > 1500 ) oXs_Out.sendData();
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
-
- Posts: 241
- Joined: Tue Jan 15, 2013 9:41 pm
- Country: -
Re: New beta version of openXsensor (=openXvario)
I think you might be getting the confusing beeps because in climbing the steps you actually produce accelerations in both directions and the accelerometers can easily detect this but depending on the latency of the sampling and telemetry stream the vario audio routines in the TX dont always see it. Probably if you move it very smoothly without walking you will not see that behaviour.
Re: New beta version of openXsensor (=openXvario)
Probably That is why I said it needs to be tested in flight now
Sometimes get beeps when on the table.. But I have the light ON and the baro is exposed to it.. So, really need to make the PCBs now
One thing I forgot on my previous PCBs was a VCC (5V) pad.. This can be very useful when connecting for example a current sensor..
I'm powering the oXs from the first 2 cells of the LiPo battery. So, this voltage will be stable. Good for a stable voltage reading as well as a stable current reading..
João
Sometimes get beeps when on the table.. But I have the light ON and the baro is exposed to it.. So, really need to make the PCBs now
One thing I forgot on my previous PCBs was a VCC (5V) pad.. This can be very useful when connecting for example a current sensor..
I'm powering the oXs from the first 2 cells of the LiPo battery. So, this voltage will be stable. Good for a stable voltage reading as well as a stable current reading..
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
-
- Posts: 241
- Joined: Tue Jan 15, 2013 9:41 pm
- Country: -
Re: New beta version of openXsensor (=openXvario)
Speaking of stability, when I made my boards I included an RF filter on the line which goes to the analog reference for the A/D converters in the Atmega328. It is a good idea considering the oXs is in close proximity to the transmitter from the model's RX.
Re: New beta version of openXsensor (=openXvario)
Something like on this picture?
I plan to build my PCB tomorrow, so for now I won't include it.. I did think about it earlier. Actually I think the arduino doesn't have it? I never had problems with my other vario, but then, this one will be more sensitive. The other problem is space I'm including all the pins on the board, analog and digital.. I want to design only one board that can be used with all my models, and easily reprogrammed, hence the one wire bootloader thingy, which is working really well No need to leave pins for the FTDI. Only one pin and ground on Pin8.
João
I plan to build my PCB tomorrow, so for now I won't include it.. I did think about it earlier. Actually I think the arduino doesn't have it? I never had problems with my other vario, but then, this one will be more sensitive. The other problem is space I'm including all the pins on the board, analog and digital.. I want to design only one board that can be used with all my models, and easily reprogrammed, hence the one wire bootloader thingy, which is working really well No need to leave pins for the FTDI. Only one pin and ground on Pin8.
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
-
- Posts: 241
- Joined: Tue Jan 15, 2013 9:41 pm
- Country: -
Re: New beta version of openXsensor (=openXvario)
yes that is the idea.
Re: New beta version of openXsensor (=openXvario)
This filter can help reducing noise when measuring an analog voltage.
It will have no impact at all on Vspeed measurement (because Vspeed uses only digital signals from sensors)
It will have no impact at all on Vspeed measurement (because Vspeed uses only digital signals from sensors)
Re: New beta version of openXsensor (=openXvario)
exactly. I will see how voltage sensors behave, but the cell voltage seems pretty stable to me at the moment..
Mstrens, I gotta say, you're doing a great job with this project, Thank you..
I am using this project together with 3 other projects, which make my whole RC experience 90% open source.
Why only 90%??
Because servos and ESCs are still not open source??
I'm using the multi protocol module on my Ersky9x radios. 2 open source projects.. Then I build and use the DIY Frsky compatible receiver with diversity. Excellent project. Good range and more features thjan the original frsky D receivers.
For telemetry, of course, I use the openXsensor project.
it's wonderful.I'm using at the moment only open source stuff. Fantastic
And it is fun when you build your own stuff..
João
Mstrens, I gotta say, you're doing a great job with this project, Thank you..
I am using this project together with 3 other projects, which make my whole RC experience 90% open source.
Why only 90%??
Because servos and ESCs are still not open source??
I'm using the multi protocol module on my Ersky9x radios. 2 open source projects.. Then I build and use the DIY Frsky compatible receiver with diversity. Excellent project. Good range and more features thjan the original frsky D receivers.
For telemetry, of course, I use the openXsensor project.
it's wonderful.I'm using at the moment only open source stuff. Fantastic
And it is fun when you build your own stuff..
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
-
- Posts: 241
- Joined: Tue Jan 15, 2013 9:41 pm
- Country: -
Re: New beta version of openXsensor (=openXvario)
I would like to emphasize that as well. Mstrens is working very hard for us and I hope he knows it is so appreciated. It is always more satisfying when you use something you have crafted with your own hands, but for me I am continuously amazed by the example of the openRC community and see how in other forums and communities in which I am a member people have never seen and frankly do not believe that such a huge thing can be built up from the contributions of some tech savvy hobbyists who have a good ethic about sharing and recognize they can do something great without coveting the idea of some get rich scheme based on their knowledge. There are very few forums like this also where you don't encounter people with bad manners and behaviour. Aside from the remarkable open character here the other thing is we can just build things that we see a need for to fulfill a certain dream and it is something that can not even be bought as a product off a shelf because it is so wacky and cool and only a few people would want it, but with open hardware and software we can have it. These pages are full of such stories.
Re: New beta version of openXsensor (=openXvario)
I subscribe every single word..
João
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: New beta version of openXsensor (=openXvario)
Ok. I managed to build a version with GY-63 Baro and a GY-521 ACC. But not without a little fight till 5.30 in the morning last night And only solved the problem today, which was, the divider with a 1K5 to I2C lines and 2K2 to GND doesn't work. I tested with 820 Ohm and 1K5, and that worked. So, I had to remove the GY-521 again to replace the resistors. Thank God for chipquik. Wonderful to desolder stuff in seconds
Here are a couple pictures. The first shows how I connected Both sensors to the I2C lines.
And the other is a picture of it assembled. Without the sensors's PCB it can still be used with other sensors.
Perhaps I design another PCB so it takes another board on top (instead of the vario board)with a current sensor that use A6 and/or 7. So, for different models, I can just use a different sensor PCB soldered to the main one. The current sensor would also be powered by the oXs regulator. That would make the reading quite stable.. Just some ideas
I took some other pictures so I will probably start a build thread. Then I won't forget how I built it when I need another one There are a couple tricky steps that need to be done before you solder both boards together
Mstrens, I still had problems with the "#define MSEC_PER_BYTE" setting. I had it set to 7 and still had a little problem. Now I have set it to 8 and will test it like this, and then back to 7 again. The default (6) seems to be a bit too low.
Also the delay value in " if ( millis() > 1000 ) oXs_Out.sendData();" needs to be changed to at least 1500 to avoid the false alarms at power ON
With a vario and ACC 1000 is definitely not enough..
Reaction of the vario seems to be nearly instantaneous.. Very quick indeed, at least on the ground..
Thanks for all
João
Here are a couple pictures. The first shows how I connected Both sensors to the I2C lines.
And the other is a picture of it assembled. Without the sensors's PCB it can still be used with other sensors.
Perhaps I design another PCB so it takes another board on top (instead of the vario board)with a current sensor that use A6 and/or 7. So, for different models, I can just use a different sensor PCB soldered to the main one. The current sensor would also be powered by the oXs regulator. That would make the reading quite stable.. Just some ideas
I took some other pictures so I will probably start a build thread. Then I won't forget how I built it when I need another one There are a couple tricky steps that need to be done before you solder both boards together
Mstrens, I still had problems with the "#define MSEC_PER_BYTE" setting. I had it set to 7 and still had a little problem. Now I have set it to 8 and will test it like this, and then back to 7 again. The default (6) seems to be a bit too low.
Also the delay value in " if ( millis() > 1000 ) oXs_Out.sendData();" needs to be changed to at least 1500 to avoid the false alarms at power ON
With a vario and ACC 1000 is definitely not enough..
Reaction of the vario seems to be nearly instantaneous.. Very quick indeed, at least on the ground..
Thanks for all
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: New beta version of openXsensor (=openXvario)
It is fine that it works with a Gy-521 but if you have to buy new sensors, it is much easier to use a Gy-86 which has on the same board the MS5611, the 6050 and the level converter. So you have only 5 wires to connect. The gy-86 is available on aliexpress for less than 10 euro I think.
It is strange that it did not worked with the initial resistors because the initial resistors should provide a higher voltage (1.86 V in high level) than with the new resistors (1.65 volt).
Perhaps that the signal was disformed due to the 1.5 k resistor in serie on MS5611.
Your "high level of 1.65 Volt seems me quite low but if it works that is the most important..
In fact I do not think that resistors in serie to Gy-63 (so the 820 ) are really needed.
In fact on Gy-63 side, there is a 2.2k connected to Vcc (on the photo that I see on the net).
I expect that gy-63 can not really drive an output voltage to Vcc. When the MS5611want to force a high level, I think that MS5611 is in high impedance and so the voltage is forced by the 2.2k resistor connected to Vcc. If Vcc is 5 volt and if there is no divider, then voltage is 5 volt.
If you just add a resitor to ground, the voltage drop.
If Vcc is 5 volt and if the added resistor to ground is 3.3k , then the voltage will be about 5 v * 3.3 / (3.3 + 2.2 ) = 3 volt which is safe for the 6050.
In fact the voltage is just a bit higher because there is also a 4.7 k on gy521 connected to 3.3 volt.
"#define MSEC_PER_BYTE" can be increased.
I never tested it but a member on the forum asked for a low value in order to increase the number of data being transmitted per sec.
With his receiver (and Tx) a value of 6 was OK.
Perhaps that if you do not use the same Rx and TX module that 6 is to fast.
I will increase the delay from 1000 to 1500 in next release.
It is strange that it did not worked with the initial resistors because the initial resistors should provide a higher voltage (1.86 V in high level) than with the new resistors (1.65 volt).
Perhaps that the signal was disformed due to the 1.5 k resistor in serie on MS5611.
Your "high level of 1.65 Volt seems me quite low but if it works that is the most important..
In fact I do not think that resistors in serie to Gy-63 (so the 820 ) are really needed.
In fact on Gy-63 side, there is a 2.2k connected to Vcc (on the photo that I see on the net).
I expect that gy-63 can not really drive an output voltage to Vcc. When the MS5611want to force a high level, I think that MS5611 is in high impedance and so the voltage is forced by the 2.2k resistor connected to Vcc. If Vcc is 5 volt and if there is no divider, then voltage is 5 volt.
If you just add a resitor to ground, the voltage drop.
If Vcc is 5 volt and if the added resistor to ground is 3.3k , then the voltage will be about 5 v * 3.3 / (3.3 + 2.2 ) = 3 volt which is safe for the 6050.
In fact the voltage is just a bit higher because there is also a 4.7 k on gy521 connected to 3.3 volt.
"#define MSEC_PER_BYTE" can be increased.
I never tested it but a member on the forum asked for a low value in order to increase the number of data being transmitted per sec.
With his receiver (and Tx) a value of 6 was OK.
Perhaps that if you do not use the same Rx and TX module that 6 is to fast.
I will increase the delay from 1000 to 1500 in next release.
-
- Posts: 241
- Joined: Tue Jan 15, 2013 9:41 pm
- Country: -
Re: New beta version of openXsensor (=openXvario)
My concern is that simply using voltage dividers results in very marginal logic levels for the arduino input side and not much room for any noise.
Re: New beta version of openXsensor (=openXvario)
Yeah let's see if it works like this now.. It was my last GY-63 so next time I might get the GY-86. The problem is that aliexpress's shipping cost to Germany is normally very expensive. Also they don't use PayPal and I don't really want my credit card number on the net, specially in Chinamstrens wrote: ↑Wed Mar 01, 2017 4:07 pm It is fine that it works with a Gy-521 but if you have to buy new sensors, it is much easier to use a Gy-86 which has on the same board the MS5611, the 6050 and the level converter. So you have only 5 wires to connect. The gy-86 is available on aliexpress for less than 10 euro I think.
It is strange that it did not worked with the initial resistors because the initial resistors should provide a higher voltage (1.86 V in high level) than with the new resistors (1.65 volt).
Perhaps that the signal was disformed due to the 1.5 k resistor in serie on MS5611.
Your "high level of 1.65 Volt seems me quite low but if it works that is the most important..
This affect only HUB telemetry as far as I understand. The problem is there with the multiprotocol module and with the DJT as well. It was a hard job to trace the problem back to the oXs."#define MSEC_PER_BYTE" can be increased.
I never tested it but a member on the forum asked for a low value in order to increase the number of data being transmitted per sec.
With his receiver (and Tx) a value of 6 was OK.
Perhaps that if you do not use the same Rx and TX module that 6 is to fast.
Maybe the user that requested that is not sending cell voltage? It is where the problem become visible. Even if you are sending only 3 cells, sometime it starts sending 4 or even more.
I think the default value should be at least 7 as you had before.. If people want to try it faster then they can change the value.. There is clearly a problem with lower values.
ThanksI will increase the delay from 1000 to 1500 in next release.
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: New beta version of openXsensor (=openXvario)
Let's see how it behaves.. If there are problems I can always remove the 521 again and change/remove the resistors..RightRudder wrote: ↑Wed Mar 01, 2017 4:35 pm My concern is that simply using voltage dividers results in very marginal logic levels for the arduino input side and not much room for any noise.
Need some good weather now
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: New beta version of openXsensor (=openXvario)
Strange that shipping costs are high for Germany.
Many sellers have free shipping to Belgium.
I just checked on aliexpress and found Gy-86 for 9.6 euro (with free shipping) .
On ebay, it is 13.38 (free shipping).
Many sellers have free shipping to Belgium.
I just checked on aliexpress and found Gy-86 for 9.6 euro (with free shipping) .
On ebay, it is 13.38 (free shipping).
Re: New beta version of openXsensor (=openXvario)
Will check that, thanks..
João
EDIT: I think I have just found the same.. And it is indeed free shipping..
João
João
EDIT: I think I have just found the same.. And it is indeed free shipping..
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
-
- Posts: 241
- Joined: Tue Jan 15, 2013 9:41 pm
- Country: -
Re: New beta version of openXsensor (=openXvario)
I just made my first transaction about a month ago with Aliexpress to get my GY-86's. My friend did three transactions with them in 2016 and each time afterward he got a call from the credit card company that his card was compromised. That's 3 for 3. I still have my fingers crossed!
Re: New beta version of openXsensor (=openXvario)
That is why I prefer to pay a bit more and pay with PayPal..
I think with my bank i might be able to generate 1 time cards that can only be used once.. Gotta check that..
João
I think with my bank i might be able to generate 1 time cards that can only be used once.. Gotta check that..
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW