Below is an issue I’m having with RTS/CTS on the G400. Hopefully its formatted well enough to be a quick read. Hopefully someone already knows the answer?
Project:
I’m using COM2 (Gadgeteer port 4 on Raptor) for a serial application with flow control.
Issue:
But, it seems that the RTS signal coming from the G400 is always high.
Testing
USE COM2 with and without flow control. You will notice that RTS (PA2) is always high.
Expectation:
It should go low when the module is ready for data (signalling that it’s “clear to send” to the other device).
Its also worth mentioning that, as it stands, the RTS should not be connected. Watch out when you make your PCBs:)
Reason being is, since the signal is always HIGH, your device will not respond unless you pull the signal LOW by way of a jumper or cutting traces on the board.
@ rbrainard - I feel your pain, the IoT Labs WiFi module does not work with the Raptor for this exact reason. I’d like to hear from GHI on when this will be corrected.
@ munderhill…guess I should have read your release notes too! I happen to have a Raptor and just bought your module. It’s no big deal though…no worries.
@ leforban - Handshaking does not work at all on the G400 in the current release, neither CTS nor RTS on any COM port. You should be able to use them as I/Os.
Hi John, do you have an issue tracker? It might help put people at ease if they can see that these issues are being cataloged and scheduled for specific releases.
@ John - It is the Hydra+ and if you are not going to support handshaking then socket 6 needs to have the ‘K’ removed from the silkscreen and the specifications need to be updated (Socket ‘K’ removed).
@ munderhill - The Hydra+ and FEZ Hydra run the same firmware so this applies to both. The specifications tab has been updated to reflect the lack of K support.