Running into an issue using a Teensy 4.0 as a replacement for the 3.2.
I'm using a Teensy 4.0 along with a 900Mhz XBee XSC S3B module to remotely communicate with some other equipment. Due to space constraints the Xbee and Teensy are located inside a small plastic enclosure in relatively close proximity to each other, but on opposite sides of the PCB with a ground plane in between. I've used this exact setup for years with the Teensy 3.2 with no issues (slight tweak to the PCB due to the slight difference in RX2/TX2 pins).
Teensy and radio communicate on Serial2 @ 57600baud, and the Xbee has it's own 3V reg. The wire antenna is routed exactly the same as before, away from the microcontroller and other circuitry.
For some reason, when the XBee transmits I'm picking up a lot of garbage 'incoming' data in the Serial2 RX pin. I've taken steps to mostly ignore this data via software tricks but would like to get to the root of the problem. Changing the baud rate seems to help a little, but the problem remains across all baud rates that I've tried.
Any ideas why the 4.0 might be more sensitive to this than the 3.2 and any steps I could take to try to fix it? RF stuff is kind of voodoo magic to me so any help is appreciated.
Thanks
I'm using a Teensy 4.0 along with a 900Mhz XBee XSC S3B module to remotely communicate with some other equipment. Due to space constraints the Xbee and Teensy are located inside a small plastic enclosure in relatively close proximity to each other, but on opposite sides of the PCB with a ground plane in between. I've used this exact setup for years with the Teensy 3.2 with no issues (slight tweak to the PCB due to the slight difference in RX2/TX2 pins).
Teensy and radio communicate on Serial2 @ 57600baud, and the Xbee has it's own 3V reg. The wire antenna is routed exactly the same as before, away from the microcontroller and other circuitry.
For some reason, when the XBee transmits I'm picking up a lot of garbage 'incoming' data in the Serial2 RX pin. I've taken steps to mostly ignore this data via software tricks but would like to get to the root of the problem. Changing the baud rate seems to help a little, but the problem remains across all baud rates that I've tried.
Any ideas why the 4.0 might be more sensitive to this than the 3.2 and any steps I could take to try to fix it? RF stuff is kind of voodoo magic to me so any help is appreciated.
Thanks