Technical Mac HP48gx connectivity problem with USB to serial converter



#2

Like the 5 points (commandments) for this group.

I am posting here on the suggestion of Wayne Brown, who I met on the comp.sys.hp48.

I have in the past connected my HP48sx calculator to an old mac via a
serial port, no problems using Link 48 software.

I have been trying to do the same unsuccessfully using a New Motion
USB to serial port adaptor to a G4 powerbook running OS 9.2.2, with
Carbon Lib 1.6. I have also tried on a G3 powerbook with same OS
setup.

There is some initial indication of communication on the HP
calculater.. with the following..

HP: <connecting> <processing command> <connecting> <processing
command> later ..<retry 1> <retry 2>,... then <timeout>.

With the attempted exchange process between the HP 48 sx and HP Link 48 software program, the Link software reports the error (result code 55) Couldn't complete the last command because the connection timed out. Please check your connections.... etc (all fine, HP calculator in server mode etc..)

Within the Link 48 software, program continues to report no
connection. Have tried many combinations of set up within Link 48
software and the control panel for iDock USB to serial dual port
adapter from NewMotion. No success.

I thought someone familiar with the Kermit exhange process may have
some suggestions as to a solution.

I have also tried connecting through Appleworks (software on Macs) with no success.


The USB serial converter software has an option of 5V on pin 9. Not sure what this is about, and if I want to use it? This is a second technical question I think?

In response to my comp.sys.hp48 posting, Bill Graves made the following comments about this problem....

This is my guess ....

1. The round trip time for serial communication between the PC and the Calc is pretty short IF the calc does not have to do much.

2. Although USB has a much higher peak transfer rate, it seems like the total round trip time can be a little longer for the one
character server commands.

3. In the case we are discussing, it is a little worse because the characters go through USB then serial then to the calc then back
as serial and then back to USB.

4. Again I think the total throughput rate might be fine, the round trip time for a single message might be too long.

5. This might cause the link program to time out because it has been coded for the shorter serial, round trip times.

(...full posting on comp.sys.hp48 4 August 2003)

For those technically minded I have added below a USB Events List, accessed from Apple System Profiler. (Powerbook started up and Link 48 program begun, with USB to serial converter and HP48sx already connected ready. - keeping this list as short as possible!)

I am consious this makes for a long posting, however on the other hand putting all information into the one posting can be time efficient interms of another scanning to see if they have something to offer.

I am having trouble posting it formatted by individual line. Sorry.

Cameron downunder.


1.917: Expert - Initializing ROM based USB Expert 1.5.6
1.937: [ 123456789]: UIM - keylargo found -2147483648
1.937: [ 123456789]: UIM - wake handler enqueued 0
1.946: [ 123456789]: UIM - keylargo found -2147483648
1.947: [ 123456789]: UIM - wake handler enqueued 0
2.011: [ 123456789]: UIM - UIMEndpointDelete: Could not find
endpoint -6987
2.071: [ 123456789]: UIM - UIMEndpointDelete: Could not find
endpoint -6987
2.084: [ 75575988]: Expert - LoadClassDriver: USBHub1Apple - calling
driver initialize routine... 0
2.084: [ 75575988]: Expert - LoadClassDriver: USBHub1Apple - driver
initialization completed 0
2.085: [ 75575988]: Driver - Externally powered Hub attached - power
supply good 0
2.097: [ 75576245]: Expert - LoadClassDriver: USBHub1Apple - calling
driver initialize routine... 0
2.097: [ 75576245]: Expert - LoadClassDriver: USBHub1Apple - driver
initialization completed 0
2.098: [ 75576245]: Driver - Externally powered Hub attached - power
supply good 0
3.355: [ 0]: Expert - Bus Enumeration using ROM-based drivers
(mSec): 1299
3.359: [ 0]: Expert - Registered with Native Power Manager 0
34.201: [ 597]: Expert - LoadUSBShim: Unable to register
fragment! -2805
34.333: [-1610604544]: UIM - All ports disconnected, stopping
clocks 0
34.337: [-1610608640]: UIM - All ports disconnected, stopping
clocks 0
35.344: [ 0]: Expert - Bus Enumeration using disk-based
drivers (mSec): 1016
120.011: [ 75575988]: Driver - Hub Driver - Device found, calling
USBHubAddDevice. Port 1
120.181: [ 0]: USL - processDelayQ delayQueueChanged,
breaking 0
121.142: [ 75576502]: Expert - LoadClassDriver: USBBootstrap -
calling driver initialize routine... 0
121.164: [ 75576502]: Expert - LoadClassDriver: USBBootstrap -
driver initialization completed 0
121.749: [ 75575988]: Driver - Hub driver - Removing dead device:
132104
121.750: [ 0]: USL - processDelayQ delayQueueChanged,
breaking 0
121.753: [ 75576502]: Expert - Unable to locate device descriptor:
-2538
121.753: [ 75576502]: Expert - Finalize returned: 0
121.783: [ 0]: USL - processTimeoutQueue found dead queue
element - X 0
122.265: [ 75575988]: Driver - Hub Driver - Device found, calling
USBHubAddDevice. Port 1
122.425: [ 0]: USL - processDelayQ delayQueueChanged,
breaking 0
122.953: [ 75576759]: Expert - LoadClassDriver: iDock_Driver -
calling driver initialize routine... 0
122.955: [ 75576759]: Expert - LoadClassDriver: iDock_Driver -
driver initialization completed 0
123.012: [ 75576759]: USL - - USBDeviceRequest called for
Set_Config. Use USBSetConfiguration instead 75576759
123.021: [ 75576759]: USL - - Obsolete funtion, USBOpenPipe,
called 75576759
123.021: [ 75576759]: USL - - Obsolete funtion, USBOpenPipe,
called 75576759
123.025: [ 75576759]: USL - - Obsolete funtion, USBOpenPipe,
called 75576759
123.025: [ 75576759]: USL - - Obsolete funtion, USBOpenPipe,
called 75576759
123.025: [ 75576759]: USL - - Obsolete funtion, USBOpenPipe,
called 75576759
364.062: [ 0]: USL - Stalling pipe 1174716422
364.074: [ 0]: USL - Stalling pipe 1174716422
364.086: [ 0]: USL - Stalling pipe 1174716422
364.098: [ 0]: USL - Stalling pipe 1174716422
364.110: [ 0]: USL - Stalling pipe 1174716422
364.122: [ 0]: USL - Stalling pipe 1174716422
364.134: [ 0]: USL - Stalling pipe 1174716422
364.146: [ 0]: USL - Stalling pipe 1174716422
364.149: [ 75575988]: Driver - Hub driver - Removing dead device:
132104
364.155: [ 75575988]: Driver - Hub driver - Connection bounce:
-1744500480
364.155: [ 0]: USL - processDelayQ delayQueueChanged,
breaking 0
364.158: [ 75576759]: Expert - Unable to locate device descriptor:
-2538
364.158: [ 0]: USL - Obsolete function
USBClosePipeByReference called 1174718474
364.158: [ 0]: USL - Obsolete function
USBClosePipeByReference called 1174717961
364.158: [ 0]: USL - Obsolete function
USBClosePipeByReference called 1174716422
364.159: [ 0]: USL - Obsolete function
USBClosePipeByReference called 1174717448
364.159: [ 0]: USL - Obsolete function
USBClosePipeByReference called 1174716935
364.160: [ 75576759]: Expert - Finalize returned: 0
364.197: [ 0]: USL - processTimeoutQueue found dead queue
element - X 0
367.487: [ 75575988]: Driver - Hub driver - Connection bounce:
-1744500480
367.584: [ 75575988]: Driver - Hub Driver - Device found, calling
USBHubAddDevice. Port 1
367.645: [ 0]: USL - processDelayQ delayQueueChanged,
breaking 0
368.527: [ 75577016]: Expert - LoadClassDriver: USBBootstrap -
calling driver initialize routine... 0
368.530: [ 75577016]: Expert - LoadClassDriver: USBBootstrap -
driver initialization completed 0
369.097: [ 75575988]: Driver - Hub driver - Removing dead device:
132104
369.098: [ 0]: USL - processDelayQ delayQueueChanged,
breaking 0
369.101: [ 75577016]: Expert - Unable to locate device descriptor:
-2538
369.101: [ 75577016]: Expert - Finalize returned: 0
369.112: [ 0]: USL - processTimeoutQueue found dead queue
element - X 0
369.602: [ 75575988]: Driver - Hub Driver - Device found, calling
USBHubAddDevice. Port 1
369.760: [ 0]: USL - processDelayQ delayQueueChanged,
breaking 0
370.280: [ 75577273]: Expert - LoadClassDriver: iDock_Driver -
calling driver initialize routine... 0
370.282: [ 75577273]: Expert - LoadClassDriver: iDock_Driver -
driver initialization completed 0
370.294: [ 75577273]: USL - - USBDeviceRequest called for
Set_Config. Use USBSetConfiguration instead 75577273
370.303: [ 75577273]: USL - - Obsolete funtion, USBOpenPipe,
called 75577273
370.303: [ 75577273]: USL - - Obsolete funtion, USBOpenPipe,
called 75577273
370.307: [ 75577273]: USL - - Obsolete funtion, USBOpenPipe,
called 75577273
370.307: [ 75577273]: USL - - Obsolete funtion, USBOpenPipe,
called 75577273
370.307: [ 75577273]: USL - - Obsolete funtion, USBOpenPipe,
called 75577273


Possibly Related Threads...
Thread Author Replies Views Last Post
  Prime Connectivity Kit Suggestion toml_12953 1 231 12-06-2013, 10:41 PM
Last Post: Michael de Estrada
  Gathering USB dumps for Connectivity Kit <-> 39gII communication... debrouxl 2 282 12-01-2013, 12:59 PM
Last Post: Marcus von Cube, Germany
  HP Prime Connectivity software in Virtualbox/wine Chris Pem10 2 250 11-22-2013, 02:20 PM
Last Post: Chris Pem10
  HP-Prime firmware update on a Mac Javier Goizueta 5 397 11-15-2013, 10:52 AM
Last Post: Javier Goizueta
  HP Prime - Connectivity kit purpose bluesun08 2 211 11-11-2013, 10:37 AM
Last Post: Michael de Estrada
  Connectivity Kit Les Koller 1 194 11-10-2013, 06:38 PM
Last Post: Michael de Estrada
  Hp PRIME - how to send a list to the connectivity Kit giancarlo 1 219 11-10-2013, 11:50 AM
Last Post: Tim Wessman
  Proper location for files on the PC for Connectivity Kit ,etc. Harold A Climer 8 473 10-23-2013, 02:43 AM
Last Post: Marcus von Cube, Germany
  HP Prime vs. 39gII Connectivity Kit Marcus von Cube, Germany 3 299 10-09-2013, 05:44 PM
Last Post: Marcus von Cube, Germany
  HP48GX screen replacement Francisco Quiles 9 497 10-03-2013, 09:17 PM
Last Post: Francisco Quiles

Forum Jump: