| Products > Test Equipment |
| New bench scope - Fnirsi 1014D, 7", 1GSa/s |
| << < (62/67) > >> |
| Harrow:
Hi all, I just joined the FRISNI 1014D club today. Found one for under $200 AUD on eBay, so it will tide me over until the SDS814X makes it to our shores. I can understand why so many people love to hate it, but I'm already quite fond of it. I understand its limitations, which is why I plan on getting something better, but for what it is, I think it's pretty good. I find the controls and layout quite intuitive, and while it won't be up to scratch for detailed design, it's certainly handy for basic diagnostics and hobby tinkering. I like the idea of being able to take it anywhere and run it off a power pack. I think the trigger level encoder is already playing up a little after two days, lol, but I expected as much at this price level. It will be like owning a Triumph. ;-) |
| Atlan:
Hantek is close to this price level, and it can already be called an oscilloscope. |
| csuhi17:
--- Quote from: bunaziua on March 04, 2024, 12:17:13 am ---I got the scope recently, needed something portable to find why my car did not want to run. In my use case I found 2 areas lacking: 1)If you use a wide time band (ex. 100ms per division) it will miss a lot of data. Theoretically it could capture the data (with a supposed 1GSa/s) , but seems like the limitation is in the sample memory (supposedly 240 Kbit). When the trigger hits, the oscilloscope captures 30 time divisions. With one sample supposedly 8 bits, you get 30K samples over 30 divisions, so 1K samples per division. But I really doubt it's 1K samples per division, and I am a beginner with oscilloscopes so not sure if I have correct assumptions. So if you don't know what the frequency of the signal will be, you might miss some important details if you use too wide of a time division. 2) The trigger behavior seems odd. I used a Rigol DS5102CA before, and the trigger was intuitive. With the FNIRSI it seems odd and I didn't use it enough to say what is wrong, but it feels like it's not a good implementation. What I chose to buy it: In my area you can't find a good oscilloscope for a decent price. I needed a portable scope, and with all the drawbacks this one is the best option. If I would be in the North America I would get the Rigol DHO802 for 330$ and not waste my money on the FNIRSI. But I am in eastern europe and the DHO802 is 415 euro, and I have to also add 20% customs VAT (and potentially shipping), so that makes it 500+ euro. So the 130 euro FNIRSI it is. It's not something you can confidently use if you need it for serious/responsible work (at least that is my opinion), but for a lot of use cases it gets the job done. --- End quote --- Are you sure about that? that 1Gs/s is the real sampling?! Based on tests, the oscilloscope corresponds to a maximum of 30 Mhz. I tried what you wrote with the 1013D with its factory firmware. I gave it a 51Khz square signal, with a 100ms time base, then stopped it, then tried to zoom in on it, but it wouldn't let me. When I set the trigger to Single, the time base was automatically set to 10mS. I don't know what other people's experience with this device is, but I don't think it will be suitable for what you want. I quickly tested it with my Micsig. I can't upload a picture now because I have to go to work, maybe tomorrow if you're interested. I gave a 51Khz square signal to both. My Micsig memory is limited to 28k. The time base is 10ms, because only then does Fnirsi allow me to zoom in on the stopped wave. The difference between the two waves is heaven and earth. On my Micsig, the whole wave is continuous, and I have to zoom in even more to see the waveform. Fnirsin is worthless in comparison. So does Fnirsi use much less memory? Maybe you would be better off with a Hantek 1112. Although there are many complaints about that. |
| pcprogrammer:
Both the 1013D and 1014D only use a small amount of the available memory in the FPGA to store the samples. In the software it even uses less depending on the time base setting. Only on the shortest times per division does it use both ADC's per channel with the related storage. For the rest of the settings it uses only half the storage space and in the roll mode it only stores a single display. We are talking max 1500 or 3000 samples per channel. The 1014D FPGA configuration is for the most part the same as for the 1013D. I almost fully reverse engineered the one for the 1013D and looked at the one for the 1014D to find matching parts. The basic conclusion is that the design is crap and only ok for simple hobby use. The original firmware polishes the signal to make it look good, but it is utter crap. The new firmware for the 1013D improves things quite a bit especially now that Atlan took over to tweak things and implement the parts I skipped. Unfortunately for some it can't be used on the 1014D. Efforts on porting it seem to have stopped. |
| bunaziua:
--- Quote from: Atlan on March 04, 2024, 07:28:17 am ---Why didn't you buy the 1013D, it's actually a portable version of the 1014D. --- End quote --- I got what was available locally since I didn't want to wait for shipping from china. And I like the knobs more than touch screen, and the fact that you can use it with a power bank instead of a integrated battery that might go bad after some years. --- Quote from: csuhi17 on March 04, 2024, 11:35:48 am ---Are you sure about that? that 1Gs/s is the real sampling?! Based on tests, the oscilloscope corresponds to a maximum of 30 Mhz. --- End quote --- I know that the specs are exaggerated, like usual chinese cheap stuff --- Quote from: csuhi17 on March 04, 2024, 11:35:48 am ---I tried what you wrote with the 1013D with its factory firmware. I gave it a 51Khz square signal, with a 100ms time base, then stopped it, then tried to zoom in on it, but it wouldn't let me. When I set the trigger to Single, the time base was automatically set to 10mS. --- End quote --- This might be one of the reasons the trigger seemed so bad, will test it later and post the findings. --- Quote from: csuhi17 on March 04, 2024, 11:35:48 am ---I quickly tested it with my Micsig. I can't upload a picture now because I have to go to work, maybe tomorrow if you're interested. I gave a 51Khz square signal to both. My Micsig memory is limited to 28k. The time base is 10ms, because only then does Fnirsi allow me to zoom in on the stopped wave. The difference between the two waves is heaven and earth. On my Micsig, the whole wave is continuous, and I have to zoom in even more to see the waveform. Fnirsin is worthless in comparison. --- End quote --- Haha, I believe you, FNIRSI seems to capture so little data --- Quote from: csuhi17 on March 04, 2024, 11:35:48 am ---Maybe you would be better off with a Hantek 1112. Although there are many complaints about that. --- End quote --- The specs look better than the FNIRSI regarding sample memory will look into the Hantek 1112, if it is indeed good. --- Quote from: pcprogrammer on March 04, 2024, 12:17:47 pm ---Both the 1013D and 1014D only use a small amount of the available memory in the FPGA to store the samples. In the software it even uses less depending on the time base setting. Only on the shortest times per division does it use both ADC's per channel with the related storage. For the rest of the settings it uses only half the storage space and in the roll mode it only stores a single display. We are talking max 1500 or 3000 samples per channel. The 1014D FPGA configuration is for the most part the same as for the 1013D. I almost fully reverse engineered the one for the 1013D and looked at the one for the 1014D to find matching parts. The basic conclusion is that the design is crap and only ok for simple hobby use. The original firmware polishes the signal to make it look good, but it is utter crap. The new firmware for the 1013D improves things quite a bit especially now that Atlan took over to tweak things and implement the parts I skipped. Unfortunately for some it can't be used on the 1014D. Efforts on porting it seem to have stopped. --- End quote --- Thank you for pointing it out. One screen is 14 divisions, so in the worst case it's 1500 samples for 14 divisions = ~100 samples per division (but it feels even lower than that hehe). |
| Navigation |
| Message Index |
| Next page |
| Previous page |