New Zoyi multimeter+oscilloscopes - ZT-70xS, up to 50MHz/250MSps (nov 2022)

[tol]

I don't know, probably it's a bug. The trigger place of the signal is shown correctly in the center up to 500 ns, but when we reduce the time scale to 250 ns or less, the trigger place is lost from the screen. It can be still found somewhere if we move the signal picture to the sides, but as we reduce the time scale it can be hardly made manually as it takes unreasonable amount of time (several minutes). Besides, the position of the marker on the scroll bar becomes lost (out of range) and it's even impossible to understand what part of the memory is shown at the moment. Moreover, getting back the trigger pointer to the center of the screen may takes minutes to roll it back with the arrows buttons - I couldn't find a button that could get it back at once (except reseting the hole device to defaults). I think it's the most annoying issue that I found in this device by the moment.

[AGMAR1]

1) I would like to say hello, as a new user of ZOYI ZT-703S, which was purchased two days ago Version 1.4.2

2) After one day of use, the equipment seemed great for the price and what I expected from it. Oscilloscope tests with periodic signals from the generator up to 1 MHz showed me its capabilities in relation to the analog equipment I had in the years 1990-2000. Unfortunately, I later tested with single signals and came across problems .... I think the quality of the software is lacking in proper documentation. And that is why I need help from experienced people who own and understand this equipment.

3) In order not to discuss all the problems in one post, I will try to present the problems with version 1.4.2 successively
4) Here the first question in version 1.4.2 is the ability to set in the menu (Sample : Peak or HD) there is no such option in the documentation. How is the sample created in these modes? And how does it relate to the sampling period. I know the operation of a digital oscilloscope well enough to understand that for one channel, sampling at 100 MHz gives sampling every 10 ns. If we have a buffer of 128,000 samples, it gives us a recording time of 1800 micro sec. But how do we set the time base to 1 or 50 [ms]? Does the sampling period change? (the sampling period value should be displayed). How is the sample (HD) composed and how is it displayed. The documentation does not describe at all how it looks, and it is very important to understand what is displayed.

5) Additionally, if I view the graph (Hold key), I can scale (enlarge the waveform) to a certain range? so what is sampling or cheating.

6) In addition, I do not fully understand the way storage depth is presented on the screen (the bar on the left at the top in the documentation, item 2 Time Base Window). Is what is in gray recorded but not visible on the screen?

Please be very understanding, maybe I missed something reading the last very interesting posts, especially from jar171. I also understand that I didn't buy the equipment for 500 Euro, but I think that if you know the shortcomings of the equipment, you can fix it.

7) I can't find a list of errors detected by others in general.
In the next post I will address the problem of incorrect display of data from the fifo buffer. which led to my frustration

[AGMAR1]

The second question/error is more difficult to present but I will try.

9) When I started testing a single trigger. A simple test of charging/discharging a capacitor through a resistor. I wanted to see if the trigger would work and understand how to buffer and then present data or position 2 of the Time Base Window)
I was getting strange recordings Figure 1 and 2, and I was expecting something like Figure 3 and 4 (this is a different mode of operation without triggering, so the question arises how it is assembled).


10) Analyzing Figures 1 and 2 I have the impression that the meter is not showing from the right place in the fifo buffer.

11) I also noticed that when I set the trigger location in time (green marker) after the red arrow, the oscilloscope records correctly. Figure 5 and 6

12) what does the red (triangle) marker (on the up window) mean?

[AGMAR1]

I also noticed what "Tol" wrote in the previous post, that the trigger for the time base below 500ns triggers in the wrong place. To see the shift you have to press the Hold key and then increase the time base, then you will see the trigger shift (it is significant). You have to test it on a single peak, not a periodic signal. Maybe it is a buffering error.
What I wrote in the previous post if you know the shortcomings of the equipment you can fix it.

[tol]

You have to test it on a single peak, not a periodic signal. Maybe it is a buffering error.

Yes, I also found that the single trigger gives more chances to find what you want. Your suggestion with the hold button is also helpful. However, let's take a look how the horizontal marker works. If we reduce the time scale, we can see that the green trigger marker always stays in a fixed place, while the real position of the triggered place moves to the left side. This is surely yet another bug. And I also have no idea what the red marker means, it feels like it's just the center of the screen marker? Before buying this oscilloscope I've watched a lot of reviews on youtube and some user showed very well that the scroll bar and the markers live their own life in different zoom levels and cannot be trusted, as well as the grid that shows unreal values in different zoom levels (I don't know if it was fixed in 142). To say the truth, it looks like the engineers tested this device in some lower zooms and decided that if it works fine there, there is no need to test other zoom levels.

[tol]

By the way, I just looked at the screenshots above and found another nonsense. It shows a graph with the signal rise from 0V to 3V and the calculations window shows max 3.1V and min 3.0V. I have no idea where it takes these values from. Maybe the reason why nobody still made a full list of bugs is that all this firmware is a whole rotten bucket of bugs

[indman]

Maybe the reason why nobody still made a full list of bugs is that all this firmware is a whole rotten bucket of bugs

These errors with the trigger and calculations have already been mentioned many times on previous pages, read carefully!
I also wrote that it is difficult to use oscilloscope as a measuring device in ZT-703, it is just a toy!
Waiting for custom firmware, because there is little hope for the manufacturer.

[IC_Toaster]

I don't know, probably it's a bug. The trigger place of the signal is shown correctly in the center up to 500 ns, but when we reduce the time scale to 250 ns or less, the trigger place is lost from the screen. It can be still found somewhere if we move the signal picture to the sides, but as we reduce the time scale it can be hardly made manually as it takes unreasonable amount of time (several minutes). Besides, the position of the marker on the scroll bar becomes lost (out of range) and it's even impossible to understand what part of the memory is shown at the moment. Moreover, getting back the trigger pointer to the center of the screen may takes minutes to roll it back with the arrows buttons - I couldn't find a button that could get it back at once (except reseting the hole device to defaults). I think it's the most annoying issue that I found in this device by the moment.

This is the way my device works.
Is the amplitude value right?
In my device the usual value is 0,2 - 0,3 volts less than the real value

[IC_Toaster]

Maybe the reason why nobody still made a full list of bugs is that all this firmware is a whole rotten bucket of bugs

These errors with the trigger and calculations have already been mentioned many times on previous pages, read carefully!
I also wrote that it is difficult to use oscilloscope as a measuring device in ZT-703, it is just a toy!
Waiting for custom firmware, because there is little hope for the manufacturer.

Exactly, my perception is more and more as a toy.
When you try almost any digital oscilloscope, you star to feel this device is a toy and not very reliable in some situations.

[tol]

These errors with the trigger and calculations have already been mentioned many times on previous pages, read carefully!

I think we should point it out in every page of every forum. It is quite typical for Chinese manufacturers to abandon the firmware updates as a new version of hardware appears, which may happen every year. So we should take attention of the developers at least to the most terrible issues in hope they fix them in newer firmware, because I bet there will be no new firmware fixes as soon as they make zoyi 704 - they will just spend all their time to fix it's bugs and abandon 703 with all the bugs that it has at the moment because such small companies don't have enough people to support previous models of products... So the list of all the bugs is not a bad idea, the problem is to deliver this list to somebody who is responsible for the firmware development. Alternative firmware from users is also a good idea but we never know if it becomes better or worse that the original For example, I have no idea how to write firmware for oscilloscopes, and if the alternative firmware happens to miss some features that I need from the original version, I will have to use the original firmware anyway...

This is the way my device works.
Is the amplitude value right?
In my device the usual value is 0,2 - 0,3 volts less than the real value

The voltage is different on both channels in my device. Channel 1 always shows higher voltage than Channel 2. The difference is usually 0.1-0.2V, but it is MUCH higher when measuring higher voltage. I tried different probes and I reset the device to defaults, and calibrated several times, and swapped and calibrated the probes, but nothing helps. I think it may be caused by the resistors/capacities tolerance somewhere in the device channel lines, and this difference cannot be compensated in the settings.
In the second picture, it measures RMS 245V, while in the voltmeter mode it shows 220V, which is true voltage (I thought it could be because of different algorithms of RMS/TrueRMS measuring, but the difference is the same with clean sinus wave, so it's just the way it works.

[tol]

And just to be fair, here is the same device with the same probes that shows 0.1-0.2V higher voltage than 3V (my multimeter measures 1.48*2=2.96V). But the first channel is higher anyway. I don't know why this happens. I found that the measurement precision depends on many things in this device,  the values change when I zoom horizontally or vertically, and even when I change HD/PEAK mode, the values may also change.

I've got the most close-to-reality values when I closed the input sockets with a foil from a chocolate and made full re-calibration of the device. I'm not a specialist in such issues but I expect that the open sockets may grab some noise from the air that will make the calibration less precise. For example the second and the third photos show what happens when I just touch the probe (it is not connected to anything except my finger). It feels that I work as an antenna and receive a lot of energy from the air... Actually I can slightly light up LEDs when I touch them

[AGMAR1]

I don't want to start a discussion about toys. IC_Toaster and Indman are almost right. But I wouldn't call ZT-703S a toy but an indicator... for which 20 years ago many would give a lot to have it lying on their table, even with such errors.

After three days I "feel" where the errors are in the software and my son (as a young "electronics engineer", he bought this indicator) can see\measure certain things with his own eyes, which is rather difficult to do with a voltmeter alone. During these few days he saw: interference on the amplifier power supply, phase shifts, the influence of the bias on the overheating of transistors working as switches.

I am attaching several images from CAN transmission in the car where I can check the voltage levels on the lines (and even the values ​​in version 1.4.2 are appropriate). Possibility of recording data on a time basis of 2 ms and then scaling to the level of 10 micro sec.

It is obvious that there are errors in the software and the buffer indicator in the browsing mode contradicts logic, but it works according to this logic (sometimes you have to reset the meter).
It is obvious that my son would not be able to handle these errors without experience ... now he is already working.
Quite probably after a year he will stop being a "Young Electronics Engineer" and the indicator will remind him of those years and maybe I will use it sooner. But it is only a loss of 70 euros.

I see potential in this device for an amateur and I am waiting for the software to be changed.

For my part (let the other users of this indicator do it) I have already written a letter to the director and manager of this company what I think about the software. The motto of this company is "Need to get in touch with the team? We are all ears！" I wrote ... I am checking if it is true and waiting for a response ... and maybe it will not come.

[AGMAR1]

Now if there is anyone who can answer me or point me to sources of information:

1) How do Samples work in this oscilloscope: (Peak or HD);

2) how does the sampling period change from the time base (and when there is then the possibility of scaling down almost 10 times);

3) how does the "scrolling mode" work, apart from the fact that they are for slow signals.

4) Here are words of admiration for "ajar171" for taking on such a difficult matter.

Secondly, to forum user "tol", as I wrote, he does not treat this device as an oscilloscope but as an indicator. Moreover, such effects as you describe may be the result of a mismatch or lack of appropriate load. Yesterday, my son and I measured a seemingly simple thing, a Graetz Bridge rectifier circuit, and the effect was the same as in your drawing. After loading with a lower resistance value, there was no such effect. But I am not an electronics expert, but a programmer.

[csuhi17]

The automatic measurement is bad, this has been written several times before, that's why you have to use the cursor.

If I calculated and measured correctly, then at 1V/Div sensitivity, the maximum measurable voltage is 9.3Vpp measured with the cursor and according to the automatic measurement it is only 8.6Vpp.
In other words, the automatic measurement is faulty for some reason, I think this must be a firmware bug.

In 1V/Div.
The smallest change that the device measures is 0.05V.
In other words, 50mV, 100mV 150mV. There is no value in between.
Theoretically, it is 8-bit stuff, but if I divide 9.3V by 0.05v, it only comes out to 186, not 256.

If I compare it to the voltage accuracy of DMMs, which is ±(%+digit).
so if I measure a wave that is definitely 3.00V with it, but it shows 3.2V, it is only a +4 digit difference, inaccuracy.

According to the description: "DC Gain Accuracy: ±3%"
It doesn't say what % it is, but I don't think it is the same for every time base.

According to the description:
Sweep speed range: 10ns/div – 20s/div
Sample rate range: 1.5Sa/s – 280MSa/s
If you swap the sample rate value, for example, then
Sweep speed range: 10ns/div – 20s/div
Sample rate range: 280MSa/s - 1.5Sa/s

The memory only says:
"record length: Max 128Kbyte"
From this I assume that it is not constant.
Since we can't save the wave as a file with it, only save images, so I don't know.

I think the HD/Peak detect mode just thickens the lines and makes the part you can't see visible.
I tested it with a single trigger, zoomed in to the wave in HD and Peak detect mode, and I didn't see any difference in the faster time base.
But I hope I'm wrong.

[Atlan]

If it is not done in the same way as with 1013D, the change on bit 0 and bit 1 is simply ignored.

[IC_Toaster]

This is the way my device works.
Is the amplitude value right?
In my device the usual value is 0,2 - 0,3 volts less than the real value

The voltage is different on both channels in my device. Channel 1 always shows higher voltage than Channel 2. The difference is usually 0.1-0.2V, but it is MUCH higher when measuring higher voltage. I tried different probes and I reset the device to defaults, and calibrated several times, and swapped and calibrated the probes, but nothing helps. I think it may be caused by the resistors/capacities tolerance somewhere in the device channel lines, and this difference cannot be compensated in the settings.
In the second picture, it measures RMS 245V, while in the voltmeter mode it shows 220V, which is true voltage (I thought it could be because of different algorithms of RMS/TrueRMS measuring, but the difference is the same with clean sinus wave, so it's just the way it works.

This is a disaster. One channel is wrong and the other is worse.
As it is not possible to see the samples value, I think it is difficul to deduce if the problem is the samples quantification, the values adquired by the A/D converter or the processing.
I don't think there is a different algorithm for each channel.

And just to be fair, here is the same device with the same probes that shows 0.1-0.2V higher voltage than 3V (my multimeter measures 1.48*2=2.96V). But the first channel is higher anyway. I don't know why this happens. I found that the measurement precision depends on many things in this device,  the values change when I zoom horizontally or vertically, and even when I change HD/PEAK mode, the values may also change.

I've got the most close-to-reality values when I closed the input sockets with a foil from a chocolate and made full re-calibration of the device. I'm not a specialist in such issues but I expect that the open sockets may grab some noise from the air that will make the calibration less precise. For example the second and the third photos show what happens when I just touch the probe (it is not connected to anything except my finger). It feels that I work as an antenna and receive a lot of energy from the air... Actually I can slightly light up LEDs when I touch them

I have notice that the values change even if you move the reference down.

That you say that you introcude signal just touching the probe happens also in good oscilloscopes. Certain, you act as antenna and that signal is the electrical installation signal (50-60Hz).

I don't want to start a discussion about toys. IC_Toaster and Indman are almost right. But I wouldn't call ZT-703S a toy but an indicator... for which 20 years ago many would give a lot to have it lying on their table, even with such errors.

After three days I "feel" where the errors are in the software and my son (as a young "electronics engineer", he bought this indicator) can see\measure certain things with his own eyes, which is rather difficult to do with a voltmeter alone. During these few days he saw: interference on the amplifier power supply, phase shifts, the influence of the bias on the overheating of transistors working as switches.

I am attaching several images from CAN transmission in the car where I can check the voltage levels on the lines (and even the values ​​in version 1.4.2 are appropriate). Possibility of recording data on a time basis of 2 ms and then scaling to the level of 10 micro sec.

It is obvious that there are errors in the software and the buffer indicator in the browsing mode contradicts logic, but it works according to this logic (sometimes you have to reset the meter).
It is obvious that my son would not be able to handle these errors without experience ... now he is already working.
Quite probably after a year he will stop being a "Young Electronics Engineer" and the indicator will remind him of those years and maybe I will use it sooner. But it is only a loss of 70 euros.

I see potential in this device for an amateur and I am waiting for the software to be changed.

For my part (let the other users of this indicator do it) I have already written a letter to the director and manager of this company what I think about the software. The motto of this company is "Need to get in touch with the team? We are all ears！" I wrote ... I am checking if it is true and waiting for a response ... and maybe it will not come.

When I received the Zoyi I was quite surprised because my last use of an oscilloscope was some years ago and I had used mainly analog oscilloscopes. So I found this device quite useful, but after seeing the bugs and have bought a Siglent my perception was changing.
I know this is more than a toy, but I feel, due to the lack of precision, that you need to know the bugs and have some criterion to discern if the values could be right or not.

[ajar171]

The only difference (electrically) between the two channels is an analog switch (6\$\Omega\$) just before the ADC input (10k\$\Omega\$).
I could not find out, how they do the self-calibration, although I must admit, that I did not really looked into that yet. I have still 3 unknown pins on the MCU..

From the firmware side of things, I think that they push everything through the DFSDM of the MCU (I will do that for sure), wich does the Sinc filtering, mix/max detection and offset correction.
If fed with the wrong offset values, the poor filter will give us wrong output

[ajar171]

Just some thoughts about the selfcal for discussion:
Each analog channels voltage divider can be set from 1000:1 to 1:1 in 12 steps.
I have no idea how a selfcal without an external (high) voltage fed into the BNC connector could work in a device where the highest internal voltage is that of the battery 

[tol]

Moreover, such effects as you describe may be the result of a mismatch or lack of appropriate load. Yesterday, my son and I measured a seemingly simple thing, a Graetz Bridge rectifier circuit, and the effect was the same as in your drawing. After loading with a lower resistance value, there was no such effect. But I am not an electronics expert, but a programmer.

As far as I understand, this happens when being close to high voltage wires. The frequency of this parasite signal is 50Hz, this is exactly the same frequency used in high voltage lines in my country. Besides, this signal gets stronger when I get close to the places where the wires or electronic devices are placed and it is absent when I'm out of house. So this is not the problem of zoyi itself but a problem of the "dirty" environment, in terms of electromagnetic fields around us. It's possible that calibration in "clean" electromagnetic conditions may be important to this device. As far as I understand the main purpose of the calibration is to find the pattern of the internal noise in the device and eliminate it by software algorithms, so IMHO the cleaner the calibration conditions are, the better.

Anyway, I think this device is not so bad, I've bought it for just $50 and I need it mostly to play with esp32/raspberry and other hobby stuff. Now I can see PWM and this is what I couldn't do with a voltmeter.  I think that everyone understands that the oscilloscope for $50 cannot work the same way as the oscilloscope for $5000. The fact that is has problems with measurements and correct trigger place display seems to be more software issue than hardware issue, we only need to encourage the developers to read this forum thread and respond somehow. I believe that many issues can be solved easily by somebody who has the source code and can modify it. The most difficult thing is to reach that person and tell him what needs to be fixed

[tol]

1) How do Samples work in this oscilloscope: (Peak or HD);

I don't know how it works but I feel that it's just a kind of software noise filter. Maybe it's just a marketing trick to make the graph look more clean in comparison with the cheap oscilloscopes of competitors. What I see is that HD just shows some average line from what I see in the PEAK mode.
 

[AGMAR1]

There are many topics discussed and very important…….

1) Thanks to csuhi17 with a good compilation of data, it is necessary to understand what we require from the device and directed me to some tests. But I would like to establish one basic thing, the sampling frequency for one channel. Ajar171 writes that "dual channel 100MSPS ADC (overclocked to 140MSPS in high speed mode), both channels sampled in parallel." and I agree with this, the given frequency of 200 - 280 is marketing for two channels. Maybe I am wrong and when we use one channel, two converters work for one channel, which I doubt.

2) Differences for Peak or HD Atlan is wrong "If it is not done in the same way as with 1013D, the change on bit 0 and bit 1 is simply ignored."
I am attaching several images in turn:

p1 is a test signal sin 25,000 Hz amplitude 10 : -10; we can see it nicely, it has 10 us and we measure it.
p2) we increase the base time to 5ms and we get what should be visible (sample Peak mode) it is good. we see too large a time base.

p3) we change to HD mode and we see a straight line ... so there is some averaging. I will definitely not use this mode when I see the signal for the first time.

3) Additionally, I am attaching another 3 drawings where:
p4 records the same signal based on 1ms;
p5 (hold key) o I increase to 10 us and I see a beautiful sine signal. I cannot decrease the time, there is a blockade.
P6 I do the recording based on 5ms and I can increase to 10us and the signal is the same as for p5

4) As csuhi17 wrote, without real data we are not able to properly determine what the sampling, buffer length or interpolation is, but these tests allow me to determine certain limits of the device.
6) I am attaching two additional drawings:
p7) shows the image at a base of 100ms and this is normal, the sampling has changed and hence such an image and the wrong frequency.
p8) very long time base... We change the sample mode Peak HD Peak during recording

[AGMAR1]

I didn't want to discuss separate topics in one place

1) Ajar171 Unfortunately, I\We are not able to help you at all, we are waiting for the result like hyenas. Maybe if you found the time, you could present the diagram, give the firmware for testing, but I also doubt that it would help you. Rather us. Think about it. If you have time, answer question 3)

2) The topic of voltage measurement accuracy ... I don't quite understand what you require from this indicator. I have a +10 -10 sine (I don't know if it's correct) on the oscilloscope, the Amplitude is displayed halfway, i.e. about 128 bits, one percent (20 V) is 0.2, I assume that 3% 0.6 is OK and for small voltages it is OK.
3) Change of accuracy when shifting up or down (question to Ajar171 whether the shift is on the analog side), a diagram of the input path is needed. I think the shift is on the analog side because after shifting out of range the calculations are also cut off. I don't think the programmer averaged over bytes and after shifting and then subtracted the shift value. (difficult to explain).
4) As for the previous post (sampling test), it is obvious that switching to 140 MHz removed (illustrating) the intermediate frequency of 6.14 KHz. The question is still whether the sampling is 140 or 280 MHz

[ajar171]

I didn't want to discuss separate topics in one place

1) Ajar171 Unfortunately, I\We are not able to help you at all, we are waiting for the result like hyenas. Maybe if you found the time, you could present the diagram, give the firmware for testing, but I also doubt that it would help you. Rather us. Think about it. If you have time, answer question 3)

2) The topic of voltage measurement accuracy ... I don't quite understand what you require from this indicator. I have a +10 -10 sine (I don't know if it's correct) on the oscilloscope, the Amplitude is displayed halfway, i.e. about 128 bits, one percent (20 V) is 0.2, I assume that 3% 0.6 is OK and for small voltages it is OK.
3) Change of accuracy when shifting up or down (question to Ajar171 whether the shift is on the analog side), a diagram of the input path is needed. I think the shift is on the analog side because after shifting out of range the calculations are also cut off. I don't think the programmer averaged over bytes and after shifting and then subtracted the shift value. (difficult to explain).
4) As for the previous post (sampling test), it is obvious that switching to 140 MHz removed (illustrating) the intermediate frequency of 6.14 KHz. The question is still whether the sampling is 140 or 280 MHz

1, there is not much to test at the moment, I am working on getting all the hardware stuff running properly. The firmware has currently no oscilloscope function at all, my focus is currently on the DMM part.
2, a vertical DC gain accuracy of ±3% is explicitly stated in the specs of this meter, so it is within specs. An oscilloscope is not intended to be a precision voltmeter anyway.
3, it is a result of the inaccuracy of the divider network (there are a lot of resistors in the signal path, even if they all have 0.1% accuracy, it adds up...) and the joke of a selfcal function. All filtering, averaging is done in HW, see the DFSDM block diagram (ignore the serial and parallel ADC part, the data is coming from the bus)
4, a 280MSPS is electrically possible only on channel 1 (it is still 140MHz ADC clock, but with a 180° clock phase shift), but I don't know (and don't care) if Zoyi uses it in the stock firmware.

I am not posting anything, that I have reverse engineered, because I don't know if it is even legal in Germany.

[LucSVK]

I am not posting anything, that I have reverse engineered, since I don't know if it is even legal in Germany.

I have heard before that it's legal in EU, not in the US...


https://www.tme.eu/en/news/library-articles/page/56932/reverse-engineering-what-is-it-and-is-it-legal/

In the European Union, reverse engineering is permitted – under the verdict of the Court of Justice issued in 2012 – for creating computer programs with operation analogous to the original program. In that verdict, the Court of Justice ruled that the functionality of software is not protected by copyrights within the territory of the EU, which opened the door to research and testing of original programs so as to reproduce (not copy) their behavior in another program.

[ajar171]

I am not posting anything, that I have reverse engineered, since I don't know if it is even legal in Germany.

I have heard before that it's legal in EU, not in the US...


https://www.tme.eu/en/news/library-articles/page/56932/reverse-engineering-what-is-it-and-is-it-legal/

In the European Union, reverse engineering is permitted – under the verdict of the Court of Justice issued in 2012 – for creating computer programs with operation analogous to the original program. In that verdict, the Court of Justice ruled that the functionality of software is not protected by copyrights within the territory of the EU, which opened the door to research and testing of original programs so as to reproduce (not copy) their behavior in another program.

Happy new year everyone!

I know, that it is legal to RE a product that I have bought, I just don't know if it is allowed to publish or share the information obtained through RE. Sorry, but it is simply not worth the risk for me.