Software to capture and plot with the new firmwares
Re: Software to capture and plot with the new firmwares
GNUplot don't start anymore with this version and I don't get any information (values) see in the grabber.
CU, Rob
Re: Software to capture and plot with the new firmwares
Debug (date and timestamp) .txt produced?
Does it say anything?
Regards
Rob
Does it say anything?
Regards
Rob
Re: Software to capture and plot with the new firmwares
As its the new version you have to tell it each time which com port to use
(it will ask and sit there forever - till you have manually typed in COM2 and hit enter (or whatever com port is needed- it should start by listing valid ports when the app is opened)
Regards
Rob
(it will ask and sit there forever - till you have manually typed in COM2 and hit enter (or whatever com port is needed- it should start by listing valid ports when the app is opened)
Regards
Rob
Re: Software to capture and plot with the new firmwares
Is the new style with com port selection a bit confusing?
Do I need to go back to 'fixed' on com2?
What about when bluetooth is used or com2 is not available?
I need some way of letting the user choose, and cant think of a neat way that is easy and not confusing....
Suggestions?
Regards
Rob
Do I need to go back to 'fixed' on com2?
What about when bluetooth is used or com2 is not available?
I need some way of letting the user choose, and cant think of a neat way that is easy and not confusing....
Suggestions?
Regards
Rob
Re: Software to capture and plot with the new firmwares
I see, I have restart the program for a new plot.
BTW, I upload all the files to my server http://www.bucket.gompy.net/dso150 so you can see wat I get from the program.
CU, Rob
BTW, I upload all the files to my server http://www.bucket.gompy.net/dso150 so you can see wat I get from the program.
CU, Rob
CU, Rob
Re: Software to capture and plot with the new firmwares
I have 8 USB-ports and befor I use the program I have to look in the hardware to see where the TTL is connect on USB.robocog wrote:Is the new style with com port selection a bit confusing?
Do I need to go back to 'fixed' on com2?
What about when bluetooth is used or com2 is not available?
I need some way of letting the user choose, and cant think of a neat way that is easy and not confusing....
Suggestions?
I don't think at this moment it is not a problem.....if they know wat they are doing.
But first of all the program works and the files have a followup name, I'm happy
EDIT: is it not possible to hit ENTER to restart the program instead of quit the program and ESC to quit the program ?
CU, Rob
Re: Software to capture and plot with the new firmwares
DSO_Shell_v1.7.2.zip uploaded
http://www.robocog.co.uk/electronics/ds ... v1.7.2.zip
On first run it after detecting which ports it finds asks for the com port you want to use...(same as before)
It NOW saves that to a file (comport.ini)
It will NOT ask again and always use that port
To "reset" it back to asking which port - just delete the comport.ini (or hand edit it to the com port you need)
Is that a better solution?
Does it work?
(it does for me...but ...)
I will see if getting the file to stay open and re run a data grab - or quit by key press is something I can easily do
(the script is getting much bigger and more complex each re-write!!)
Having never programmed anything before I am wearing Google out asking it questions!
Regards
Rob
http://www.robocog.co.uk/electronics/ds ... v1.7.2.zip
On first run it after detecting which ports it finds asks for the com port you want to use...(same as before)
It NOW saves that to a file (comport.ini)
It will NOT ask again and always use that port
To "reset" it back to asking which port - just delete the comport.ini (or hand edit it to the com port you need)
Is that a better solution?
Does it work?
(it does for me...but ...)
I will see if getting the file to stay open and re run a data grab - or quit by key press is something I can easily do
(the script is getting much bigger and more complex each re-write!!)
Having never programmed anything before I am wearing Google out asking it questions!
Regards
Rob
Re: Software to capture and plot with the new firmwares
Well, I can only say....you doing it very well...I can't do this in the short time you learn
I try with Adroid studio, but it look likes C to program and I'n not a programmer.
Is it not possible to hit enter to restart the main program....in G(00d)O(ld)D(os)....go to 20
Any other key is exit the program.
I try with Adroid studio, but it look likes C to program and I'n not a programmer.
Is it not possible to hit enter to restart the main program....in G(00d)O(ld)D(os)....go to 20
Any other key is exit the program.
CU, Rob
Re: Software to capture and plot with the new firmwares
The spacing on the code in Python is hyper critical
eg
<code lives here:>
......<subroutine type stuff lives here>
..........<and maybe here>
......<and sometimes here>
<and it ends here again>
the issue I have is that it is all formatted right, as it is
but it now needs to ALL move over 3 or 4 lines so I can modify the code with a bit at the top and bottom for the restart thing to work, and moving EVERYTHING over without upsetting the current formatting, I cannot see a quick way of automating it
I did get it working (but only under Python, and I ran it 5 or 6 times till my desktop was full of debug/data and gnuplot files...ROFL)
If it make it a Windows exe it only works once then quits as it does before, so it fails when dong the conversion...sigh
eg
<new code to make a restart happen:>
............<all the old code needs to move here>
.................<blah blah blah>
............<end of old code>
<new code to make a restart happen>
I will have to do it manually :/
Maybe not tonight though
Regards
Rob
eg
<code lives here:>
......<subroutine type stuff lives here>
..........<and maybe here>
......<and sometimes here>
<and it ends here again>
the issue I have is that it is all formatted right, as it is
but it now needs to ALL move over 3 or 4 lines so I can modify the code with a bit at the top and bottom for the restart thing to work, and moving EVERYTHING over without upsetting the current formatting, I cannot see a quick way of automating it
I did get it working (but only under Python, and I ran it 5 or 6 times till my desktop was full of debug/data and gnuplot files...ROFL)
If it make it a Windows exe it only works once then quits as it does before, so it fails when dong the conversion...sigh
eg
<new code to make a restart happen:>
............<all the old code needs to move here>
.................<blah blah blah>
............<end of old code>
<new code to make a restart happen>
I will have to do it manually :/
Maybe not tonight though
Regards
Rob
Re: Software to capture and plot with the new firmwares
Done!
DSO Shell grabberv1.7.3.zip uploaded
It now always loops back to the start ready for another data grab till you press the q key (and enter)
any other key will make it start again from the beginning
It was quite easy in the end (...nearly as easy as "goto 10"!)
I found a way of moving the whole code over the right amount in just a few keystrokes!
http://www.robocog.co.uk/electronics/ds ... v1.7.3.zip
Let me know
Is the comport ini thing working OK for you?
I think it was the cleanest method for now
Not sure about having so much data spat out - how much do you need?
The gnuplot.txt data and the gnuplot.plt yes they deserve to be timestamped and saved / not over written each run of the software
the debug.txt, header.txt and all_data.txt though?
Are they of much use?
Would just saving the last instance be good enough ?
Are they even needed?
Put them as options in an ini file?
Give me your thoughts
Regards
Rob
DSO Shell grabberv1.7.3.zip uploaded
It now always loops back to the start ready for another data grab till you press the q key (and enter)
any other key will make it start again from the beginning
It was quite easy in the end (...nearly as easy as "goto 10"!)
I found a way of moving the whole code over the right amount in just a few keystrokes!
http://www.robocog.co.uk/electronics/ds ... v1.7.3.zip
Let me know
Is the comport ini thing working OK for you?
I think it was the cleanest method for now
Not sure about having so much data spat out - how much do you need?
The gnuplot.txt data and the gnuplot.plt yes they deserve to be timestamped and saved / not over written each run of the software
the debug.txt, header.txt and all_data.txt though?
Are they of much use?
Would just saving the last instance be good enough ?
Are they even needed?
Put them as options in an ini file?
Give me your thoughts
Regards
Rob