Hi,
I am in the process of changing my CubeBlack to Orange.
On my Black the LightWare SF11/C was connected to serial 5.
On the Orange serial 5 is used for ADSB so how can I connect the range finder? I prefer not to cut and solder for the telem2 if I can avoid it?
Also, serial 5 used to be for debug, how it is done on the adsb carrier board?
Thanks
Gal
There is no software method to disable the ADSB on serial 5.
You need to either move your SF11/C to another port or desolder something from the carrier board.
If you really want serial 5 back, remove these 2 resistors to disconnect the ADSB:
Hi @Alvin, thanks for this.
I wouldn’t touch my board.
I shall use telem2.
Gal
Remember that you have also GPS2 port which can be Serial4.
Wow, this is definitely something I didn’t know.
Great solution, especially in my case where both gps are on I2C
Thank you
I see this was from 2020, but I assume the method above with removing the two resistors restores access to the Serial 5 UART from the CONS pins and disables the ADSB. Can anyone confirm if this has worked for them?
Hi @Alvin
Does this method of restoring serial5 currently work? It doesnt appear to. is there anything else that needs to be done to access serial5 through the CONS pins?
@Star-2033 have you configured SERIAL parameters accordingly as well. Which device are you trying to connect and how? Have you run out of serial ports. There are total 4 standard Serial ports available on standard carrier board.
Hi @sidbh,
Yes, I have tried configuring the serial 5 to different settings, then connected to a TTL - USB converter to debug on a terminal. I set serial 5 to NMEA-output, but unfortunately the CONS pins do not seem to output any data. Yes, I have used all 4 ports in my application. The only other option would be to deploy a board with AP_Periph, but that seems overly complex. It would be the best solution to get serial 5 working. Is there any reason why it wouldn’t work after removing the resistors? Does it need a full reset/firmware reload?
Thanks!
@Star-2033 can you test if you can get MAVLink on the serial port by setting SERIAL5_PROTOCOL to 2 and SERIAL5_BAUD 57600.
@sidbh that’s a good idea, and something that I hadn’t tried. Thanks! I just ran a test now with the setting you suggested, but unfortunately i still see no activity on the port. Mission planner times out when attempting the connection.
And you have verified that serial to uart converter is functional, simply by connecting say telemetry port?
Yes, I have had it connected to other ports (TELEM2) on the board to connect MP to the board and it is functioning. I just redid the test to be sure, and the TTL converter is working.
Can you share images of connections.
@Star-2033 those pins actually don’t go anywhere in ADSB Standard Carrier Board. To access the Serial 5 you need to open the Carrier board and use the FMU DEBUG pin which are present at the bottom here:
I will update the documentation to avoid confusion in the future.
Thank you @sidbh That is very helpful! Can you provide the pinouts and the type of connector used on that port? I looked through the documentation and I couldn’t see a reference to these internal ports.
Thanks!
@Star-2033 the connector type is SM06B-SURS-TF(LF)(SN)-ND . The pinout is FMU DEBUG on this link The Cube Module Overview | CubePilot
