DS213 Compatibility [Enhancement Request] #44
Comments
PawxSpec
changed the title
|
Hello! I am currently working on firmware for LA104 (https://github.com/gabonator/LA104) which is device produced by the same company and uses the same processor. I took a bit different approach - simple operating system that can load ELF application images, so the development is much faster and also you do not need to think "which memory slot contains which app?" Just nice simple graphical application switcher solves this task:
So a lot of things will be reused from LA104 development. I do not have capacity to maintain this (DS203) firmware and I noticed that every week (or so) a new issue is reported. So I am hoping that new DS203/DS213 fw will be compatible with all hardware revisions and we will solve these hiccups with choosing the right firmware image for your oscilloscope - because there were multiple hardware revisions and you need to choose the right image version to get it working. Also people were puzzled to choose the right firmware, because there were 4 different ones which loads to 4 different slots. Not everyone understood the idea that you can load 4 different firmwares onto the device.... (just look into issues tab). So I am now waiting for e-design to provide me with all source codes to start porting this (DS203) firmware to the new design. Just out of curiosty, if anyone is reading this, give +1 if you also request the firmware for DS213, so I will know whether there is actually demand for it. When I will start the development for DS213, I will let you know here |
|
+1 for DS213 |
1 similar comment
|
+1 for DS213 |
|
specially x/y function to measure sinus cosinus figures |
|
+1 for ds213 |
|
+1 for the DS213 for sure. I love this little thing but it needs some work. Thank you, Marco Reps for pointing me to this. |
|
+1 for DS213. |
|
+1 for ds213 |
|
+1, keep up the great work! amazing! |
|
+1 for DS213 as well! Happy to test as well. I opened it up and found an SOIC-8 SPI flash chip, would a dump of that be useful? When I originally got this, I thought it would be compatible with these existing FW's, as I thought only the analog input rate was increased. I've been so bummed, especially because it was like three times the cost of a DS203, or even a LA104, and the existing firmware has been so difficult to use that I haven't even used it successfully once... |
|
@cmorche, that SPI chip contains the FAT filesystem you see when you attach your device to PC, so it holds only configuration and possibly screenshots and caputred signals. I am currently working on compatibility with DS213 and it works quite well, at least the operating system stuff, now I just need to figure out how to read captured data from FPGA and combine it with the fw I made for DS203. I will focus mainly on DS213, I cannot promise anything regarding the DS203, since it was made in various hw revisions and for me it is absolute magic what are the differences and I just dont want to spend much time with backward compatibility. Guys at e-design will be surely very happy, when owners of DS203 will upgrade to DS213 to try new features... :) |
|
+1 for DS213.... I would be happy to help debug when you get an initial firmware. The current firmware is garbage and cannot trigger using single or normal trigger mode with high sample rates. It makes the product useless to me, so I really hoping you can fix and provide a new firmware quickly. |
|
@gabonator I'm not sure if it's helpful, but I just noticed they released the source code for the latest FW update for the DSO213. Looking forward to any updates :) |
|
@cmorche, thank you, anyway I am right now looking at this code :) I successfully ported if to my OS, but for my surprise, the trigger does not work properly. If I connect WAVE OUT to CH1 and configure trigger level and channel, the screen is not refreshing. Only when I switch to "SLOW" display mode, I can see the waveform. Strange. At first I thought it is my fault, but then I flashed their FW and it behaves in the same way. |
|
Just to note. The 1.22 firmware that you reference has the trigger bug. You can refer to the forum link below: http://minidso.com/forum.php?mod=viewthread&tid=3518&extra=page%3D1 I honestly don't have too much faith in mindso to fix as it has been months and they will not commit to a timeline. Without that trigger functionality most of us think the DS213 is useless. So, I think we are all hoping that gabonator can come in and save the day! |
|
...pretty sad, I don't understand why they still didn't fix this issue. If only I could split into 5 persons, so I can do all the things I planned to do and go to work and still could have time to party with friends till late morning. But surely this wonderful piece of hardware deserves some more time, but it seems this will be problem of the FPGA code which was not released yet. They released only the code which is running on ARM processor, but not the code running on two other chips on the board. |
|
If it is something you think you could fix, I will get on their forums and request the FPGA code. Maybe they will provide it. They claim it is open source, so they should make it available. |
|
@caykroyd1 I was just thinking that as well. I've contacted other companies
in the past for GPL violations and source code requests, and was usually
successful (Except Panasonic...). I'll try emailing them/contacting
support, if you want to pester them on the forum?
I can't believe they are selling this for so much, when it has major
unresolved issues. Plus, the OG DS203 is going to be off the market soon.
I'm really starting to regret ignoring all the threads I read online before
I bought this, that all said to spend your money on something non-portable
and professional instead.
…On Thu, Aug 1, 2019 at 3:25 PM caykroyd1 ***@***.***> wrote:
If it is something you think you could fix, I will get on their forums and
request the FPGA code. Maybe they will provide it. They claim it is open
source, so they should make it available.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44?email_source=notifications&email_token=AE66KDBO6G34O32BLVWKORTQCNPGHA5CNFSM4GSSHJP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3MB4AA#issuecomment-517479936>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE66KDFTY6DW26H7WJEYCC3QCNPGHANCNFSM4GSSHJPQ>
.
|
|
@gabonator/DS203 <[email protected]> come on, you don't just want
to give up all those material needs and dedicate yourself to a niche
firmware replacement for a spectrum analyser, especially with the added
challenge of an unhelpful seller? (They seriously seem inept on their
forums, people are simply requesting copies of the original app.hex and
they cant even provide that...). I'm just kidding btw, thanks for your
effort in this, it's greatly appreciated!
Do you accept any donations? I'm unemployed ATM, but would happily toss
some coinage your way :)
…On Thu, Aug 1, 2019 at 4:48 PM Caleb Morche ***@***.***> wrote:
@caykroyd1 I was just thinking that as well. I've contacted other
companies in the past for GPL violations and source code requests, and was
usually successful (Except Panasonic...). I'll try emailing them/contacting
support, if you want to pester them on the forum?
I can't believe they are selling this for so much, when it has major
unresolved issues. Plus, the OG DS203 is going to be off the market soon.
I'm really starting to regret ignoring all the threads I read online before
I bought this, that all said to spend your money on something non-portable
and professional instead.
On Thu, Aug 1, 2019 at 3:25 PM caykroyd1 ***@***.***> wrote:
> If it is something you think you could fix, I will get on their forums
> and request the FPGA code. Maybe they will provide it. They claim it is
> open source, so they should make it available.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#44?email_source=notifications&email_token=AE66KDBO6G34O32BLVWKORTQCNPGHA5CNFSM4GSSHJP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3MB4AA#issuecomment-517479936>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AE66KDFTY6DW26H7WJEYCC3QCNPGHANCNFSM4GSSHJPQ>
> .
>
|
|
The only donation I accept is invitation for couple of beers :) I am doing it in my free time because I am having lots of fun with it. The LA104 is great as arduino replacement, it has battery, display, simple controls, you can load it with tons of applications and switch between them very easily. The situation around DS213 is bit worse, you can use it "just" as oscilloscope, since it does not have any GPIO pins exposed and without proper firmware it is more or less useless. They guys at minidso are very kind, every time I was facing any software issue and requesting portions of BIOS code (which is not open source, this is the way how they protect their devices from counterfeit copying), they always replied in few days. This is their response regarding trigger problems:
So let's just be patient... It is summer, maybe their engineers are just on vacation |
|
Today I discovered that single mode trigger works with time base >= 5ms and with timebase < 5ms it shows all the readings but doesn't show the waveform which means the waveform gets captured it just don't show up on the screen. Maybe this could be of some help |
@aviralpatel Cool finding... It may be best for you to post your findings here: They are not working very hard on fixing this, but this information might give them the push they need to fix the scope. |
Does not look like it's going to be fixed in this year. And they definatly won't realize the code for fpga until they fix it. Can somebody explain to me what is the problem? When I got DS213 I noticed that issue and was trying to fix it. I found out that there is no problem with firmware but with fpga. I did some workaround like disabling other channels and it makes it to work a bit better. But still it's mostly useless and just stay in a box covered with dust. I never code fpga and I don't understand what the problem to write own firmware from scratch? Is it too difficult or impossible without their input? According to how firmware works I found that it mostly only sets sample rates and trigger, and on trigger reads values from fpga, sounds simple, doesn't it? |
|
I have good news (email from minidso.com):
|
|
good to know they at least give email feedback to someone, @gabonator I imagine they're not a large team, but products are beautifully made, and I hope they'll keep working on these toys. |
|
Guys, I have 3 firmware 1.20, 1.21, 1.22, can it help? |
|
1.20_119kb. 1.21_103kb 1.22_98kb weird thing |
|
Some news about upgrade to V1.27 I have received a new DS213 just today. It worked well. But I have downloaded upgrade to V1.27 from official site and made it. (No!!!) The problem looks like here: http://www.minidso.com/forum.php?mod=viewthread&tid=4421&extra=page%3D1 After long rewritings of firmware (all versions from this forum) I have found, that China's version V1.28 working well on my DS213. It looks like something was changed in the hardware. China interface, yes :( |
|
@Sergee17: 1.) What means China interface ? I just use the existing USB port and a PC to flash the software. 2.) V 1.28 is for me completely unknown and I don't find it on MiniDSO page. In Jan 2021 there was the echo-version with Roll-Mode based von V1.27 3.) What version has been the delivery state of your DS213 ? If you might have a hardware change in your very new DS213, <V1.28 couldn't be on it, (I got my DS213 in Sept. 2020 and it had V1.22 on it) |
|
1.) China V1.28: https://www.minidso.com/forum.php?spm=a2g0s.imconversation.0.0.b7bb3e5foW6t13&mod=viewthread&tid=4619&extra=page%3D1 It's just App and it works well with FPGA018 from 1.27 2.) Any kind of 1.27 does not work (have tried all including both echo-versions) 3.) Didn't remember. I just started following the instructions and did not pay attention to the version when the device started. |
|
@Sergee17: If you bought your DS213 as one with chinese texts, so I could image, that english menues from versions <V1.28 don't work, because the chinese language may have other printouts. |
Me too.
No, it was english Support have mailed me a new (?) .hex file with V1.27 App. It looks better but buttons K1...K4 still does not working. Encoders' are better. Maybe. Could anyone give me a *.PRM file from "pure" DS213 V1.27 (Not echo). I have an idea. |
|
@Sergee17: I only can say, that on my DS213 the following versions are working (especially the menues): V1.22; V1.22f; V1.27; V1.27 with roll mode from echo DS213 APP 1.27 FPGA018.zip from mindso-page included DS213AppV1.27.hex, but not an *.PRM file. The DS213AppV1.27.hex is 109KB (122 204 Bytes) which I found by property-function from Windows. |
It's a simple settings file stored on the DS213's disk "U". Otherwise, it will appear after pressing K4+K2 buttons and its name will be 'serial#'.PRM. Just rename it for safety. 512 bites in my DS213 V1.28
|
|
K4+K2 buttons pressed together saves the system settings which is described in the manual of the DS213. May be that the serialnumber is stored too in this *.PRM-file. I think MiniDso should help or anybody other who understand that problem. |
|
I might be a bit late to the party but I've read that some of you have had to resort to using the 1.28 version of the software in Chinese. I had the same problems but now I have the 1.28 version in english. So if you need it let me know... |
Fantastic! :) Could you share this version? Thank you in advance! |
|
@DaSithDude |
|
I don't really know what the differences are between 1.27 and 1.28. I just received mine yesterday and wanted to flash the alternative firmware on there with "roll mode" support. But that didn't work. So I thought i'll just put back the 1.27 I found on the minidso website. But then the buttons acted all weird so I couldn't control the scope. I contacted the seller on aliexpress and got an answer within 5 minutes to give them my email so they could send me the newer firmware. Sadly its just the .hex file so no source, sorry @Tooluserathome . @Sergee17, here is the file, hope it works for you. I did have to copy everything using the command prompt (using win 10) https://drive.google.com/drive/folders/1IQIHShi-_EY4YOk6SHemS7XokCYPV5Ut?usp=sharing |
|
@DaSithDude the wheels in mine are also super jumpy, a pain to use. Did you find a solution? |
|
@dbuezas: After some time of not using it. it's the same. It jumps to all menus. But after dummy movements for a few minutes, it |
|
Yes same here with DS203 after some time they are glitchy. Compressed air helps a little. I then tried a few drops of isopropyl alcohol and somehow it made it inside the LCD which made it unusable. So please DO NOT USE alcohol. Afterwards, I was able to take apart the LCD, IPA wiped clean and air dry all the layers(silver, white, polarize) and the glass and put it back together. Its 99% working and looks as new but still few blemishes can be seen. Finally with DS203 apart, I carefully put a drop of "Pacer Technology (Zap) Rail-Zip 2 Track Cleaner and Corrosion Inhibitors" on both wheels and this seem to work good for few months. |
Thanks a lot! Now my DS213 can work normally
In my case I have the same then DS213 is connected by USB to my laptop |
|
@dbuezas wheels haven't acted up on me so far, 1 click is 1 menu item further. |
|
Has anyone tried hw debouncing? I tried soldering two capacitors (left to middle and middle to right) but it did nothing |
|
@dbuezas I read it above (near the beginning) that gabonator has done it, because he had first described such problems. But did he can say, if it works after long time of unusage. |
|
@gabonator do you mind sharing the diagram of your debouncer? |
|
@xjtuecho I now get problems with the 2 encoderwheels, they are bouncing, so I can't really work with the DS213. I can't really agree to the hardware solution with the 100nF capacitor found by gabonator first, because the spec. from manufacturer Kailh allows 1mA for the contacts in the wheels. And they may damage the wheel contacts by much to high currents from the c. The reason because the wheels from Kailh are not working properly after the time, is probably oil film, which I found on the metal surface of the encoder and I could move it away by my finger. I think this could reach the contacts too. Normally they would have a good lifetime, because they are designed for the wheel of computer mouses |
|
I prepare to replace the wheel encoders after terrible bouncing. In the circuitry of the DS213 ground is in the middle at the encoders connected. And there surely some pullups in the DS213 or form the ports of the STM... I just made some tests to find out if Kalh and TTC- encoders are equal. Strange is, that sometimes one of the both signals are not going back to ground. So ground ist not In the meantime after some movements of the wheels everything works better. Pictures: It's a pity that gabonator didn't answer and tell us about his experience with the debouncing software at his DS213. |
|
Hello guys, sorry for not responding, I was just watching your progress :) hoping that the community will find some workaround. Yes, the encoders are pretty annoying. But I gave up. Did some tests with just capacitors connected to the signal outputs coming from the encoder and ground - nothing more. I made a simple application which draws signal level from the encoders to see whether the noise is still there. I wasn't aware that I could damage them because they are not made to withstand high current pulses coming from the capacitors. I was just playing around and looking for some fix. I thought that they are just cheap low quality encoders with not long lifetime. It needs more research on the combination of hw improvement combined with software debouncer. |
|
@gabonator. Thanks for the reply. Do you have experience for long time unuse and the effect of the software debounder ? The switch is designed for mouse wheel application and the counts of switches over lifetime is very high. If you can't do without Rail-zip, you should let the drop in the house from the metal side and store the DS213 on his display for days. You can imagine that this is better than grease and Rail-zip run away from the contactbars.
|
|
Hey guys! I bought dso203. And it is awesome. I tried to change firmware to wildcat but I failed. Dfu disk is dismounts during transfer at 42 percent. So I tried 3 step upgrade with changing addresses. A and B parts changed correctly(copied and remounted with "use" and "SET"). But C part had some problems. ADR of C part was set but bin file was just copied, there wasn't remounting. I tried to find my problem on another forums but I failed in it too. Would appreciate some advice. |
It seems now you can try 1-step upgrade. |
|
Thank you for reply, but No, it's question about 203
|
|
I installed wildcat on my 203 and still have my 213. The difference is so big. No trigger error, all works smooth |
|
@darkonerakot: I can't help, because I only have the DS213 not a DS203. All my posts are related to Ds213. |
and others
Any compatibility with the DS213?
http://www.miniware.com.cn/product/ds213-mini-oscilloscope/
Other sketchy sources (ebay, banggood.com, etc.) say this has 15MHz Analog Bandwidth.
From main website: (link above)
CPU: ARM Cortex M3
FIFO & Control: FPGA
ADC: HWD9288-100
Analog Channels: 2（[CH_A] [CH_B]）
Digital Channels: 2（[CH_C] [CH_D]）
Operation Channel: INV [CH_A], INV [CH_B], [CH_A]+[CH_B]、 [CH_A]-[CH_B]、[CH_C]&[CH_D]、[CH_C] | [CH_D]
Vertical Sensitivity: 10mV-10V/div (1-2-5 STEP) (using X1 probe)
Vertical Resolution: 8 bits
Sample Memory Depth: 4 channels, 4*4K
Coupling: DC, AC
Max Input Voltage: ±40Vpp (using X1 probe)
Trigger Types: Ascend/Descend Edge Trigger Mode, Positive/Negative Pulse Trigger, Logic Trigger
Trigger Mode: Auto, Normal, Single, Slow
Trigger Source: [CH_A] [CH_B] [CH_C] [CH_D]
Signal Source: Square Wave: 10Hz to 8MHz, in total 20 shifts and 3 Vpp Signal Sources;
Sine/Triangle/Sawtooth Wave: 10Hz to 20MHz, in total 11 shifts and 3 Vpp Signal Sources
Storage: built in 8M USB disk
File Types: BMP、BUF、CSV
Auto Measurement Types: Signal sequence/cycle/duty ratio, peak voltage/virtual value/max value/min value/average
Cursor Measurement: Time value, Amplitude value
Display Modes: 4 wave lines: Line 1: [CH_A], HIDE
Line 2: [CH_B], HIDE
Line 3: [CH_C], REC_1, REC _2, REC _3, REC _4, HIDE
Line 4: [CH_D], [CH_A]+[CH_B], [CH_A]-[CH_B], [CH_C]&[CH_D], [CH_C] | [CH_D], HIDE
Sampling Mode: Real-time Sampling
Sampling Rate: 100M Sa/s
Battery: 1000mAh
Size: 99.5mmx58.5mmx13.5mm
Weight: 129g (with battery)
Certificate: CE, FCC
The text was updated successfully, but these errors were encountered: