Products > Test Equipment
Gw Instek GDS2204E (200MHz 4 channel DSO) review
tautech:
--- Quote from: CC555 on December 21, 2017, 07:54:41 pm ---Hello tautech,
thanks for your reply, setting a falling edge (channel 1) on both oscillocopes I get the same result.
--- End quote ---
You need to take a step back, reset to defaults and set up again with thought and not fast button bashing.
Use only the channels needed and keep the channels and Trigger position on the display.
As 2N3055 mentions the idle setting for the data stream must also be set correctly.
Take screenshots in a way to show us as much info as possible for members to best help you.
CC555:
Yes, polarity may be wrong specifying the start bit |O, thanks for your help, I am going to try.
nctnico:
--- Quote from: wraper on December 21, 2017, 08:43:42 pm ---As I remember someone wrote that he got wrong decoding on instek and fine on Rigol or maybe some other scope. Turned out that actual baud rate was off but Rigol was more tolerant to that. And after firmware update instek became more tolerant to inaccurate baud rate.
--- End quote ---
First make sure to have the latest firmware. Secondly the decoding thresholds must also be adjusted to match the signal (for each channel). Triggering doesn't matter at all.
CC555:
Latest firmware V1.32.
I have to trigger with channel 1 because I want to look the communication at that event.
Default polarity on both scopes (start bit at falling edge, 0 = high) triggering with yellow signal.
Rigol decodes right (0xFD should be)
GW
At 57600 bps (57600 8N1): 1 bit = 17.36 us, so 0xFE is wrong, the 0 (logic 1) begins at 34.2 us.
The baudrate is ok, 17.36 us * 9 (start bit + 8 data bits) = 156.24 us
the start bit is at the rising edge instead the falling edge.
1V threshold levels, what am I doing wrong? |O
Thanks
nctnico:
First of all set the polarity back to 'inverted (h=1)'.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version