JYE Tech Forum

Well, yeah, there was this whole FTDIgate thing when ftdi released an updated driver which would brick counterfeit chips. I don't know if this was ever resolved, maybe your chip had that sad fate and is useless now. cp2102 series have no such issues, although sadly only support 3.3v ttl levels. Did ...

You probably didn't put the scope in bootloader mode. Make sure that you have good solder joins on the jumpers, when you turn it on the screen should be just blank white. Also don't connect the power, only gnd, tx and rx. I powered the scope on it's own. The ftdi board I used was this one, it has 3....

I used FTDI FT232RL based adapter which also worked just fine.

I'm assuming you use windows, there are no issues with these uart to usb converters on a proper OS :P Try just connecting your cp2102 device, without hooking it up to the scope. You should be able to see a com port appear in your device manager. If you don't see it you need to install drivers: http:...

I like this little scope for it can be a great tool for low frequency work. Biggest selling point to use it over the big proper scope is that it is small and portable. Except it's not quite portable if you also need to carry a power source and look for an outlet, now is it? Well I decided to fix tha...

I just flashed 055 and none of the problems mentioned by the nitroburn are present. For me this firmware is strictly an improvement, although there are still issues which I experienced with old firmware as well. Namely scrolling with the encoder is very slow and obviously misses some ticks. This app...

jye1 Ok, that explains why frequency is not counted but not why the trace is flat and Vpp and other measurements are showing wrong values. EDIT: Wait, no that doesn't explain the frequency counter either. How come on a lower sensitivity 0.1v is enough to pass the threshold and trigger the counter bu...

@jye1
But that is wrong, there obviously is a 1khz 0.1v signal with dc offset on the input. It shouldn't show 0 khz.

@jye1 But it doesn't always turn red. If you follow Macross' second video closely at 0:48 the scope shows a flat trace near the middle of the screen and Vpp is 0.01v (within noise margin), which is very misleading. https://www.youtube.com/watch?v=Q2SjAiwbBlE That is the exact situation that I would ...

jye1
That is great, thanks!
Can we also fix the issue with wrong values displayed when the input doesn't fit on screen? Preferably the trace should disappear as well.