Advertisement
Guest User

alta

a guest
Jan 9th, 2023
22
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.80 KB | None | 0 0
  1. System Loader V1.2.1
  2. FMU V1.3.22
  3. OSD V1.0.6
  4. POWER V0.0.1
  5. MOTOR_TELEM V1.0.0
  6. MOTOR_TELEM_HW V255.255.65535
  7.  
  8. FMUv2 ver 0xE : Rev 0 V30
  9. [boot] Fault Log info File No 4 Length 3177 flags:0x01 state:1
  10. [boot] Fault Log is Armed
  11. sercon: Registering CDC/ACM serial driver
  12. sercon: Successfully registered the CDC/ACM serial driver
  13. HW arch: PX4_FMU_V3
  14. HW type: V30
  15. HW version: 0x0009000E
  16. HW revision: 0x00000000
  17. FW git-hash: 075ab7242ee99ada995d066334ed4743078fffaa
  18. FW version: Release 1.3.6 (16975615)
  19. FW git-branch: ff-release/hotfix3
  20. OS: NuttX
  21. OS version: Release 7.28.0 (119275775)
  22. OS git-hash: 1381738a7ca3b66dc6f9bdb946a35a6c7d11ca25
  23. Build datetime: Apr 21 2022 21:49:56
  24. Build uri: localhost
  25. Toolchain: GNU GCC, 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255 204]
  26. PX4GUID: 0001000000003832383333385115004c001f
  27. MCU: STM32F42x, rev. 3
  28. [hardfault_log] Fault Log is Armed
  29. INFO [tune_control] Publishing standard tune 1
  30. INFO [param] selected parameter default file /fs/mtd_params
  31. Board defaults: /etc/init.d/rc.board_defaults
  32. WARN [rgbled] no RGB led on bus #2
  33. rgbled1 on I2C bus 1 at 0x39 (bus: 100 KHz, max: 100 KHz)
  34. nsh: rgbled_pwm: command not found
  35. WARN [blinkm] I2C init failed
  36. WARN [blinkm] init failed
  37. INFO [FF_CAN_QUAD] FF CAN Module Started
  38. INFO [FF_CAN_QUAD] CAN initialized.
  39. INFO [FF_CAN_QUAD] CAN registered.
  40. INFO [FF_CAN_QUAD] FF_CANRead Task spawned.
  41. INFO [FF_CAN_QUAD] --------------------------
  42. INFO [FF_CAN_QUAD] Bootloader jumper started.
  43. INFO [FF_CAN_QUAD] ----------------------------
  44. INFO [FF_CAN_QUAD] FF_CAN_ReadeINFO [FF_CAN_QUAD] BootloaderJur-> Thread started.
  45. mp-> sending jump command to CAN ID: 00000009.
  46. INFO [FF_CAN_QUAD] BootloaderJump-> CAN opened for write (blocking).
  47. INFO [FF_CAN_QUAD] BootloaderJump-> Sending jump address value.
  48. INFO [FF_CAN_QUAD] ----------------------------
  49. INFO [FF_CAN_QUAD] BootloaderJump-> sending jump command to CAN ID: 0000000a.
  50. INFO [FF_CAN_QUAD] BootloaderJump-> CAN opened for write (blocking).
  51. INFO [FF_CAN_QUAD] BootloaderJump-> Sending jump address value.
  52. INFO [FF_CAN_QUAD] ----------------------------
  53. INFO [FF_CAN_QUAD] BootloaderJump-> sending jump command to CAN ID: 0000000e.
  54. INFO [FF_CAN_QUAD] BootloaderJump-> CAN opened for write (blocking).
  55. INFO [FF_CAN_QUAD] BootloaderJump-> Sending jump address value.
  56. INFO [FF_CAN_QUAD] Bootloader jumper finished.
  57. INFO [FF_CAN_QUAD] FF_CAN_WriteINFO [FF_CAN_QUAD] FF_CANWrite r-> Thread started.
  58. Task spawned.
  59. INFO [FF_CAN_QUAD] FF_CAN_WriteINFO [FF_CAN_QUAD] FF CAN Modulr-> CAN opened
  60. e Exited
  61. INFO [px4io] default PWM output device
  62. Board sensors: /etc/init.d/rc.board_sensors
  63. WARN [hmc5883] no device on bus 1 (type: 2)
  64. WARN [lis3mdl] no device on bus 2
  65. ERROR [ak09916] driver start failed
  66. IST8310 on I2C bus 1 at 0x0e (bus: 100 KHz, max: 400 KHz)
  67. INFO [ist8310] cross axis cal: [+1.01,+0.05,-0.04|-0.05,+1.01,-0.02|-0.05,-0.03,+1.00]
  68. INFO [ist8310] no device on bus 5
  69. ERROR [ist8310] calibration only feasible against one bus
  70. WARN [hmc5883] no device on bus 2 (type: 1)
  71. WARN [mpu6000] no device on bus #3 (SPI1)
  72. WARN [mpu6000] no device on bus #5 (SPI4)
  73. INFO [mpu9250] Bus probed: 5
  74. MPU9250 on SPI bus 4 at 4 (1000 KHz)
  75. INFO [mpu9250] accel cutoff set to 20.00 Hz
  76. INFO [mpu9250] gyro cutoff set to 20.00 Hz
  77. L3GD20 on SPI bus 4 at 1 (11000 KHz)
  78. LSM303D on SPI bus 4 at 2 (11000 KHz)
  79. INFO [mpu9250] Bus probed: 3
  80. MPU9250 on SPI bus 1 at 4 (1000 KHz)
  81. INFO [mpu9250] accel cutoff set to 20.00 Hz
  82. INFO [mpu9250] gyro cutoff set to 20.00 Hz
  83. WARN [ms5611] no device on bus 1
  84. MS5611_SPI on SPI bus 4 at 3 (20000 KHz)
  85. WARN [ms5611] no device on bus 4
  86. MS5611_SPI on SPI bus 1 at 3 (20000 KHz)
  87. WARN [bst] no devices found
  88. ERROR [param] Parameter UAVCAN_ENABLE not found
  89. INFO [mavlink] mode: Config, data rate: 800000 B/s on /dev/ttyACM0 @ 57600B
  90. Starting Main GPS on /dev/ttyS3
  91. Starting MAVLink on /dev/ttyS1
  92. INFO [mavlink] mode: Normal, data rate: 7200 B/s on /dev/ttyS1 @ 57600B
  93. Starting MAVLink on /dev/ttyS2
  94. INFO [mavlink] mode: Normal, data rate: 7200 B/s on /dev/ttyS2 @ 57600B
  95. Starting MAVLink on /dev/ttyS6
  96. INFO [mavlink] mode: Normal, data rate: 7200 B/s on /dev/ttyS6 @ 57600B
  97. WARN [mavlink] hardware flow control not supported
  98. FF frame selection
  99. Alta Quad selected
  100. ERROR [mavlink] offboard mission init failed (-1)
  101. px4flow [429:100]
  102. INFO [px4flow] scanning I2C buses for device..
  103. ERROR [param] Parameter UAVCAN_ENABLE not found
  104. INFO [logger] logger started (mode=all)
  105. INFO [logger] Start file log (type: full)
  106. USE IO
  107. yes
  108. ------
  109. IO PRESENT
  110. yes
  111. ERROR [logger] Can't create log buffer
  112. INFO [mavlink] mode: Custom, data rate: 5000 B/s on /dev/ttyS5 @ 57600B
  113. WARN [mavlink] hardware flow control not supported
  114. nsh: param: command not found
  115. nsh: param: command not found
  116.  
  117. NuttShell (NSH)
  118. nsh> ▒ L▒▒3*P▒ L▒▒▒▒ L▒▒▒▒L▒▒&▒ L▒▒▒N▒>
  119. iy :|v?o▒m?Y▒▒';<▒hD=N▒:▒혾▒▒▒=Su▒>ݣ▒G▒ND▒▒0B▒▒▒
  120. L▒▒▒▒
  121. L▒▒am▒ L▒▒S▒▒ L▒▒▒▒▒ L▒▒▒▒▒2▒▒>▒▒▒▒''▒▒▒▒v▒R▒▒▒▒▒▒x▒▒ ▒▒ ?▒jD▒▒
  122. QK▒▒FT`E2▒▒828338QL▒Z▒+!+ $▒@{▒$▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒@Ď▒$▒>▒▒▒▒JJkrl▒▒ L▒▒^P▒ ▒▒▒U▒ L▒▒+▒▒ L▒▒▒▒▒ L▒▒▒<▒ L▒▒v▒ L▒▒-V▒>!iΡD▒U?▒[k?n5▒▒▒#<:▒9=?猹▒▒▒▒`▒=▒k▒>ޢ▒G▒YDG▒0B▒g▒
  123. "JppD▒▒▒ #L▒▒▒▒ $L▒▒▒u▒ %L▒▒j?▒ &L▒▒X▒▒ 'L▒▒▒▒▒ (L▒▒ )L▒▒▒[▒ *L▒▒▒▒▒ +L▒▒M▒▒ ,L▒▒▒2▒ -L▒▒8x▒ .L▒▒
  124. ▒▒ /
  125. Q'▒▒F0T▒▒A▒▒828338QL▒|▒ 1L▒▒g▒P▒2+!+4"▒@▒$3▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒@▒▒▒4$▒N▒▒▒▒JJ▒▒▒>5i▒▒N▒b?▒n?▒p▒S▒;▒▒=
  126. i_<:▒Nv▒=▒p▒>\▒▒G▒_D▒▒0B▒26▒(N▒▒▒▒''▒▒▒▒v▒▒▒R▒▒▒N▒7▒▒)8▒▒▒▒9▒▒9▒ :▒▒▒ ;L▒▒▒@▒ <L▒▒r▒▒ =L▒▒▒▒▒ >L▒▒▒)▒ ?L▒▒@c▒ @L▒▒▒i▒
  127. ▒ ML▒▒▒G▒ NL▒▒▒▒FOT(▒P▒▒828338QL▒▒▒P+!+M ▒@Z▒$Q▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒@|J▒R$]▒▒▒▒JJ4▒▒▒;▒▒h<Q▒:D▒▒▒▒▒▒=t▒>]▒▒G0vD▒▒0B▒▒▒ JL▒▒H▒▒ KL▒▒▒▒▒ LL▒▒=
  128. ▒2STg]▒▒▒▒''▒▒▒▒v▒▒▒S▒▒▒▒T▒▒▒ U▒▒▒ VLQh▒P▒ XL▒▒0▒▒ YL▒▒▒▒▒ ZL▒▒▒5▒ [L▒▒ \L▒▒▒▒▒ ]L▒▒w▒▒ ^L▒▒E▒
  129. _J▒YD@▒ `L▒▒▒|▒>ai6hd▒▒>ThP?,▒▒qI<▒▒^▒▒▒▒<▒蝾▒=ڐ▒>ݣ▒G▒ND▒▒0B▒▒▒ bL▒▒C▒▒ cL▒▒▒▒▒ dL▒▒6_▒ eL▒▒▒▒ fL▒▒▒▒▒ gL▒▒▒WARN [commander] Dangerously low battery! Shutting system down
  130. ▒ hL▒▒▒;
  131.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement