Skip to Navigation
Home
  • Company
    • Quick Facts
    • Board of Directors
    • Management Team
    • Press Releases
    • News Coverage
    • Newsletter
    • Careers
    • Articles
    • Ember Chronology
    • Contact Us
  • Products
    • ZigBee Chips
    • ZigBee Software
    • ZigBee Development Tools
    • Documentation
  • Buy
    • Digi-Key (Online)
    • Distributors
  • Applications
    • AMI & AMR
    • Integrated Home Automation
    • Building Automation
    • Others
  • ZigBee
    • About ZigBee
    • Ember & ZigBee
    • ZigBee FAQ
    • Download Specifications
    • ZigBee Events
  • Partners
  • Support
    • Training
  • Events
Home › FAQs

Why does port 4901 on the InSight Adapter show bad data?

Categories:
  • Tools : ISD, ISA

When connected to the InSight Adapter via telnet to port 4901, but my prints and the EM250 answers are gibberish, just like you get when you are connected with the wrong baud rate. How do I change the baud rate?

Try first:

You must configure the InSight Adapter baud rate to match the baud rate configured in the application -- this is because the InSight Adapter is just a translator between serial and telnet.
The Ember sample applications use 19200 as the baud rate, but your application may have set a different baud rate. You can set the proper baudrate (19200) for this application in the InSight Adapter administrative port configuration: telnet to Port 4902, type "config" to see the settings, then type "port 1 19200" to set port 1 to 19200 baud.

Try second:

(For the EM250 breakout board): The jumpers on the breakout board should be set accordingly for Ethernet I/O (J19, J20 open; J18 shorted to GND; GPIO9 and GPIO10 bridged to the extended debug connector on J5).

Finally, if there is still a problem:
Test the interaction with the device via a direct serial connection through the DB-9 port, to see if the trouble still occurs. If the problem still occurs, it is likely a configuration problem (perhaps you configured the baud rate differently than you thought?) or a hardware problem. If the problem does not occur, then the InSight Adapter configuration should be re-examined.

  • Login to post comments
  • Printer-friendly version

Search

FAQs

  • All (162)
  • Software : Embedded (62)
  • Software : Networking (70)
  • Hardware : Design (22)
  • Hardware : Manufacturing (10)
  • Tools : Dev Boards (2)
  • Tools : ISD, ISA (20)
  • Tools : xIDE (6)
  • Tools : Other (7)
  • ZigBee (1)
  • Change Notification (0)
Primary links
  • Developer Blog
  • Documentation
    • Release Notes
  • Contributed Software
  • FAQs
  • Change Notifications
  • Training
Portal
  • My Account
  • Search
User login
  • Request new password

Company | Products | Buy | Applications | ZigBee | Partners | Support | Events | Contact Us

©2007-2008 Ember Corporation | All rights reserved | Privacy