Josh52

Hi @attila, thanks for your fast response! The documentation bug explains the LV -> WaveForms Protocol parity error, but I also get a parity error while transmitting and receiving on the same AD2 via LabVIEW: I'm using the DWF SDK functions F Dwf Digital Uart Tx.vi and F Dwf Digital Uart Rx.vi with Pin 0 and 1 connected via Jumper. It doesn't matter if I use odd or even parity - I always get a parity Error on the first character: "Parity error on index 1" I build the Check RX errors function also according to the reference manual part 12.1 where pParity in FDwfDigitalUartRx is described as follows: I can't understand, why this parity error keeps showing up, because the parity is set only once for TX and RX. I'll be happy about any help or suggestions!

Hi there, I'm using an AD2 with LabView and the WF SDK for UART communication. Initialization of the AD2 and UART RX works fine. Data bits and stopp bits setup works and these are also transmitted correctly. But I'm always getting a wrong / inverted parity bit on my TX channel while using WF SDK in LabView: If I set ODD parity my LabView RX-programm and the WaveForms Protocol on an other AD2 return a parity error. If I set EVEN parity in my LV TX-programm and odd parity in the WafeForms Protocol I receive no parity error. The problem doesn't emerge when using the WaveForms Protocol Desktop Application for TX too. I've used a second AD2 with WaveForms scope to check the output of the first AD2 running WF SDK in LabView. (See screenshot) Also I've exchanged both AD2 for each other, switched pins, changed the UART config in LabView (according to the reference manual part 12.1) without success. Am I missing something in the configuration (screenshot 2) or is it a bug? Best regards Josh