HP48 sx connecting problems to Powerbook G4 via NewMotion USB-serial adapter - technical challenge.
Cameron Aust
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>.
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 Apple works with no success.
USB Events List from Apple System Profiler follows.
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
Cameron Aust
Further information to the previous post. With the attempted exchange
process between the HP 48 sx and HP Link 48 software program, the
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..)
I know my original post was long, however I felt it best to include
the USB log on this occassion so another with technical knowledge can
skim and say .. I can see where this guy's problem is, or
alternatively skim and move on ..
Cameron downunder.
William Graves
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.
I would suggest using Conn4x from HPCalc.org but its server will not work on the SX calc. also I know the current version at
HPCalc.org has a few bugs.
-- - - - - - - - - - - - - - - - -
Bill Graves RKBA!
bgr...@ix.netcom.com
"Cameron Aust" <contact...@yahoo.co.uk> wrote in message news:ed3e5ee5.03080...@posting.google.com...
Cameron Aust
Valued your reply.
I have gone to the HPCalc.org site and downloaded Conn4x. I am running
into difficulties which I suspect may be due to using a Mac. Some
versions on this site are clearly for windows. PC can mean Mac, though
I suspect here not.
I feel I am missing some "overview" information of how to access, load
Conn4x on the Mac and HP 48 sx. I found a Netscape file titled Index
within the HelpConn4x files. I have opened this and the Index links
(if they should be there linking to the other text files) do not come
up. I have browsed around and opened a number of the other files as
text and they seem to be intended to be referenced by a browser.
I feel I am missing something, hopefully nothing to obvious, to go
this direction effectively.
Am I correctly interpreting this situation as a .. I am using a Mac -
I really should switch, problem?
I have been reading you explanation - valued.
Re 2. When I have connected, it has had quite a few menu variable
names to transfer over to the Link 48 program window where it lists
the current HP list of variables. Would this change the timing issue
you raise, or the single character commands - time issue still apply.
( I admit I am a little out of my depth technically here, doing my
best). Does this information change your perception of the problem.
Also, I am not quite sure of the implications of ".. its server will
not work on the SX calc." re Conn4x.
Any other workarounds re set up within HP and Link 48 that I could try
in view of your perceptions of the problem. Alternatively, guidance on
how to access Conn4x for a Mac equally valued, if I have not been
stupidly missing something. (I am going to be rather redfaced if the
Mac issues is not the problem ... spent quite some time trying.)
Very much valued your post.
Thank you.
Cameron Downunder.
Bruce Horrocks
In message <ed3e5ee5.03080...@posting.google.com>, Cameron
Aust <contact...@yahoo.co.uk> writes
>Any other workarounds re set up within HP and Link 48 that I could try
>in view of your perceptions of the problem. Alternatively, guidance on
>how to access Conn4x for a Mac equally valued, if I have not been
>stupidly missing something. (I am going to be rather redfaced if the
>Mac issues is not the problem ... spent quite some time trying.)
I've never bothered with Conn4x for the Mac. I just use ZTerm (which is
a very old comms package, but works great) in Kermit mode to transfer
stuff to and from my SX.
>Also, I am not quite sure of the implications of ".. its server will
>not work on the SX calc." re Conn4x.
The SX only has Kermit built-in. There is no Xmodem unlike the GX. This
may be what was meant by the above statement.
Regards,
--
Bruce Horrocks
Surrey
England
<firstname>@<surname>.plus.com -- fix the obvious for email
Cameron Aust
Bruce,
Have found a copy to try (ZTerm 1.1b7 for MacOS 8/9 only (PowerPC
only)). I'll take a good look see how I go.
Bruce, thanks for your post.
Cameron Downunder.