NAZE32+latest baseflight frozes on PC and in the air
-
- Posts: 7
- Joined: Sat Apr 19, 2014 10:20 am
NAZE32+latest baseflight frozes on PC and in the air
Strange thing happened yestrday. I have NAZe32 board rev.4. Old baseflight worked OK, then I tried harakiri 2.5 and was not so happy with it.
Few days back I tried latest baseflight. Flashing was done trough crome baseflight app.
After flasghing I calibratet ewerything and check how command is working. everything was ok, motors startet at the same level...
But then something strange happened. When I went to receiver tab and check if all is OK I noticed that after fev movement with stiks made board not responsiv.
I thout that this was because of PC.
I went out to test it and started flying. After monute or two quad sudenly flips on right side and goes strait down on propelers. I was flaying over high grass so no damage there.
After id fell down on motors, grass stoped motors - good thing because stiks on command did not work. Only solution to stop motor was to disconnect batery.
I tried again and again same result. Flip on right side in grass. No damage again. solution do disarm plate - battery disconnect.
Third time I held quad in hand and simulate fliyng. again after minute or two almost the same thing. In this case quad tried to flip ower front side. I held it firm so no damage there. Again command was not working and dissarming was done with batery disconnect.
Any idea what can be cause of this?
Few days back I tried latest baseflight. Flashing was done trough crome baseflight app.
After flasghing I calibratet ewerything and check how command is working. everything was ok, motors startet at the same level...
But then something strange happened. When I went to receiver tab and check if all is OK I noticed that after fev movement with stiks made board not responsiv.
I thout that this was because of PC.
I went out to test it and started flying. After monute or two quad sudenly flips on right side and goes strait down on propelers. I was flaying over high grass so no damage there.
After id fell down on motors, grass stoped motors - good thing because stiks on command did not work. Only solution to stop motor was to disconnect batery.
I tried again and again same result. Flip on right side in grass. No damage again. solution do disarm plate - battery disconnect.
Third time I held quad in hand and simulate fliyng. again after minute or two almost the same thing. In this case quad tried to flip ower front side. I held it firm so no damage there. Again command was not working and dissarming was done with batery disconnect.
Any idea what can be cause of this?
Re: NAZE32+latest baseflight frozes on PC and in the air
You tried to enable GPS.
-
- Posts: 7
- Joined: Sat Apr 19, 2014 10:20 am
Re: NAZE32+latest baseflight frozes on PC and in the air
I don`t use GPS. I did not configure anything that conserns GPS. All setting was default
Re: NAZE32+latest baseflight frozes on PC and in the air
nothing changed in firmware that would cause this.
if you can demonstrate a certain old:new version that has/doesn't have this issue.
there is one case where I2c bus will lock up processor but this only happens when rest of hardware is dead/dying/dodgy. and thats not affected by board revision.
if you can demonstrate a certain old:new version that has/doesn't have this issue.
there is one case where I2c bus will lock up processor but this only happens when rest of hardware is dead/dying/dodgy. and thats not affected by board revision.
-
- Posts: 7
- Joined: Sat Apr 19, 2014 10:20 am
Re: NAZE32+latest baseflight frozes on PC and in the air
i made some test and I noticed that:
if I reflash board no difference
if i set aux chanels and use them (1 in 2) board stops working
if I only set AUX chanels and not use them board stops wotking
If I DONT set any of AUX chanels board works longer few minutes longer but
If I go to CLI with status I see that there are I2C errors (min number was 2, higest number was 6).
One other thing - range of signals on command goes from 992 to 2008 - 2012.
I tried pushing command to max to see if it will stop working any sooner than If I dont push it ower 1850. No difference.
Is my board dying?
if I reflash board no difference
if i set aux chanels and use them (1 in 2) board stops working
if I only set AUX chanels and not use them board stops wotking
If I DONT set any of AUX chanels board works longer few minutes longer but
If I go to CLI with status I see that there are I2C errors (min number was 2, higest number was 6).
One other thing - range of signals on command goes from 992 to 2008 - 2012.
I tried pushing command to max to see if it will stop working any sooner than If I dont push it ower 1850. No difference.
Is my board dying?
-
- Posts: 7
- Joined: Sat Apr 19, 2014 10:20 am
Re: NAZE32+latest baseflight frozes on PC and in the air
aux 0 0
aux 1 0
aux 2 0
aux 3 0
aux 4 0
aux 5 0
aux 6 0
aux 7 0
aux 8 0
aux 9 0
aux 10 0
aux 11 0
aux 12 0
aux 13 0
aux 14 0
aux 15 0
aux 16 0
aux 17 0
aux 18 0
aux 19 0
aux 20 0
mixer QUADX
feature -PPM
feature -VBAT
feature -INFLIGHT_ACC_CAL
feature -SERIALRX
feature -MOTOR_STOP
feature -SERVO_TILT
feature -SOFTSERIAL
feature -LED_RING
feature -GPS
feature -FAILSAFE
feature -SONAR
feature -TELEMETRY
feature -POWERMETER
feature -VARIO
feature -3D
feature VBAT
map AETR1234
set looptime = 3500
set midrc = 1500
set minthrottle = 1150
set maxthrottle = 1850
set mincommand = 1000
set mincheck = 1100
set maxcheck = 1900
set deadband3d_low = 1406
set deadband3d_high = 1514
set neutral3d = 1460
set deadband3d_throttle = 50
set motor_pwm_rate = 400
set servo_pwm_rate = 50
set retarded_arm = 0
set flaps_speed = 0
set fixedwing_althold_dir = 1
set reboot_character = 82
set serial_baudrate = 115200
set softserial_baudrate = 9600
set softserial_1_inverted = 0
set softserial_2_inverted = 0
set gps_type = 0
set gps_baudrate = 0
set serialrx_type = 0
set telemetry_provider = 0
set telemetry_port = 0
set telemetry_switch = 0
set vbatscale = 110
set vbatmaxcellvoltage = 43
set vbatmincellvoltage = 33
set power_adc_channel = 0
set align_gyro = 0
set align_acc = 0
set align_mag = 0
set align_board_roll = 0
set align_board_pitch = 0
set align_board_yaw = 0
set yaw_control_direction = 1
set acc_hardware = 0
set max_angle_inclination = 500
set moron_threshold = 32
set gyro_lpf = 42
set gyro_cmpf_factor = 600
set gyro_cmpfm_factor = 250
set pid_controller = 0
set deadband = 0
set yawdeadband = 0
set alt_hold_throttle_neutral = 40
set alt_hold_fast_change = 1
set throttle_correction_value = 0
set throttle_correction_angle = 300
set rc_rate = 90
set rc_expo = 65
set thr_mid = 50
set thr_expo = 0
set roll_pitch_rate = 0
set yawrate = 0
set tparate = 0
set tpa_breakpoint = 1500
set failsafe_delay = 10
set failsafe_off_delay = 200
set failsafe_throttle = 1200
set failsafe_detect_threshold = 985
set rssi_aux_channel = 0
set yaw_direction = 1
set tri_unarmed_servo = 1
set gimbal_flags = 1
set acc_lpf_factor = 4
set accxy_deadband = 40
set accz_deadband = 40
set acc_unarmedcal = 1
set acc_trim_pitch = 0
set acc_trim_roll = 0
set baro_tab_size = 21
set baro_noise_lpf = 0.600
set baro_cf_vel = 0.985
set baro_cf_alt = 0.965
set mag_declination = 0
set gps_pos_p = 11
set gps_pos_i = 0
set gps_pos_d = 0
set gps_posr_p = 20
set gps_posr_i = 8
set gps_posr_d = 45
set gps_nav_p = 14
set gps_nav_i = 20
set gps_nav_d = 80
set gps_wp_radius = 200
set nav_controls_heading = 1
set nav_speed_min = 100
set nav_speed_max = 300
set nav_slew_rate = 30
set p_pitch = 40
set i_pitch = 30
set d_pitch = 23
set p_roll = 40
set i_roll = 30
set d_roll = 23
set p_yaw = 85
set i_yaw = 45
set d_yaw = 0
set p_alt = 50
set i_alt = 0
set d_alt = 0
set p_level = 90
set i_level = 10
set d_level = 100
set p_vel = 120
set i_vel = 45
set d_vel = 1
aux 1 0
aux 2 0
aux 3 0
aux 4 0
aux 5 0
aux 6 0
aux 7 0
aux 8 0
aux 9 0
aux 10 0
aux 11 0
aux 12 0
aux 13 0
aux 14 0
aux 15 0
aux 16 0
aux 17 0
aux 18 0
aux 19 0
aux 20 0
mixer QUADX
feature -PPM
feature -VBAT
feature -INFLIGHT_ACC_CAL
feature -SERIALRX
feature -MOTOR_STOP
feature -SERVO_TILT
feature -SOFTSERIAL
feature -LED_RING
feature -GPS
feature -FAILSAFE
feature -SONAR
feature -TELEMETRY
feature -POWERMETER
feature -VARIO
feature -3D
feature VBAT
map AETR1234
set looptime = 3500
set midrc = 1500
set minthrottle = 1150
set maxthrottle = 1850
set mincommand = 1000
set mincheck = 1100
set maxcheck = 1900
set deadband3d_low = 1406
set deadband3d_high = 1514
set neutral3d = 1460
set deadband3d_throttle = 50
set motor_pwm_rate = 400
set servo_pwm_rate = 50
set retarded_arm = 0
set flaps_speed = 0
set fixedwing_althold_dir = 1
set reboot_character = 82
set serial_baudrate = 115200
set softserial_baudrate = 9600
set softserial_1_inverted = 0
set softserial_2_inverted = 0
set gps_type = 0
set gps_baudrate = 0
set serialrx_type = 0
set telemetry_provider = 0
set telemetry_port = 0
set telemetry_switch = 0
set vbatscale = 110
set vbatmaxcellvoltage = 43
set vbatmincellvoltage = 33
set power_adc_channel = 0
set align_gyro = 0
set align_acc = 0
set align_mag = 0
set align_board_roll = 0
set align_board_pitch = 0
set align_board_yaw = 0
set yaw_control_direction = 1
set acc_hardware = 0
set max_angle_inclination = 500
set moron_threshold = 32
set gyro_lpf = 42
set gyro_cmpf_factor = 600
set gyro_cmpfm_factor = 250
set pid_controller = 0
set deadband = 0
set yawdeadband = 0
set alt_hold_throttle_neutral = 40
set alt_hold_fast_change = 1
set throttle_correction_value = 0
set throttle_correction_angle = 300
set rc_rate = 90
set rc_expo = 65
set thr_mid = 50
set thr_expo = 0
set roll_pitch_rate = 0
set yawrate = 0
set tparate = 0
set tpa_breakpoint = 1500
set failsafe_delay = 10
set failsafe_off_delay = 200
set failsafe_throttle = 1200
set failsafe_detect_threshold = 985
set rssi_aux_channel = 0
set yaw_direction = 1
set tri_unarmed_servo = 1
set gimbal_flags = 1
set acc_lpf_factor = 4
set accxy_deadband = 40
set accz_deadband = 40
set acc_unarmedcal = 1
set acc_trim_pitch = 0
set acc_trim_roll = 0
set baro_tab_size = 21
set baro_noise_lpf = 0.600
set baro_cf_vel = 0.985
set baro_cf_alt = 0.965
set mag_declination = 0
set gps_pos_p = 11
set gps_pos_i = 0
set gps_pos_d = 0
set gps_posr_p = 20
set gps_posr_i = 8
set gps_posr_d = 45
set gps_nav_p = 14
set gps_nav_i = 20
set gps_nav_d = 80
set gps_wp_radius = 200
set nav_controls_heading = 1
set nav_speed_min = 100
set nav_speed_max = 300
set nav_slew_rate = 30
set p_pitch = 40
set i_pitch = 30
set d_pitch = 23
set p_roll = 40
set i_roll = 30
set d_roll = 23
set p_yaw = 85
set i_yaw = 45
set d_yaw = 0
set p_alt = 50
set i_alt = 0
set d_alt = 0
set p_level = 90
set i_level = 10
set d_level = 100
set p_vel = 120
set i_vel = 45
set d_vel = 1
Re: NAZE32+latest baseflight frozes on PC and in the air
I2C errors should never happen. Unless you hooked up some external shit to pads.
So yes, it's dying. You could try re-reflowing MPU or other parts and see if that helps, but it didn't for me.
So yes, it's dying. You could try re-reflowing MPU or other parts and see if that helps, but it didn't for me.
Re: NAZE32+latest baseflight frozes on PC and in the air
I had one of these Naze32 boards (rev3 or 4, i cant remember). It eventually began to overheat and freeze. After a while, it would only boot up for a few seconds before it would lock up and fail. The MPU got so hot it burnt me when i touched it.
I trashed it and got another Witespy Flip32. Been happy ever since.
I trashed it and got another Witespy Flip32. Been happy ever since.
-
- Posts: 7
- Joined: Sat Apr 19, 2014 10:20 am
Re: NAZE32+latest baseflight frozes on PC and in the air
Board was working fine with harakiri fw few days back. I was flying quad with no problem.
Then I tried to flash it with baseflight and board did not want to connect to croma baseflight app.
I took twizeers, shortet two pins during booting and then flash board with baseflihgt. Flasing went OK. After flashing this problems started. Before it was working fine.
There was newer any thing connected to board exept radio and ESC.
Dont know how flasing could cause this problems...
Is it possible?
Then I tried to flash it with baseflight and board did not want to connect to croma baseflight app.
I took twizeers, shortet two pins during booting and then flash board with baseflihgt. Flasing went OK. After flashing this problems started. Before it was working fine.
There was newer any thing connected to board exept radio and ESC.
Dont know how flasing could cause this problems...
Is it possible?
Re: NAZE32+latest baseflight frozes on PC and in the air
Not possible, but with harakiri, who knows.
Re: NAZE32+latest baseflight frozes on PC and in the air
scorpioncek wrote:Dont know how flasing could cause this problems...
Is it possible?
hum..
did you compile the firmware by yourself ? -> if crashed , you board wont do anything , no calibration , no blinking led
did you check if the eeprom structure were identical ? -> should start , but fucked setting , reset all value to default before flight
i know for sure that you can have i2c error just by setting the right (or rather wrong) values in cli ...
best regards
-
- Posts: 7
- Joined: Sat Apr 19, 2014 10:20 am
Re: NAZE32+latest baseflight frozes on PC and in the air
treym wrote:scorpioncek wrote:Dont know how flasing could cause this problems...
Is it possible?
hum..
did you compile the firmware by yourself ? -> if crashed , you board wont do anything , no calibration , no blinking led
did you check if the eeprom structure were identical ? -> should start , but fucked setting , reset all value to default before flight
i know for sure that you can have i2c error just by setting the right (or rather wrong) values in cli ...
best regards
-I used hex that I got it from crome baseflight app - board is working OK for minute or two.
I also noticed that If I dont power on receiver board is working OK without i2C erorrs. As soon as i power up receiver and start moving command in CLI with status command I can see I2C errors. After 2-5 errors board hangs and is not responsive. Ony blue LED is on.
-I flashed board with baseflight from crome and I pressed default button in baseflight app. No difference. I also rebooted board and went to CLI and put default command there but also with no difference.
Are command values from 992 to 2014 ok? Maybe my radio is giving strange data to board and this is why it hangs...
Re: NAZE32+latest baseflight frozes on PC and in the air
Oj scorpioncek. Set sticks travel (end-points) from 1000 to 2000 or 1005 to 1995.
-
- Posts: 7
- Joined: Sat Apr 19, 2014 10:20 am
Re: NAZE32+latest baseflight frozes on PC and in the air
I did that, no difference, I also set mid point to 1500, no difference, I also set midpoint to 1520 no difference.
I also set max end point to 1850 - no difference.
I flashed with new hex (from last day) and only differnce that now it takes 400sek before board stops responding and there are allways only one or two I2C errors.
I also set max end point to 1850 - no difference.
I flashed with new hex (from last day) and only differnce that now it takes 400sek before board stops responding and there are allways only one or two I2C errors.
Re: NAZE32+latest baseflight frozes on PC and in the air
Then just try again harakiri and see if it works.
Re: NAZE32+latest baseflight frozes on PC and in the air
Hi there
Did someone of you have also boardfreezing since the new update from 24.04.2014 (Baseflight) ? It works in the beginning for about two minutes and freeze completly.
Today i test the new firmware and after about 2 minutes normal easy flight it made a flip. On my workbench i test that strange thing without propellers again and look, after about two minutes freeeze. The only thing you can do in this case is to unplug the battery.
Really strange and i have no clue about them. Someone can help me ?
I have this board MW32 Board: http://flyduino.net/Multikopter-FC_2
Did someone of you have also boardfreezing since the new update from 24.04.2014 (Baseflight) ? It works in the beginning for about two minutes and freeze completly.
Today i test the new firmware and after about 2 minutes normal easy flight it made a flip. On my workbench i test that strange thing without propellers again and look, after about two minutes freeeze. The only thing you can do in this case is to unplug the battery.
Really strange and i have no clue about them. Someone can help me ?
I have this board MW32 Board: http://flyduino.net/Multikopter-FC_2
Re: NAZE32+latest baseflight frozes on PC and in the air
prodrones wrote:I have this board MW32 Board: http://flyduino.net/Multikopter-FC_2
Then email or call support at flyduino. They will solve all your problems.
Re: NAZE32+latest baseflight frozes on PC and in the air
@prodrones and others : in cli reset to default and deactivate all feature (notably SERIALRX and FAILSAFE) then test with gui on the bench without anything connect to the fc but the esc and usb clable (no rx , no buetooth , nothing else) .. then , if your board stop working like you described and the gui says either 'msp checksum error' or 'nothing' then your board has issue .. if not then , test with a lipo battery ,then add other components..
Re: NAZE32+latest baseflight frozes on PC and in the air
Hi. I have original rev5 board and load the latest FW from 24.4.2014 with bf configurator. Did 3 16 minutes FPV flights and nothing happened. But every time I load new FW on board, I go to CLI and type: defaults and hit enter. Only then I start to configure FC.
Re: NAZE32+latest baseflight frozes on PC and in the air
treym wrote:@prodrones and others : in cli reset to default and deactivate all feature (notably SERIALRX and FAILSAFE) then test with gui on the bench without anything connect to the fc but the esc and usb clable (no rx , no buetooth , nothing else) .. then , if your board stop working like you described and the gui says either 'msp checksum error' or 'nothing' then your board has issue .. if not then , test with a lipo battery ,then add other components..
Hi thx for that tips. I done that before but that wasnt the case. If i only plug in the USB it works for hours. If i plug in USB+ Battery it works in armed mode also for hours.
Only when i spin up the motors it will freeze. The baseflight will not give out any error.
Thats why i looked today on the accelometers and i see that i have many vibrations on the board. I have made a screenshot from it. Is it possible to overload the bord with vibrations ?
I have a 250 sized H Quad completly made out of carbonfiber. So every vibration will also go trough the controller. Controller is put on nylon standoffs.
I see in a earlier firmware there are a feature called "gyro_smoothing" i dont can find them anymore. Any other menu to smooth gyros ?
You will find in the attachement a screenshot of the raw sensor datas. Did you have vibrations with the same cycles or much less ?
Re: NAZE32+latest baseflight frozes on PC and in the air
Hi there
I can locate the bug now. It must be something new with accelerometer (code?).
If i have only manual mode activated it works great and dont freeze. If i use a flightmode that use accelerometer it would freeze after max. 2 minutes.
I have two accelerometer probably that would produce a freeze ?- MPU6050 and MMA8452
Thx for help
I can locate the bug now. It must be something new with accelerometer (code?).
If i have only manual mode activated it works great and dont freeze. If i use a flightmode that use accelerometer it would freeze after max. 2 minutes.
I have two accelerometer probably that would produce a freeze ?- MPU6050 and MMA8452
Thx for help
Re: NAZE32+latest baseflight frozes on PC and in the air
Have you emailed the chinese cloneshop you purchased that shit from yet?
Re: NAZE32+latest baseflight frozes on PC and in the air
prodrones wrote:If i have only manual mode activated it works great and dont freeze. If i use a flightmode that use accelerometer it would freeze after max. 2 minutes.
i see no changes in the code that relate to such issue ...
Re: NAZE32+latest baseflight frozes on PC and in the air
timecop wrote:Have you emailed the chinese cloneshop you purchased that shit from yet?
Hi timecop. Im not sure if you are the "real" one. In europe there are not so many solutions for naze32. I buy them on a german website. Did you have a better solution ? Is my board a fake ?!? I pay for them nearly 50eur ! I would buy immediatly from you a real one. Please Pm me if you sell them.
I Email Flyduino but they dont answer me.
Re: NAZE32+latest baseflight frozes on PC and in the air
Yes man. This is THE REAL timecop - original maker of Naze32 board and yes...he is selling them: http://abusemark.com/store/index.php?ma ... oqonlr58d2 and if you order the board...you can get it in 3 days from Japan to your home Buy original.
- Crashpilot1000
- Posts: 631
- Joined: Tue Apr 03, 2012 7:38 pm
Re: NAZE32+latest baseflight frozes on PC and in the air
Well, since the designfiles of n5 are not published it is junk in terms of open development. Considering that TC cloned himself the original chinese(?) design it is nothing to praise him about holding back designfiles now - he simply forgot where he came from - amne$ia.
- Attachments
-
- RememberOrigins.gif
- (4.11 KiB) Not downloaded yet
Re: NAZE32+latest baseflight frozes on PC and in the air
Crashpilot1000 wrote:Well, since the designfiles of n5 are not published it is junk in terms of open development. Considering that TC cloned himself the original chinese(?) design it is nothing to praise him about holding back designfiles now - he simply forgot where he came from - amne$ia.
well , this design has little to do with the rev5 board and since the rev4 board is available to study .. I dont see what is your point, the price is so low and the rever engenering so obvious for this simple pcb ... maybe you want timecope to pay you the right to use his eagle file ?
if wiring an i2c bus a big deal them you might just not want to manufacture board .
but yes , one thing is wrong here .. this obviously overpriced hardware thats seem to look up in the air.
edit : here , just for you , more "fake" patent trolling .
http://diydrones.com/profiles/blogs/pha ... 2#comments
Code: Select all
Yes, I'm sure you're right that they should actually be publishing their PCB layouts and firmware because it's a derivative of the APM. Just like the mini-APM that hobby king made.
- Crashpilot1000
- Posts: 631
- Joined: Tue Apr 03, 2012 7:38 pm
Re: NAZE32+latest baseflight frozes on PC and in the air
"..I dont see what is your point.."
My point are the missing design files no matter if it's overpriced or not or if it is hard to put sensors on an I2C bus. It is based on Creative Commons design so anyone faintly familiar with that concept would have released the files immediately.
My point are the missing design files no matter if it's overpriced or not or if it is hard to put sensors on an I2C bus. It is based on Creative Commons design so anyone faintly familiar with that concept would have released the files immediately.
Re: NAZE32+latest baseflight frozes on PC and in the air
Crashpilot1000 wrote:It is based on Creative Commons design so anyone faintly familiar with that concept would have released the files immediately.
Except it was MY decision to publish schematic under CC BY-NC-SA which, if you'd actually gave a fuck, means it isn't there for clonespy & friends to go and make their shitty derivatives from. If someone thinks they can actually take the gerbers (if I provided them) and manufacture PCB and assemble it with parts for less than 16 EUR or wahtever it would cost them to just buy it, i'd totally want to see it happen. Except it won't. All it would do is let clonespy make a bunch of shitty copies on garbage pcb with reject components. That takes no skill or effort.
NonCommercial — You may not use the material for commercial purposes.
(not that I give a fuck, I spend major part of the day either assembling these fucking boards or shipping them out, if that means I lose 50 sales per day to clonespy, the better, because I still have another 50 to deal with).
- Crashpilot1000
- Posts: 631
- Joined: Tue Apr 03, 2012 7:38 pm
Re: NAZE32+latest baseflight frozes on PC and in the air
Ahh, ok you gave CC BY-NC-SA because you are a good fellow not because you already based it on a clone yourself. Thanks!
Re: NAZE32+latest baseflight frozes on PC and in the air
The genuine Naze32 boards are so cheap that I'd still buy them even if there were cheaper Chinese copies around. Whenever I've ordered to the UK I get the boards within about 3 to 4 working days. That seems really good considering they come all the way from Japan.
The only broken Naze32 board I have is one where I got the soldering wrong. My soldering has improved since then
Do I get a discount now
The only broken Naze32 board I have is one where I got the soldering wrong. My soldering has improved since then
Do I get a discount now
Re: NAZE32+latest baseflight frozes on PC and in the air
Crashpilot1000 wrote:Ahh, ok you gave CC BY-NC-SA because you are a good fellow not because you already based it on a clone yourself. Thanks!
And all freeflight-related bits (about the only one remaining is the shitty PWM assignment) is still right there in latest schematic.
Thank you. If you knew how to code, the rest wouldn't concern you, but you don't, so you find retarded things to nitpick about. I don't mind, but you're just wasting your time (much like you're wasting time maintaining that zip-file with bunch of shitty copypasted code that barely works).
- Crashpilot1000
- Posts: 631
- Joined: Tue Apr 03, 2012 7:38 pm
Re: NAZE32+latest baseflight frozes on PC and in the air
Haha I wonder how you always absolutely falsely accuse me of copying code - and don't tell me it's the sphere-fit-least-squares code that improves mag calibration that is not even a fraction of what I have changed. On the other side I see some stuff silently from harakiri being backported to bf - so even the zip type codepublishing doesn't seem to be a waste of time after all - so I am very happy with that.
What about you? Copying hardware and copying the complete mwii project? Remember the guy that wrote you the makefile because you couldn't? Remember yourself being helpless on RCG because you couldn't figure out how to change orientation of sensors - because you are the super - coder? Simply rediculous. Not publishing designfiles in a really open project like mwii is a complete fail IMHO.
What about you? Copying hardware and copying the complete mwii project? Remember the guy that wrote you the makefile because you couldn't? Remember yourself being helpless on RCG because you couldn't figure out how to change orientation of sensors - because you are the super - coder? Simply rediculous. Not publishing designfiles in a really open project like mwii is a complete fail IMHO.
Re: NAZE32+latest baseflight frozes on PC and in the air
> Haha I wonder how you always absolutely falsely accuse me of copying code - and don't tell me it's the sphere-fit-least-squares code that improves mag calibration that is not even a fraction of what I have changed.
It's unnecessary bloat like that, which provides maginally (if at all noticeable) results, that's a problem. Did you know, with properly calibrated sensors (and I mean properly, which is beyond the scope of this hobby project), mag is not needed to keep heading *at all*? How about doing some REAL improvements like floating-point entry of mag_declination, instead of shitty fixedpoint stuff I did because I didn't feel like offending gcc users by pulling in atof().
> On the other side I see some stuff silently from harakiri being backported to bf - so even the zip type codepublishing doesn't seem to be a waste of time after all - so I am very happy with that.
If your stuff was in source control you could point out to what was being "backported", but as long as it zips, I have no idea. I hardly have time to review other people's patches, never mind keeping track of your zip files in a forum.
> What about you? Copying hardware and copying the complete mwii project?
Copying stm32 with sensors on I2C? Aww yeah. My shit is still around. Is freeflight? Is it even supported anymore? Yes, I could have changed pinout and left thousands of users stuck to running your code and miss out on all the innovations in baseflight that only runs on new closed-source hardware. But guess what, baseflight runs on every board from rev0 to rev5. Let's see you achieve the same. I bet you didn't even test your shit on anything beyond rev4/5. Copying multiwii? Yeah, never mind all the drivers and other unrelated shit.
> Remember the guy that wrote you the makefile because you couldn't?
Why would I need to write a makefile for a compiler I don't use? And if there is someone who can, why stop them? Guess whose makefile you're currently using to compile your shit? Oh, right.
> Remember yourself being helpless on RCG because you couldn't figure out how to change orientation of sensors - because you are the super - coder?
Remember the sensor orientation in "original" multiwii was so fucked it made no sense. double-rotated shit that depended on some incorrect initial alignment of wiimotionplus or something. I do have more important things to do than try 144 combinations of mag orientation. If someone has the time to do it, by all means, knock yourself out.
> Simply rediculous. Not publishing designfiles in a really open project like mwii is a complete fail IMHO.
I'm still waiting for your amazing cheap german hardware with published design files. The only German STM32 hardware I'm aware of costs 100EUR and comes with a hacked up Taulabs port.
How about "design files" for MW32, Flip, etc? Oh, right! I'm the bad guy, so I'm the only one who needs to provide them. I bet neither clonespy or paul baked even HAVE those files, since they just order that shit straight out of China. Why innovate when you can just buy now on taobao?
Why are you still wasting time with me? Don't you have some code to copypaste and forget to reindent?
It's unnecessary bloat like that, which provides maginally (if at all noticeable) results, that's a problem. Did you know, with properly calibrated sensors (and I mean properly, which is beyond the scope of this hobby project), mag is not needed to keep heading *at all*? How about doing some REAL improvements like floating-point entry of mag_declination, instead of shitty fixedpoint stuff I did because I didn't feel like offending gcc users by pulling in atof().
> On the other side I see some stuff silently from harakiri being backported to bf - so even the zip type codepublishing doesn't seem to be a waste of time after all - so I am very happy with that.
If your stuff was in source control you could point out to what was being "backported", but as long as it zips, I have no idea. I hardly have time to review other people's patches, never mind keeping track of your zip files in a forum.
> What about you? Copying hardware and copying the complete mwii project?
Copying stm32 with sensors on I2C? Aww yeah. My shit is still around. Is freeflight? Is it even supported anymore? Yes, I could have changed pinout and left thousands of users stuck to running your code and miss out on all the innovations in baseflight that only runs on new closed-source hardware. But guess what, baseflight runs on every board from rev0 to rev5. Let's see you achieve the same. I bet you didn't even test your shit on anything beyond rev4/5. Copying multiwii? Yeah, never mind all the drivers and other unrelated shit.
> Remember the guy that wrote you the makefile because you couldn't?
Why would I need to write a makefile for a compiler I don't use? And if there is someone who can, why stop them? Guess whose makefile you're currently using to compile your shit? Oh, right.
> Remember yourself being helpless on RCG because you couldn't figure out how to change orientation of sensors - because you are the super - coder?
Remember the sensor orientation in "original" multiwii was so fucked it made no sense. double-rotated shit that depended on some incorrect initial alignment of wiimotionplus or something. I do have more important things to do than try 144 combinations of mag orientation. If someone has the time to do it, by all means, knock yourself out.
> Simply rediculous. Not publishing designfiles in a really open project like mwii is a complete fail IMHO.
I'm still waiting for your amazing cheap german hardware with published design files. The only German STM32 hardware I'm aware of costs 100EUR and comes with a hacked up Taulabs port.
How about "design files" for MW32, Flip, etc? Oh, right! I'm the bad guy, so I'm the only one who needs to provide them. I bet neither clonespy or paul baked even HAVE those files, since they just order that shit straight out of China. Why innovate when you can just buy now on taobao?
Why are you still wasting time with me? Don't you have some code to copypaste and forget to reindent?
- Crashpilot1000
- Posts: 631
- Joined: Tue Apr 03, 2012 7:38 pm
Re: NAZE32+latest baseflight frozes on PC and in the air
1. I am not doing an own hardwareproject, that is for sure (you may mix me up with another guy?). And have no financial interest in it and I consider myself not sponsored (I happily received 3 gifts from private guys - no companies like whitespy, flyduino, pitchpump or whatever you might think of.) So my collection of hardware is n3/4 and mw32v2. I am just doing my own thing and I am happy if something usable comes out that may other users find usable as well.
2. I am not the copy over guy you like to put me - that is a plain lie and nothing more - period. There was an update of the arducopter gps code that eos bandi missed because it appeared after he put the code in - I just added that update concerning the tiltcompensation of the already lifted code by the mwii project. On the other hand I rewrote the PH part and added a precise bearing calculation based on known gps formulas, got rid of the slew rate - just to mention some further changes.
3. heading is in float - dunno what you refer to.
4. Openhardwareplans are a must simply because humans have no eternal life. Basically your extra eeprom idea of n5 is good and it can be put to good use - on the other hand why bother with it on closed hardware that is run by one guy.
5. Clones: I own MW32v2 and I am not impressed with it I can tell you. Your N3 and N4 have way more quality - no doubt about that - your hardware is better than the mw32v2 I have. But point 4 is an absolute downer for me so that's mainly (not the only reason) why I tried out a "compatible" that sadly isn't a direct design clone - that would have been probably better.
6. Have a nice day!
Cheers
Rob
2. I am not the copy over guy you like to put me - that is a plain lie and nothing more - period. There was an update of the arducopter gps code that eos bandi missed because it appeared after he put the code in - I just added that update concerning the tiltcompensation of the already lifted code by the mwii project. On the other hand I rewrote the PH part and added a precise bearing calculation based on known gps formulas, got rid of the slew rate - just to mention some further changes.
3. heading is in float - dunno what you refer to.
4. Openhardwareplans are a must simply because humans have no eternal life. Basically your extra eeprom idea of n5 is good and it can be put to good use - on the other hand why bother with it on closed hardware that is run by one guy.
5. Clones: I own MW32v2 and I am not impressed with it I can tell you. Your N3 and N4 have way more quality - no doubt about that - your hardware is better than the mw32v2 I have. But point 4 is an absolute downer for me so that's mainly (not the only reason) why I tried out a "compatible" that sadly isn't a direct design clone - that would have been probably better.
6. Have a nice day!
Cheers
Rob
Re: NAZE32+latest baseflight frozes on PC and in the air
ok.. so to summazize : this about the "coding skills " .. ?
Could you please continue this discussion in a more appropriate sub forum , so you can trustfully expresse your feelings to each other ?
Could you please continue this discussion in a more appropriate sub forum , so you can trustfully expresse your feelings to each other ?
Re: NAZE32+latest baseflight frozes on PC and in the air
I think what you meant to say is , "get a room"
Re: NAZE32+latest baseflight frozes on PC and in the air
I have just the right song for you two guys But please no resentment.
http://www.youtube.com/watch?v=zsmUOdmm02A
http://www.youtube.com/watch?v=zsmUOdmm02A
Re: NAZE32+latest baseflight frozes on PC and in the air
So back on topic. I am experiencing similar problems with my genuine REV4 naze 32 (white).
The board stops working and the motor output stays constant. The only thing I can do is unplug the battery to make it stop.
The problem occurs with the hex file from the commit on 8 april and newer.
With the commit of 6 april there is no issue everything works just fine.
The board stops working and the motor output stays constant. The only thing I can do is unplug the battery to make it stop.
The problem occurs with the hex file from the commit on 8 april and newer.
With the commit of 6 april there is no issue everything works just fine.
Re: NAZE32+latest baseflight frozes on PC and in the air
Roeland54 wrote:The problem occurs with the hex file from the commit on 8 april and newer.
With the commit of 6 april there is no issue everything works just fine.
Ooh, I just found this thread. I apparently have the same or similar issue with my Naze32.
timecop, if I had enabled GPS before, then disabled it and removed the GPS radio, does this cause the failure/lockup? Seems kind of fiddly.
(saw the gps assumption in another thread)
So, how can I get a previous release of the firmware/Baseflight to use?
Re: NAZE32+latest baseflight frozes on PC and in the air
You don't, you need to find what the problem is and fix it.
Re: NAZE32+latest baseflight frozes on PC and in the air
Hi,
It seems I am not alone...
Short background story: I got a small quad (Warthox frame, 2208 motors, 8x4.5 props, 3S 2200mAh LiPo). Naze32 of course. Totally awesome flying. Very predictable behavior. Light, quiet, fast.
The firmware was old. So old that I have to use the MultiWiiConf tool to configure it. I got another Naze32 on my Tri and it's awesome there too.
Life was good.
Then I thought: Let me update the firmware on my quad so I can use the Chrome Baseflight Configurator instead. Because I could not use it at all. Would not connect. MWConf worked.
So I updated. Version April 30 2014 made at 00:34:32.
First problem: When testing the receiver signals in the GUI, the GUI locked down. Nothing but a power down of the Naze worked. But then it worked. Happened twice during congfiguration.
After all was configured (and yes, I reset all variables), I was going to fly a bit. Careful at first as the parameters might have changed their effect.
Was hovering for 20 sec, then wanted to move slightly left and the quad went right side up and it did not stop that rotation until it hit the ground.
I could not disarm. All props were spinning. The only way to stop them was disconnecting the battery.
Luckily nothing broke and I even found the prop nuts (that's a first). Cleaned up everything, put the props back (nothing broke). Held the quad in the hand and tested. Forward, back, left, right, yaw, repeat...and when tilting right, it did not react anymore at all. Again no disarm helped. Tested it again. Happened again. Took longer that time (about 1 min).
Needless to say, that's no good.
Some more info: Quad-X setup, default PID, slightly increase P, rate 0.1 for tilt/roll, 0.45 for yaw. Receiver JR RG831 (no PPM). Battery was full and RX voltage was 5.2V (same as the Naze would get). Never had an issue with this quad. Was flying it fast for a year now. The only change is the firmware.
And it's an original Naze (v3 or 4) from timecop (since I am in Japan, I buy locally).
It seems I am not alone...
Short background story: I got a small quad (Warthox frame, 2208 motors, 8x4.5 props, 3S 2200mAh LiPo). Naze32 of course. Totally awesome flying. Very predictable behavior. Light, quiet, fast.
The firmware was old. So old that I have to use the MultiWiiConf tool to configure it. I got another Naze32 on my Tri and it's awesome there too.
Life was good.
Then I thought: Let me update the firmware on my quad so I can use the Chrome Baseflight Configurator instead. Because I could not use it at all. Would not connect. MWConf worked.
So I updated. Version April 30 2014 made at 00:34:32.
First problem: When testing the receiver signals in the GUI, the GUI locked down. Nothing but a power down of the Naze worked. But then it worked. Happened twice during congfiguration.
After all was configured (and yes, I reset all variables), I was going to fly a bit. Careful at first as the parameters might have changed their effect.
Was hovering for 20 sec, then wanted to move slightly left and the quad went right side up and it did not stop that rotation until it hit the ground.
I could not disarm. All props were spinning. The only way to stop them was disconnecting the battery.
Luckily nothing broke and I even found the prop nuts (that's a first). Cleaned up everything, put the props back (nothing broke). Held the quad in the hand and tested. Forward, back, left, right, yaw, repeat...and when tilting right, it did not react anymore at all. Again no disarm helped. Tested it again. Happened again. Took longer that time (about 1 min).
Needless to say, that's no good.
Some more info: Quad-X setup, default PID, slightly increase P, rate 0.1 for tilt/roll, 0.45 for yaw. Receiver JR RG831 (no PPM). Battery was full and RX voltage was 5.2V (same as the Naze would get). Never had an issue with this quad. Was flying it fast for a year now. The only change is the firmware.
And it's an original Naze (v3 or 4) from timecop (since I am in Japan, I buy locally).
Re: NAZE32+latest baseflight frozes on PC and in the air
So you can meet with tc and together check what s wrong
Re: NAZE32+latest baseflight frozes on PC and in the air
The good news is that the firmware from April 6th is ok. 2 batteries emptied. No issue.
Being more specific: https://github.com/multiwii/baseflight/tree/f336fc8d20e752d1b7f31b7fa01a66365df0b273/obj
is the version I use. Works on my quad.
Being more specific: https://github.com/multiwii/baseflight/tree/f336fc8d20e752d1b7f31b7fa01a66365df0b273/obj
is the version I use. Works on my quad.
Re: NAZE32+latest baseflight frozes on PC and in the air
Roeland54 wrote:The problem occurs with the hex file from the commit on 8 april and newer.
With the commit of 6 april there is no issue everything works just fine.
Did you try this? April 8 version locks up?
I have not tested (yet) the version from April 8th, but the differences according to github are small and HoTT related.
I do not use HoTT. I use no telemetry at all (not from Naze at least).
Re: NAZE32+latest baseflight frozes on PC and in the air
hkubota wrote:The good news is that the firmware from April 6th is ok. 2 batteries emptied. No issue.
Being more specific: https://github.com/multiwii/baseflight/tree/f336fc8d20e752d1b7f31b7fa01a66365df0b273/obj
is the version I use. Works on my quad.
Thanks for this, I am going to download this hex and flash tonight, hopefully fixing all lockup issues I am having. Maybe even fly the quad again.
BTW, how did you find the hex file for a specific date? I have asked tc but don't want to bug him with noob questions.
Re: NAZE32+latest baseflight frozes on PC and in the air
hkubota wrote:Did you try this? April 8 version locks up?
Yes I did try this. It did lock up. But it would be good to have some confirmation that it reacts the same on other boards.
setup:
Full naze32 rev4 white
feature gps enabled (but no gps connected)
receiver connected (no ppm)
1 esc connected for power.
have to rewire my receiver so I can test it without GPS enabled.
@Naze_Mote you kan find it here https://github.com/multiwii/baseflight/blob/master/obj/baseflight.hex
then click "history"
@timecop I will dive into the code to pinpoint the issue. But it could take a while, my knowledge of programming is still very limited...
Re: NAZE32+latest baseflight frozes on PC and in the air
Roeland54 wrote:@Naze_Mote you kan find it here https://github.com/multiwii/baseflight/blob/master/obj/baseflight.hex
then click "history"
OK, thanks!
Do I then click "Browse Code" > select the 'Raw' button > Copy All text > save locally as text file with .hex file extension?