-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
General discussion #1
Comments
I didn't understand you very well. Do you mean add COM port name in "open" action info? |
Right now you must specify the port to use in plugin settings only. I am suggesting we have a parameter in the Serial.Open action which specifies which port to open. The user might want to talk to more than one device. Also if possible it would be good to connect to first active port when the port is not specified. |
OK, now I understand. Will add this. |
The difficult part is if we want to connect to two serial ports at the same
time.
It should be possible though.
I mention it now because it might be a pain to change it later.
…On Tue, Aug 8, 2017 at 12:47 PM, NAITcompany ***@***.***> wrote:
OK, now I understand. Will add this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APFxFzHxa7eyfKWVf6TGG7a2YrG2Fnd3ks5sWJEtgaJpZM4Ow9qk>
.
|
It means, that we need to specify port name in all actions. Or, "Serial.SelectNew", that will either select port if it exists, or create new if it's not. (Like RoboB action) |
Yes or it could just use whichever port was last used in "connect" when the
user does not specify which port.
Since connect will do nothing if already connected to that port?
…On Tue, Aug 8, 2017 at 1:12 PM, NAITcompany ***@***.***> wrote:
It means, that we need to specify port name in all actions.
So it might be better if we create action "Serial.Select", that will
select port from opened ports, and after this, user will work with selected
port.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APFxF9LVlcQ5aE0DtCVgDbGcRzhrfWO2ks5sWJbtgaJpZM4Ow9qk>
.
|
Yes, serial.open action anyway works before doAction switch, when port already connected, it "doing nothing". |
I almost rebuilt logic for connecting to countless ports. In "open" action user need to specify three options: port name, bauds rate and DTR signal activity. Also I added action "GetPorts" that moves list of ports to LastResult. And I think I can add list of all and list of opened ports in plugin settings window. So this 'll be another BIG update! |
Sounds awesome!
…On Aug 9, 2017 5:59 AM, "NAITcompany" ***@***.***> wrote:
I almost rebuild logic for connecting to countless ports.
Now user can"Select" port, then actions "write", "upload" and "close" will
work with selected port.
Also in "Select" action second option is "Auto-scan Arduino".
In "open" action user need to specify three options: port name, bauds rate
and DTR signal activity.
These three options was removed from plugin settings window.
Also I added action "GetPorts" that moves list of ports to LastResult.
This action have two options: "Only Opened ports" and "Friendly port
names".
And I think I can add list of all and list of enabled ports in plugin
settings window.
So this 'll be another BIG update!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APFxFx8hdAUNhj-pRsX4XSehJ-QaKLzbks5sWYL9gaJpZM4Ow9qk>
.
|
Committed update. Tested it, errors not found, but it would be better if another people test it too. |
Take a look at the class "util.cs". (for info only) It shows how to get non-arduino serial port info. From there we need to decide based on name. I was thinking we take anything that does not match "Communications Port" since this is usually not connected to anything. A better option might be to let the user specify the port to open by a sub-match (string.contains() or maybe using a regular expression pattern) of the name/description. So they could open either "COM6" or they could open using "Prolific" or "Mega 2560" etc. I think this would be the most powerful/easy/flexible, especially if they want to target a specific device even if the port # has changed around after being plugged into a different USB port etc. We could also use the ManagementObjectCollection above when showing available ports on the plugin settings page to provide more information than just the port number. We could show name, and maybe other info if useful. |
For me "Communications Port" shows as "Последовательный порт", so this "tag" depends on OS language. |
Good point. I forgot about that.
Let's use RegEx since it's just as easy (you can simply enter a substring
as the pattern) and much more powerful if you want to be more precise. If
you implement it as substring I will modify it to use RegEx later.
I think this should be part of the "Serial.Open" action as the first
parameter.
You can enter any of these following for the first parameter:
COM4
duino
<blank>
if it's blank it will just use the first port it finds.
I don't think we need a separate Open and Select action though. Do we?
…On Sun, Aug 13, 2017 at 12:34 PM, NAITcompany ***@***.***> wrote:
For me "Communications Port" shows as "Последовательный порт", so this
"tag" depends on OS language.
But opening port by substring is realy powerful, I'm working on it now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APFxFzQ9BklqaKMDIWWHnf7sSfANM_OIks5sXyV_gaJpZM4Ow9qk>
.
|
Probably yes. If I'll have free time I'll modify code and it will be ready tomorrow. |
Update ready. Merged Open and Select actions, now port opening by RegEx pattern. Updated GetPorts action. |
Nice. Will check later. I'm away for most of today.
…On Mon, Aug 14, 2017 at 6:49 AM, NAITcompany ***@***.***> wrote:
Update ready. Merged Open and Select actions, now port opening by RegEx
pattern. Updated GetPorts action.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APFxFxkbw-C7IOoetVTsGyylIu_9ZoKCks5sYCYjgaJpZM4Ow9qk>
.
|
I made a full-ready release, think we can add it to VC package. |
OK. I will try to test it as soon as possible. I've been super busy with
another project over the last week but I should have a bit of free time
over the next few days.
Thanks for your hard work!
J
…On Tue, Aug 29, 2017 at 3:35 PM, Nikitin Ilya ***@***.***> wrote:
I made a full-ready release, think we can add it to VC package.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APFxFxGCaXXgUT6lnAOYa-ZloSRhP_cIks5sdGgAgaJpZM4Ow9qk>
.
|
I released 1.0.4.5 version, with highlighting current opened port in plugin window, I thought that it is not comfortable to use "open / select" in 1 action, because in modem connection I need to add more options to "open" action. |
I think it's ok to make changes to the actions still.
…On Sep 17, 2017 12:06 PM, "Nikitin Ilya" ***@***.***> wrote:
I released 1.0.4.5 version, with highlighting current opened port in
plugin window,
And also some bugfixes with opening/selecting.
In next release I'm planning to implement LPT (printer) port and modem
port connection.
I thought that it is not comfortable to use "open / select" in 1 action,
because in modem connection I need to add more options to "open" action.
It's late to separate actions, or not?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APFxF5ohFXAYD2insUlsjJ1jELK7Fs-2ks5sjUN2gaJpZM4Ow9qk>
.
|
Would it make more sense to all the user to specify the com port when connecting?
The text was updated successfully, but these errors were encountered: