| Products > Test Equipment |
| True analog scopes |
| << < (34/84) > >> |
| vk6zgo:
--- Quote from: tggzzz on December 18, 2022, 12:46:47 am --- --- Quote from: vk6zgo on December 18, 2022, 12:07:25 am --- --- Quote from: tggzzz on December 17, 2022, 09:24:33 am --- --- Quote from: tautech on December 17, 2022, 06:43:19 am --- --- Quote from: H713 on December 17, 2022, 06:14:00 am --- --- Quote from: tautech on December 16, 2022, 07:36:59 pm ---With that vast experience what do you recommend for 1. The hobbyist with little or no scope experience ? 2. The young professional, say the EE student with limited resources ? --- End quote --- In both cases, it depends on what you can get. --- End quote --- Are you living in the same world as the rest of us ? In 2 weeks I can something from anywhere in the world......1 week from China. It's not about what you can get but instead the best instrument for today's and future use....they are not expensive. The hobbyist might pick some CRO boat anchor use in their twilight years however to advise the EE's of tomorrow to get one is just downright irresponsible. --- End quote --- No, it is not irresponsible. I will leave others to comment on whether a Siglent scope salesman is being "responsible" when they say that, or whether there is some other motivation. One of the best definitions of an engineer is "someone that can do for £1 what any fool can do for £10". Frequently during a professional career people will have to make do with what's already available because * you need it now, not in a month's time * money has to be used for other necessary equipment * it won't pass the purchase request process * it is back at base, not here in the field * boss says you don't need it * there is nothing that is capable of doing the jobI've seen all of those, and had to find workarounds. Might as well get engineers to think creatively from the outset. That's not true for technicians, of course - and vive la différence! --- End quote --- Funny, my experience has been the opposite. Engineers tend to have "tunnel vision"----they decide some particular thing is the problem, & doggedly pursue that, even to the point of redesigning perfectly functional equipment. Techs have the advantage of working on multiple pieces of equipment from varying manufacturers over time & can often "zero in" on a problem by comparing how manufacturers of various devices do things. --- End quote --- I've designed low noise analogue electronics, digital, semi-custom, micros, protocols, hard realtime software, soft realtime software, data analysis software. I have avoided databases (except to replace them with something less overweight), and haven't done much RF. One problem is the same for techs, engineers, accountants, lawyers, clerks etc. Do you have "10 years experience" or "1 years experience repeated 10 times". --- End quote --- Maybe I have been fortunate in working during a period in which Electronics Techs have had to learn new technology "on the run", from Tubes to microprocessors & beyond. The interesting thing is that you can't let yourself forget the "old stuff" because it still exists out there, along with the "latest & greatest", & will come back & "bite you on the bum" if you aren't careful. We have all worked with the "1 years experience repeated 10 times" people----somehow, they manage to float through life without their "feet of clay" being found out. I do think they are less common amongst EEs & techs, than in the other groups you mention. --- Quote --- --- Quote ---Of course, this is you have real technicians, not the "monkey see, monkey do" trained poor substitutes sadly so common today. --- End quote --- Ditto engineers :( --- End quote --- |
| tggzzz:
--- Quote from: vk6zgo on December 18, 2022, 01:02:09 am ---Maybe I have been fortunate in working during a period in which Electronics Techs have had to learn new technology "on the run", from Tubes to microprocessors & beyond. --- End quote --- Yes and no. Yes: I'm not sure about the future, but nowadays I would probably choose the life sciences for a career. No: when I returned to real-time embedded electronics, it was still 8-bit micros programmed in C. No change in 35-40 years :( Well, smaller, faster, cheaper, but that's only a change in degree, not in kind. The main things that have changed are nanopower and ADC/DAC speed/resolution. No: there was precisely one tech course I ever attended (on AI in the mid-80s). The rest of the time there were no courses since they could only be in the future :) Was I lucky or fortunate? Yes, but to some extent I made my luck and grasped chances. I explicitly took one of Frank Herbert's concepts to heart:“And always, he fought the temptation to choose a clear, safe course, warning 'That path leads ever down into stagnation.” --- Quote ---The interesting thing is that you can't let yourself forget the "old stuff" because it still exists out there, along with the "latest & greatest", & will come back & "bite you on the bum" if you aren't careful. --- End quote --- The fundamentals haven't changed, but there is an awful lot of here-today-gone-tomorrow faddish stuff that is best avoided. Too many people don't distinguish between the two: some hop onto and evangelise every fad (especially in computer languages and frameworks), some refuse to conceive that stuff taught at university is critically important to today's choices. |
| Wallace Gasiewicz:
Tautec: When I switch from say, 30 MHx down to 1 KHz, I sometimes do not get a trace until I push the autoscope function. On an analog scope all I had to do was to change the time base dial. Not a big deal now that I know what to do. |
| 2N3055:
--- Quote from: Wallace Gasiewicz on December 18, 2022, 11:58:42 am ---Tautec: When I switch from say, 30 MHx down to 1 KHz, I sometimes do not get a trace until I push the autoscope function. On an analog scope all I had to do was to change the time base dial. Not a big deal now that I know what to do. --- End quote --- I have no idea why is that. I assure you that modern low cost scopes from Siglent, Rigol and Micsig (or even noname brands) function perfectly and no such problems exist. This whole topic steered so away from original question. |
| Mechatrommer:
--- Quote from: Wallace Gasiewicz on December 18, 2022, 11:58:42 am ---When I switch from say, 30 MHx down to 1 KHz, I sometimes do not get a trace until I push the autoscope function. On an analog scope all I had to do was to change the time base dial. Not a big deal now that I know what to do. --- End quote --- i suspect you are on "Normal" triggering mode (which is i suspect unavailable in CRO), you can change to "Auto" triggering mode and you still can see a flat horizontal line if signal is too slow. you can rest assured that we still have that time base dial on DSO to do the same... |
| Navigation |
| Message Index |
| Next page |
| Previous page |