ghost
commented
3 years ago Tagging subscribers to this area: @dotnet/area-system-io See info in area-owners.md if you want to be subscribed.
Issue Details
_This issue has been moved from [a ticket on Developer Community](https://developercommunity.visualstudio.com/t/Input-SerialPort-binary--byte-value-17-H/1419827)._ --- I am communicating with a device via SerialPort. I have an 11 Byte frame with a. in byte 9 and 10 I receive a counter and this when it matches the value 17 Hex (11) omits the byte and the frame is cut --- ### Original Comments #### null on 5/12/2021, 08:23 PM:
Just double confirm with you, Is this a problem with Visual Studio?
Does this reproduce for all project or specific project? If it’s reproduce with the specific project, which project do you use? It would be very helpful if you can provide a screenshot of this issue. Thanks for your help!
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
#### Amy Li [MSFT] on 5/14/2021, 04:37 AM:Hi Manel,
In order to investigate this issue further could you please share your sample app for us.
In addition, this problem occurs on which VS version? You can install the latet VS from here: https://visualstudio.microsoft.com/downloads/ to check whether it still reproduced.
Thanks for help us build a better visual studio!
#### Manel Juni Marín on 5/14/2021, 07:54 AM: (private comment, text removed) #### Feedback Bot on 5/19/2021, 08:02 PM:We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
#### Manel Juni Marín on 6/25/2021, 03:27 AM:Good morning, I observe that you are passing days without having news on the subject. Can you tell me news?
Thank you!
Thank you for taking the time to log this issue! Did you still reproduce this issue in the latest stable version of Visual Studio installed from https://visualstudio.microsoft.com/downloads ?
If so, in order for us to investigate this further, could you please provide repro steps, a more detailed description of the faulty behavior and the actions you were taking when the issue appeared to help us better understand this scenario? It would be very helpful if you could provide some screenshots of this problem.
We look forward to hearing from you!
#### Manel Juni Marín on 9/5/2021, 00:10 PM: (private comment, text removed) #### Feedback Bot on 8/31/2021, 07:20 PM: We will close this report in 14 days because we don’t have enough information to investigate further. To keep the problem open, please provide the requested details. #### Feedback Bot on 9/8/2021, 11:02 PM:We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
--- ### Original Solutions #### Jeff Handley [MSFT] solved on 9/21/2021, 10:24 PM, 0 votes:Please see the previous comment about the root cause being in a different component. Thank you.
#### Manel Juni Marín on 9/21/2021, 11:20 PM:Can you explain the reason for its closure, please
#### Manel Juni Marín on 9/28/2021, 11:58 PM:In the event that you do not see the error I invite you to perform a remote session to show you the detail. If, on the other hand, you consider that this problem does not derive from your department, give instructions to channel it in the right place. Thank you
#### Mila Zhou[MSFT] solved on 5/19/2021, 01:34 AM, -1 votes:Posted by Amy Li :Thank you for your valuable feedback. Even though the issue you reported is surfacing in Visual Studio, we have determined it is caused by an issue in Siemens. Please report directly to the component provider. For your convenience here is a link: https://new.siemens.com/ca/en/products/buildingtechnologies/customer-feedback.html where the issue can be submitted.
#### Manel Juni Marín on 5/19/2021, 03:50 AM:I have performed the reception broadcast with two Windows interlocutors in Visual Studio 2019 between 2 ports of the same computer and the result also shows the same error. In this case, no external equipment has intervened. I await your suggestions
| Author: | vsfeedback |
|---|---|
| Assignees: | - |
| Labels: | `area-System.IO`, `untriaged` |
| Milestone: | - |
jeffhandley
This issue has been moved from a ticket on Developer Community.
I am communicating with a device via SerialPort. I have an 11 Byte frame with a. in byte 9 and 10 I receive a counter and this when it matches the value 17 Hex (11) omits the byte and the frame is cut
Original Comments
null on 5/12/2021, 08:23 PM:
Just double confirm with you, Is this a problem with Visual Studio?
Does this reproduce for all project or specific project? If it’s reproduce with the specific project, which project do you use? It would be very helpful if you can provide a screenshot of this issue. Thanks for your help!
Manel Juni Marín on 5/13/2021, 01:53 AM:
(private comment, text removed)
Feedback Bot on 5/13/2021, 02:44 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Amy Li [MSFT] on 5/14/2021, 04:37 AM:
Hi Manel,
In order to investigate this issue further could you please share your sample app for us.
In addition, this problem occurs on which VS version? You can install the latet VS from here: https://visualstudio.microsoft.com/downloads/ to check whether it still reproduced.
Thanks for help us build a better visual studio!
Manel Juni Marín on 5/14/2021, 07:54 AM:
(private comment, text removed)
Feedback Bot on 5/19/2021, 08:02 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Manel Juni Marín on 6/25/2021, 03:27 AM:
Good morning, I observe that you are passing days without having news on the subject. Can you tell me news?
Thank you!
Tracy Wang [MSFT] on 8/23/2021, 02:00 AM:
Thank you for taking the time to log this issue! Did you still reproduce this issue in the latest stable version of Visual Studio installed from https://visualstudio.microsoft.com/downloads ?
If so, in order for us to investigate this further, could you please provide repro steps, a more detailed description of the faulty behavior and the actions you were taking when the issue appeared to help us better understand this scenario? It would be very helpful if you could provide some screenshots of this problem.
We look forward to hearing from you!
Manel Juni Marín on 9/5/2021, 00:10 PM:
(private comment, text removed)
Feedback Bot on 8/31/2021, 07:20 PM:
We will close this report in 14 days because we don’t have enough information to investigate further. To keep the problem open, please provide the requested details.
Feedback Bot on 9/8/2021, 11:02 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Original Solutions
Jeff Handley [MSFT] solved on 9/21/2021, 10:24 PM, 0 votes:
Please see the previous comment about the root cause being in a different component. Thank you.
Manel Juni Marín on 9/21/2021, 11:20 PM:
Can you explain the reason for its closure, please
Manel Juni Marín on 9/28/2021, 11:58 PM:
In the event that you do not see the error I invite you to perform a remote session to show you the detail. If, on the other hand, you consider that this problem does not derive from your department, give instructions to channel it in the right place. Thank you
Mila Zhou[MSFT] solved on 5/19/2021, 01:34 AM, -1 votes:
Posted by Amy Li :Thank you for your valuable feedback. Even though the issue you reported is surfacing in Visual Studio, we have determined it is caused by an issue in Siemens. Please report directly to the component provider. For your convenience here is a link: https://new.siemens.com/ca/en/products/buildingtechnologies/customer-feedback.html where the issue can be submitted.
Manel Juni Marín on 5/19/2021, 03:50 AM:
I have performed the reception broadcast with two Windows interlocutors in Visual Studio 2019 between 2 ports of the same computer and the result also shows the same error. In this case, no external equipment has intervened. I await your suggestions