utracerJS, minor issue with debug

[Never Mind]

Re:"debug menu numbers for Va Vs Vsupp Vneg are "funny" for utracer6"

Here is one for when you have "spare time" LOL

I noted that the values reported on the WEB debug page for Va Vs Vsupp Vneg look incorrect.

The values reported by the web server for Va Vs Vsupp Vneg seem correct.

It could be that the values are offset by one to the right on the WEB debug page .

See attached screen shot.

The issue persists for a utracer3+ just with different errors for Va Vs Vsupp Vneg.

I also note that http://utracer.boffin.nl/debug also shows this issue.

Take care

Bob

[Ihor]

Debug on the webpage is indeed synchronises slightly different from the windows software, so you do not see the send and received information in one time, but current received and future send. It is how it is implemented and that window is just for fun, because everything is also displayed in the terminal.

Funny numbers you mean because they are negative? It means the problem with the calibration, so for such low voltages the calibration constants make those values negative. It will be exactly the same with Ronald's software is the same calibration values are used because the formulas are one-to-one the same.  

[Ihor]

oh, I see now, the shift in the positions as well, going to check that. It is also one of those cases when you add new feature (something like support for uTracer6) to a complex code after not looking at it for a year or so :) things easily break 

[Ihor]

it is fixed now, in the updated version. It was only a problem for uTracer6 with the extension board, which has a communication string of a different length compared to the uTracer3 and 6, so the Debug tab was never update with that which the main part worked well with the extension board:) 

[Martin Manning]

Hi Ihor,

I'm seeing a change in the behavior on start-up with my uT3 using this latest version. The terminal window opens automatically as before, and the echo 30 result is true. When I open a new browser window and navigate to http://localhost:80, I see this (no plot area shown):

After clicking over to the Debug screen and back to the Home screen, it looks normal again:

...and runs a trace without issue.

[Ihor]

Hi Martin, 

Thanks! I also noticed it just before you posted here. Now it is also solved (and updated on the website). 

[Martin Manning]

Great, looks good.

Another anomaly... If i click over to the Calibration screen, and then back to Home I can't run a trace unless I first press Abort. 

[Ihor]

Are you observing that in Windows? On my mac, when I start uTracerJS, go to localhost, then Calibration, then click Home tab, I can press Measure without problems. Or are you doing something else? 

[Martin Manning]

On MacBook using Safari.

I can do as you say above, but if I then go to Calibration and back to Home again, I can't run a trace unless I press Abort.

I can press measure, and then measure again, no problem. But if after a measurement I go to Calibration and then back to Home, I have to press Abort to make another trace.

[Ihor]

This is my test in safari on mac, looks like everything works, or I am still missing some steps? 

http://files.smal.ws/v/w86dLf

[Martin Manning]

That's what I'm doing, except I do not have "Log to File" ticked. If I tick that box it works as in your example.

[Ihor]

ah, ok, now I can confirm, in Chrome I get the same. I always have that checkbox on, so have not seen that. It can also be reproduced just with the refresh of the home page without going to any other tab. I am going to check that. 

[Ihor]

solved and updated! :)

[Martin Manning]

Working fine now. Thanks for your dilligence!

On Thursday, September 5, 2024 at 3:15:01 PM UTC-4 Ihor wrote:

solved and updated! :)