• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Packet Logger interpretation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Packet Logger interpretation

  • Subject: Packet Logger interpretation
  • From: Ron Wagner <email@hidden>
  • Date: Wed, 9 Jan 2008 17:05:37 -0500

Hi,

I have a device that I'm having trouble with. It looks for a named serial service which my software supplies, but the problem is happening long before my software gets involved. Seems there is trouble just asking for the list of services. In the attached PacketLogger log, you can see the ServiceSearchAttributeRequest being issued, but then it is followed by a Disconnection Request.

So my questions are:

Who is issuing that Disconnection Request, the device or the computer, and why is the list of serial services not being returned (not even the standard built-in services)?

How do I tell who is saying what in the log? Do the red and blue color codings indicate this somehow?

This log is from a new version of the device firmware. On Tiger, the older firmware returned a part of the serial services list but apparently didn't handle the ContinuationState correctly, so the Mac returned the same portion of the complete list when more data was requested. On Leopard, the old firmware behaved as the new firmware does, not really getting anywhere from the start. The firmware change was to correct the ContinuationState problem, but now I can't get any of the  serial service list to be returned.

The device is a bathroom scale. It does work on Windows, maybe by dumb luck, but also because the manufacturer develops and tests their firmware with Windows. I was able to figure out the ContinuationState problem with the SerialSearchAttributeRequest with the previous firmware under Tiger, but not being a Bluetotooth expert I'm a little stumped on this. Could someone take a look at the logs and let me know if they see anything wrong that I don't see? If I can confirm that it is NOT the Mac's fault, I can arrange to meet with the firmware engineer for a day to see if we can solve this.

Thanks

Ron Wagner
Wagner Technologies LLC
Tolland CT  
860-872-0053
email@hidden


Logs from Leopard and Tiger attached.


Attachment: Leopard Log.pklg
Description: Binary data

Attachment: Tiger Log.pklg
Description: Binary data

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
  • Prev by Date: Re: Cycle Power?
  • Next by Date: Re: OBEXFileTransferServices reporting current path wrongly?
  • Previous by thread: Re: Cycle Power?
  • Next by thread: Is -registerForChannelCloseNotification: necessary if I have a delegate?
  • Index(es):
    • Date
    • Thread