- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: Serial device issues
HPE 9000 and HPE e3000 Servers
1752353
Members
5536
Online
108787
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2003 01:25 AM
тАО10-31-2003 01:25 AM
For the last 7 months or so, we have been struggling trying to configure a Simplex time clock, a Toledo scale and a Telxon hand-held unit on an A500 running 11i, and an 8 port fan-out mux.
Currently, these are functioning on an NCR 3430 (SVR4), and we are trying to port them over to HP-UX.
Also have a Wyse term and a line printer which we were able to configure.
We cannot seem to communicate to said devices (using homegrown c programs, by the way). I've verified that our ports are good/functional.
At this point, we're not sure if our problem is with the cable pinouts, the c programs, or both. We suspect that the reason the Wyse and printer are working is because they have their own drivers, where we might be writing our own for the other devices.
We have tried virtually every pin-out combination, using both a break-out box and protocol analyzer/break-out box software, and hired two consultants.
We are going nowhere fast, and the deadline on this project is looming.
Would appreciate any hints/ideas.
Thanks-
Stace
Currently, these are functioning on an NCR 3430 (SVR4), and we are trying to port them over to HP-UX.
Also have a Wyse term and a line printer which we were able to configure.
We cannot seem to communicate to said devices (using homegrown c programs, by the way). I've verified that our ports are good/functional.
At this point, we're not sure if our problem is with the cable pinouts, the c programs, or both. We suspect that the reason the Wyse and printer are working is because they have their own drivers, where we might be writing our own for the other devices.
We have tried virtually every pin-out combination, using both a break-out box and protocol analyzer/break-out box software, and hired two consultants.
We are going nowhere fast, and the deadline on this project is looming.
Would appreciate any hints/ideas.
Thanks-
Stace
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2003 03:21 AM
тАО10-31-2003 03:21 AM
Solution
I am all but certain that you are making this much harder than it is; serial connections are generally tedious but not difficult. Because you didn't bother to identify the exact MUX and fan-out cable, it's difficult to be precise. In any event, go to docs.hp.com and enter "Multiplexer Family" as a search string.
One thing to note is that if your fan-out cable is RJ-45, it's probably a 10-pin connector rather than the far more common 8. HP makes an adapter cable that will go from this odd 10-pin RJ45 to a more common DB25P but even in this case the pin-outs on the DB-25 are non-standard. Getting your hands on the Multiplexer Family Cabling documentation is essential.
You will not need an addional driver although you may need to create/use device nodes with the proper minor device numbers. Man 7 termio and pay attention to the section on minor device numbers.
One of my favorite ways to debug this is to use kermit. Edit inittab and make sure that the port in question is set to 'off' and then issue an init q command. Now start kermit and issue a 'set line' command. You can also issue 'set flow', 'set speed', 'set parity', ... and finally issue a 'connect'.
On occasion, I go to another terminal session and do stty commands on the same port that kermit is trying to use.
e.g. stty -crts rtsxoff ctsxon < /dev/ttyd0p3
Once you know what additional commands are needed to use the port, coding any changes is your C application becomes quite simple.
One thing to note is that if your fan-out cable is RJ-45, it's probably a 10-pin connector rather than the far more common 8. HP makes an adapter cable that will go from this odd 10-pin RJ45 to a more common DB25P but even in this case the pin-outs on the DB-25 are non-standard. Getting your hands on the Multiplexer Family Cabling documentation is essential.
You will not need an addional driver although you may need to create/use device nodes with the proper minor device numbers. Man 7 termio and pay attention to the section on minor device numbers.
One of my favorite ways to debug this is to use kermit. Edit inittab and make sure that the port in question is set to 'off' and then issue an init q command. Now start kermit and issue a 'set line' command. You can also issue 'set flow', 'set speed', 'set parity', ... and finally issue a 'connect'.
On occasion, I go to another terminal session and do stty commands on the same port that kermit is trying to use.
e.g. stty -crts rtsxoff ctsxon < /dev/ttyd0p3
Once you know what additional commands are needed to use the port, coding any changes is your C application becomes quite simple.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2003 03:58 AM
тАО10-31-2003 03:58 AM
Re: Serial device issues
Hi Stace,
HP commonly uses 8-pin RJ45 connectors for its LAN cables, but when it comes to an EISA or PCI panel, the RJ-45 connectors use a 10-pin configuration. So, pin 1 (on an 8-pin connector) is really pin 2 (on the 10-pin connector).
You'll find the correct pinout for all EISA and PCI connection by going to the following URL:
http://docs.hp.com/hpux/onlinedocs/5966-8703/5966-8703.html
Hope that helps,
Ross
HP commonly uses 8-pin RJ45 connectors for its LAN cables, but when it comes to an EISA or PCI panel, the RJ-45 connectors use a 10-pin configuration. So, pin 1 (on an 8-pin connector) is really pin 2 (on the 10-pin connector).
You'll find the correct pinout for all EISA and PCI connection by going to the following URL:
http://docs.hp.com/hpux/onlinedocs/5966-8703/5966-8703.html
Hope that helps,
Ross
Retired HP
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP