| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello Colleagues, From the technology adopter’s perspective, cost-effectiveness and less PHY chip types (note not PHY types) are crucial to the success in the market. Minimizing the PHY chip types simplify the chip selection process and potentially gains large volume and optimized cost of the PHY chip. This is what 10/100/1000 standard Ethernet chip does. Supporting Auto-Negotiation is crucial to minimize the PHY chip types. I would strongly recommend the group considering the 100BASE-T1 in the scope of the auto-negotiation objective besides 10BASE-T1L.
I would also strongly recommend the group considering the technologies used in 10BASE-T1L and 100BASE-T1 when developing the proposals for 100BASE-T1L (e.g., PAM3) so that it will not increase the difficulties in implementing these PHY
types together in a single chip if the market decides it is worthwhile to do it. I am not a PHY expert, please forgive me if this is not a valid idea. Dayin XU | 徐达银 Principal Engineer | Rockwell Automation +86-21-61288390 | dyxu@xxxxxxxxxxxxxxx From: George Zimmerman <george@xxxxxxxxxxxxxxxxxxxx> [Use caution with links & attachments] Matthias – (first note – I am writing this as an individual offering my experience in PHYs, not as chair) I would suggest that compatibility has (at least) three potential dimensions:
In my mind, the first 2 types are requirements. The first type is a requirement on the interference environments, and the second is covered by our objective #4 for support of optional auto-negotiation. As to the third type of interoperability, that could be the subject of a phy proposal, and I would not want to see the phy proposal analysis preceded or short-cut because of some early-market, off-application use of 100BASE-T1 PHYs.
As an individual, I have personally seen several situations where technologies are sold into applications and installations that the phys were not designed for because “they worked” in early qualifications only to see that they did not
stand up to the test of time and breadth of installation conditions. Situations such as increased noise, aging, and the kinds of limiting specifications that we consider to and phy vendors design to are often not fully considered by such implementations and
installations. The result is a technology that does not scale, as even a small percentage of link failures can make for a problematic market environment. Therefore, I’d (personally) hold a high burden of proof to the third type of interoperability above. George Zimmerman, Ph.D. President & Principal CME Consulting, Inc. Experts in Advanced PHYsical Communications 310-920-3860 From:
stds-802-3-spep2p@xxxxxxxxxxxxxxxxx <stds-802-3-spep2p@xxxxxxxxxxxxxxxxx>
On Behalf Of Fritsche, Matthias Hello together, I have a question to the group regarding the compatibility between 100BASE-T1 and 100BASE-T1L. There is already a large amount of different PHYs for 100BASE-T1 on the market and the installed base outside vehicles is also growing. Publicly published test setups also show that today's 100BASE-T1 Phys can achieve
more than 100m channel length. With the market introduction of 100BASE-T1L PHYs in the next few years, the question will certainly arise whether the 100BASE-T1 PHYs are or can be compatible with the new 100BASE-T1L PHYs? Will this be possible? I think that
would be necessary from a market and user perspective. Thanks for your feedback in advance Very nice greetings and we see us in Berlin Matthias Best regards / Mit freundlichen Grüßen
Ethernet Connectivity - HARTING Electronics GmbH | Postfach 14 33, 32328 Espelkamp | Marienwerderstraße 3, 32339 Espelkamp |
www.HARTING.com To unsubscribe from the STDS-802-3-SPEP2P list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-SPEP2P&A=1 To unsubscribe from the STDS-802-3-SPEP2P list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-SPEP2P&A=1 To unsubscribe from the STDS-802-3-SPEP2P list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-SPEP2P&A=1 |