Communication through J18
-
@Eric-Katzfey No worries, and yes that's it. How would you recommend I communicate with that external Teensy board? Can't seem to find easily accessible pins for that.
@Filip-Slezak-0 I would go with that expansion board I pointed out and use UART.
-
@Filip-Slezak-0 I would go with that expansion board I pointed out and use UART.
@Eric-Katzfey Sorry for the late reply. Unfortunately, I don't see how that could work for us, we already have the m0078 on there and the J2 goes to the wifi dongle, what am I missing in what you're suggesting?
-
@Eric-Katzfey Sorry for the late reply. Unfortunately, I don't see how that could work for us, we already have the m0078 on there and the J2 goes to the wifi dongle, what am I missing in what you're suggesting?
@Filip-Slezak-0 The board I am suggesting has USB and UART.
-
@Filip-Slezak-0 The board I am suggesting has USB and UART.
@Eric-Katzfey So you're thinking switch out the boards, use the UART for the wifi dongle and communicate over USB with the microcontroller?
-
@Eric-Katzfey So you're thinking switch out the boards, use the UART for the wifi dongle and communicate over USB with the microcontroller?
@Filip-Slezak-0 No, keep using USB for the WiFi dongle and use the UART to communicate with the Teensy.
-
@Filip-Slezak-0 No, keep using USB for the WiFi dongle and use the UART to communicate with the Teensy.
@Eric-Katzfey Got it, this is getting clearer. Is it safe to use the Teensy's 3.3V pins? According to this, the Voxl2 comm pins are at 1.8V even though its GPIOs are at 3.3V https://docs.modalai.com/voxl2-linux-user-guide/#devttyhs1---b2b-connector-uart
-
@Eric-Katzfey Got it, this is getting clearer. Is it safe to use the Teensy's 3.3V pins? According to this, the Voxl2 comm pins are at 1.8V even though its GPIOs are at 3.3V https://docs.modalai.com/voxl2-linux-user-guide/#devttyhs1---b2b-connector-uart
@Filip-Slezak-0 Yes, should be fine. We use that UART to connect with our external flight core boards that have 3.3V rx / tx.
-
@Filip-Slezak-0 Yes, should be fine. We use that UART to connect with our external flight core boards that have 3.3V rx / tx.
@Eric-Katzfey Thanks Eric, got it working easily after that using a classic pyserial script. Great help!
-
@Eric-Katzfey Hi again, can we expose another UART port for programming on the Voxl2?
-
@Eric-Katzfey Hi again, can we expose another UART port for programming on the Voxl2?
@Filip-Slezak-0 Thinking about ttyHS2 or ttyHS3 maybe shown here https://docs.modalai.com/voxl2-linux-user-guide/#uarts
-
@Filip-Slezak-0 Thinking about ttyHS2 or ttyHS3 maybe shown here https://docs.modalai.com/voxl2-linux-user-guide/#uarts
@Filip-Slezak-0 please see here: https://docs.modalai.com/voxl2-linux-user-guide/#apps-proc, we have ttySH2/ttyHS3 routed to the B2B connectors, but you need a carrier board to pick them up...
For example, ttyHS2 goes to our
M0090 - 5G Add-On Board J9 Pins 2/3 (Tx/Rx)
-
@Filip-Slezak-0 please see here: https://docs.modalai.com/voxl2-linux-user-guide/#apps-proc, we have ttySH2/ttyHS3 routed to the B2B connectors, but you need a carrier board to pick them up...
For example, ttyHS2 goes to our
M0090 - 5G Add-On Board J9 Pins 2/3 (Tx/Rx)@modaltb Hey, thanks for the quick reply. Unfortunately, none of these work for us since it seems exposing one port prevents us from accessing another (I also can't find a ref to buy the M0130).
We found a workaround by having a USB hub on the m0125 instead of going over the native uart.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login