Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HUBOSD8-SE no comms to OSD
#1
I am about to bring out the hammer with this one. 

I have 2x HUBOSD8-SE. 

HUBOSD8-SE #1
- 5V BEC failed
- Nothing soldered onto the board. Only power via XT60.
- Can successfully update OSD using STOSD Tool. (firmware and settings)
- I replaced it with #2 due to the 5V failure. 

HUBOSD8-SE #2
- ESC's and XT60 soldered onto the board.
- Cannot connect to OSD or update firmware using STOSD Tool.
- Connect error: "Read Settings Timeout"
- Firmware flash error: "Waiting OSD Response"

I've tried every baud rate, without success. One works fine, the other doesn't. I've checked continuity between OSD processor and the RX/TX pins and they are good. 

(I'm using an Arduino UNO in "Serial Mode" for comms)

Any ideas?
If my post helped you...hit the RATE button.
Reply
Login to remove this ad | Register Here
#2
I think...


Attached Files Thumbnail(s)
   
Reply
#3
So the hammer is out. It seems there is a problem in the circuit. The moment I connect the pins, both TX and RX LED's on my TTL light up. Testing continuity between RX and TX do not produce a beep, but produce a reading of about 1500ohm. The board I can successfully flash has no reading when doing the same test and both RX and TX LED's remain off on initial connection.
If my post helped you...hit the RATE button.
Reply
#4
I fixed it!!! Took a bit of research and a cowboy approach, but it is working now. Yeehaaaw!!!

I'm not EXACTLY sure how my actions solved the problem, but I'm sure unseen will be able to explain it to me. I shorted a pad to ground, some lights flashed and stuff started working.

It is 12:07am here and I need to get some sleep. Will do a writeup with some photos tomorrow....ummm...later.
If my post helped you...hit the RATE button.
[-] The following 1 user Likes xcalibur's post:
  • Tom BD Bad
Reply
#5
Hooray! You might not be able to tell from the font, but I'm doing the running man! Caint touch this...
Windless fields and smokeless builds
[-] The following 1 user Likes Tom BD Bad's post:
  • xcalibur
Reply
#6
(03-Feb-2018, 05:27 AM)Tom BD Bad Wrote: Hooray! You might not be able to tell from the font, but I'm doing the running man! Caint touch this...

Thanks Tom!! I was on the verge of ordering a new PDB.
If my post helped you...hit the RATE button.
Reply
#7
Long story short, I had no comms via RX/TX to the OSD via the STOSD Tool. No device and/or baud rate would establish a successful connection. Not even when trying to force-flash the OSD in bootloader mode. 

THE FIX

Flashing LED: Initializing 
Solid LED: Running

I briefly grounded the pin shown in the attached image. This caused the always-solid blue LED to turn off briefly and return flashing. (On every subsequent reboot, for testing, the LED now remained flashing instead of turning solid)

I then attempted a normal connect / firmware flash with the STOSD Tool and SUCCESS!! Everything is now running brilliantly, except for my RSSI value not showing up from the X4R-SB. (Still need to figure this one out)

I would like someone (unseen?) to explain to me exactly what it was I did by grounding that pad. What did this do to fix the problem? 

   
If my post helped you...hit the RATE button.
Reply
#8
I having issues with this board. Anyone know why the osd is only showing voltage but current will not move from all zeros? Is there something I’m missing? Firmware has been updated via serial passthrough . I’m running 4 in1 esc’s with power leads soldered onto the battery pads .

What needs to be done to get current readout on the osd?
Reply
#9
As far as I know, you will only get current readings if you draw current from the esc pads on the board. The current sensor can only measure current flowing through it. If you are drawing power directly from the battery pads there is no current flowing through the board to measure.
If my post helped you...hit the RATE button.
Reply
#10
(06-Feb-2018, 07:29 AM)xcalibur Wrote: As far as I know, you will only get current readings if you draw current from the esc pads on the board. The current sensor can only measure current flowing through it. If you are drawing power directly from the battery pads there is no current flowing through the board to measure.

That’s the conclusion I was coming down to. Oh well I guess I’ll save it for another build . Now if there was a way to turn off the current and timer in osd I’d be good. Seems like the stosd tool doesn’t give you many options. Thanks for the input.
Reply
#11
(07-Feb-2018, 07:16 AM)maseffect Wrote: That’s the conclusion I was coming down to. Oh well I guess I’ll save it for another build . Now if there was a way to turn off the current and timer in osd I’d be good. Seems like the stosd tool doesn’t give you many options. Thanks for the input.

The tool is pretty limited. There must be a way to run some other firmware on that chip. I just have not found it yet.
If my post helped you...hit the RATE button.
Reply
#12
(03-Feb-2018, 07:19 PM)xcalibur Wrote: I would like someone (unseen?) to explain to me exactly what it was I did by grounding that pad. What did this do to fix the problem? 

I'd love to help, but I don't have one of these and I've never used one, so that's why I've been silent.

The row of four pins most likely go to the OSD's microcontroller. I'd suspect they are what is used at the factory to flash the MCU. The pin you shorted to ground probably goes to the MCU's reset pin.

Somehow, resetting the MCU allowed you to get the board into bootloader mode and update the firmware.
Reply
#13
(07-Feb-2018, 10:57 AM)unseen Wrote: I'd love to help, but I don't have one of these and I've never used one, so that's why I've been silent.

The row of four pins most likely go to the OSD's microcontroller. I'd suspect they are what is used at the factory to flash the MCU. The pin you shorted to ground probably goes to the MCU's reset pin.

Somehow, resetting the MCU allowed you to get the board into bootloader mode and update the firmware.

Fair explanation that makes sense. Thanks Unseen!
If my post helped you...hit the RATE button.
[-] The following 1 user Likes xcalibur's post:
  • unseen
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Is Betaflight telling me no OSD? husafreak 2 251 09-Dec-2023, 12:59 AM
Last Post: husafreak
  Lost OSD question Rob Axel 1 431 05-Aug-2021, 06:16 PM
Last Post: SnowLeopardFPV
  No OSD After Crash Opatry 23 4,908 12-Mar-2021, 10:57 AM
Last Post: woja
  No OSD in googles Mightywren 7 1,725 29-Dec-2020, 10:17 AM
Last Post: Banelle
  Is My OSD Chip Failing? the.ronin 7 1,297 20-Aug-2020, 03:23 PM
Last Post: the.ronin


Login to remove this ad | Register Here