Products > Test Equipment
OWON XDM1041 the unknown multimeter...
UniSoft:
--- Quote from: BugCatcher on January 06, 2022, 09:44:10 pm ---Good News: XDM1041 Recording Function
XDM1041 running V3.0.1
--- End quote ---
The big question is where to get that firmware?
--- Quote from: BugCatcher on January 06, 2022, 09:44:10 pm ---Data retention
- power off, 1h later, power on: recorded data still there
--- End quote ---
It is saved inside MCU's flash...
Number of guaranteed program/erase cycles before failure (Endurance): 100 kcycles (according to the datasheet)
And by the way, data and settings can be lost due power failure within erase/write sector.
BugCatcher:
There must be a battery on board. Clock is running without external power supply! The question is the size of the internal SRAM ...
theHWcave:
Maybe a dumb question but are you sure that the data "saved" by DMMeasycontrol" is actually your locally recorded data? I am asking because DMMeasycontrol had that save-the-recording-as-spreadsheed function before and what it actually did was record new data coming in from the meter online into the spreadsheet. It did not even look at the previously recorded local data.
UniSoft:
--- Quote from: BugCatcher on January 08, 2022, 08:27:14 am ---There must be a battery on board. Clock is running without external power supply!
--- End quote ---
Yes, there is a battery, for clock...
I draw the schematic of the control part, attached...
--- Quote from: BugCatcher on January 08, 2022, 08:27:14 am ---The question is the size of the internal SRAM ...
--- End quote ---
If you mean SRAM of MCU, then it is totally 48KB
If you mean storage, then how I said it is stored in FLASH, maximum 1000 points
I am working on reversing firmware...
Funny part, that the firmware is written for STM32F103 MCU (using SPL libraries), but they run it as is on GD32F303
BugCatcher:
Proof of Recording Function
I tried to make the check waterproof!
- step 1 I disconnected USB from XDM
- step 2 XDM power on
- step 3 Temp -> PT100 -> °C
- step 4 Record -> Manual -> Clear buffer -> Back
- step 5 Auto -> set 20 Points -> Interval 1s
- step 6 soft key Start
touched PT100 during measurement (increase/decrease of temperature)
- step 7 checked samples on XDM (increase/decrease of temperature) -> was ok
- step 8 XDM power off, removed PT100 cable
- step 9 reconnected USB
- step 10 XDM power on (running VDC, no PT100 connected!)
- step 11 started DMMEasyControl on PC
- step 12 DMME command Control -> Connect
- step 13 DMME command Record -> Device data export -> entered path/file-name
- step 14 after a few seconds: "Device data export completed!"
- step 15 checked file on PC ... identical with manual observation on XDM -> BINGO!
Stored file:
NO MODE VALUE
1 Period 29.1¡æ
2 Period 29.0¡æ
3 Period 29.3¡æ
4 Period 29.4¡æ
5 Period 29.5¡æ
6 Period 29.6¡æ
7 Period 29.7¡æ
8 Period 29.8¡æ
9 Period 29.8¡æ
10 Period 29.9¡æ
11 Period 29.6¡æ
12 Period 29.0¡æ
13 Period 28.6¡æ
14 Period 28.3¡æ
15 Period 27.8¡æ
16 Period 27.4¡æ
17 Period 27.0¡æ
18 Period 26.8¡æ
19 Period 26.5¡æ
20 Period 26.5¡æ
Other observation:
direct capture with DMME
- you get higher resolution
- you get date/time on top
only problem: formatting of msec is not correct
correct example for time: 19:22:47.779
incorrect example: 19:22:50. 45
-> leading zeros for msec below 100 or below 10 are replaced by "space"
-> trouble with spreadsheet processing
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version