JYETECH scope

currently it displays the bootloader and then it displays messed up graphics and freezes.
atleast it’s not dead as i thought awhile ago…

both optical check and a multimeter at the continuety test function.

looks like not many things left to try… but since the faulty part is not obvious then which component i should request?! my opinion is that something is wrong either with the mcu or the display… maybe the display has an internal bad contact somewhere?! or the mcu is not functioning well? :unamused: :unamused:

Did you mean every time the bootloader runs at powering up (i.e. displays correct version screen) and messy screen appears after (as bootloader exits)? If this is the case then one possible cause is the main program has corrupted. If you know how to program the chip and you have the right tool available I suggest you try to reflash the codes. For this design because there is a bootloader codes inside the chip could be accidently written over if strong disturbances occur at the time when bootloader is running at powering up. We did see a couple of such cases where scopes hung at bootloader screen. After reflashing codes the problem was gone.

yes!

i have received an e-mail from Mr Liu, i believe he is the designer of the oscilloscope?

he let me know that in case i’m unable to troubleshoot the oscilloscope with the assistance i’m already receiving, then i can return it back and if it is a quality issue they will reimbruse the shipping cost and no matter the result of inspection i should receive a replacement kit…

i would like to thank him for his support and for this really really kind offer of his…

so today before i take any decision to return it back i tried whatever possible from my side so i can repair it and avoid the returning, in a desperate try i have replaced almost any IC i could replace just in case that something is not working right and might somehow interfere with the rest of the circuit… specifically i changed the two op-amps ne5532 and tl084 the second one got replaced with a tl074 which is a better device with low noise, also if i was able to re-program the atmega64 i would do that too but i don’t have
the needed tools to do that!!!

the outcome…

it might be suprizing…but now the instrument always turns on and has an output shown at the display no matter how many times i turn it off and on…(though a couple of times the letters faded after awhile and i could only see the backlight) now what it shows is the bootloader and then it freezes! when i measure the voltages around the PCB i’m not getting the ones indicated by the troubleshooting guide. so what i have done? changing those ICs was a bad idea?!

update…

i’m building a simple serial level converter so i can try to re-program the atmega64 in case the
problem is a corrupted firmware…

if someone also wants to build one somebody gave this link and it’s very helpful.
picprojects.org.uk/projects/simpleSIO/ssio.htm

here’s a photo of my serial level converter…
serial_level.jpg

Hi

using a utility called tera term as you can see in the photos the oscilloscope responds…

but when trying to re-program it using the avrvbd initially it connects and then i
get a time out error.

i think the story went too far…so i stop my tries right here.

sorry if it were annoying all these posts i did and all these photos i uploaded but
i really wanted to find a sollution to the problem since it’s the only oscilloscope i got
and i need it for my audio projects.
avrubd.jpg
teraterm.jpg

Click on Option -> System, and change “maximun connect cout” to large number like 50 or 100. This will increase connect time. The default was 10, which is too short. You don’t have enough time to power up the scope. General steps: click “Dn” icon first. AVRUBD will start sending connect character “$64”. Then quickly power up oscilloscope. If the bootloader in scope receives 10 $64 characters connection will be established and downloading will start.

Sorry my mistake. 5 instead of 10 consecutive ‘$64’ characters need to be received correctly by the bootloader before a download can be started.

Hello.
madworm, you’re having trouble with hanging up the oscilloscope?
I have a similar problem, after a certain time oscilloscope hangs, works only click OK. After turning off the power and the oscilloscope is running, but instead labels SEC / DIV shows funky characters. As it turned out changing the contents of eeprom. After flashing eeprom again everything is normal.

Apologize for the bad English, I write through the translator.

firmware 113-06201-091 is out. Thanks JYE for the update.

That seems a good solution and looks useful.

But as I said long before, is there a way to use one of the top indicators of
the display to differenciate a snapshot from a live view ? And in general, how about using
those top indicators to let the user know a lot of think (signal traffic, wait state, i/o transfer, …)

Hello.
The problem itself has disappeared after I programmed the chip through a bootloader.

Thank you!

I bought a Digital Storage Oscilloscope with Panels DIY KIT (SMD pre-soldered), has collected, including not working, heats 7805, smoke from L3, short C8 replaced.
On again does not work on 7805 2.4 volts, a little later puffed L4, strongly bask 7805 and TLC5510. He took off his TLC 5510 - Oscilloscope involved.
Apparently defective TLC5510???
Who is not something encountered this problem?
What do I do? Buy TLC 5510I where I live is unreal: (

If components are believed defective please contact JYE Tech at [email protected]. JYE Tech provides free replacement for all proved defective parts.

Can JYE provide just the panels to Seeedstudio? I tried to order just a panel, I bought a scope from you directly when Seeedstudio didn’t have them yet.

Dear CrashingDutchman, can you please contact me at [email protected]? I should have your emails but they are buried deep in my mailbox and I can’t identify which are yours. We would like to send you a free panel kit as thanks to your vuluable support at the early days of the 062 oscilloscopes.

Sorry for replying late. I didn’t come to this forum often since the thread was not updated for long time. For any issues regarding to the scope users will get faster responses if posting to the JYE Tech Oscilloscopes [email protected] or write to [email protected] directly.

Dear mr. Liu,

I just sent you an email with my details. I appreciate you are going to send me a free panel and want to thank you for that in advance. I am glad to hear that my support was valuable.

Hi, just “playing” some time with the scope.
Now, with latest firmware (113-06201-092) seems to be OK (as voltage adapter used one old USB cable for Nokia 3510i, with
Prolific PL2303 chip - perfect job)
Make some tests/mods to reduce at maximum the power consumption for portable use.

  1. Desolder the backlight resistor (R23 - 0 ohm).
  2. Test some ideas to generate the AV- voltage (MAX7660 and others), but not big improvement, revert to original.
  3. Replaced the LM7805 with other low-drop 5V regulator (found in my “archive” one L487).
    Now it is possible to operae the scope even if power supply is 5.4 Vdc!
    My plan is to use the scope with NiMH batteries (5x 2500mAh, Energizer AA size)
    Total consumption is now approx. 100mA
  4. Using one old scope probe, found that a 2.2pF capacitor between pin 5 of U2B-TL084 was the proper compensation for
    input without attenuator.
    Still working for display of Vpos marker and trace line at same level (if replaced the L4 coil with 10-30 ohm, at middle screen is OK,
    but at lowest/highest positions, the trace is 3-4 lines behind VPOS marker). I will try to alter the value of R3, but for the moment
    no time available.

Forgot to ask: how to obtain a stable trace at 2uS/div?
The trace is unstable, regardless trigger position, mode (somewhere found that only AUTO is the mode for 2uS/div).

Thanks

Hello i recntly bougth a dso oscilloscope and as soon as i first turned it on, doesn´t work the lcd screen lits on but only shows th pixels in black with the icons on the top also appearing but not launch the firmware, is there a problem with the contrast or the firmware ?

This thread is not about the DSO scope. Please start your own thread, for better support reasons.