Hello,

I have experienced xmax crush on quit. I guess that this is an unusual
case, but I want to report just to make sure. This is a reproducible
issue.

1) connect Teleo modules WITHOUT power
2) launch MaxMSP
3) create a new patcher
4) create a t.servo objects
5) the following messages are printed in Max window
	 Jitter installed
	 New t.servo version 0.2
	 Iterated over all serial devices and failed to find USB serial device

	 t.servo: Fatal Error: Failed to initialize TeleoMax layer, TeleoError
code 10
6) quit MaxMSP
7) crush...


PowerBook G4 667/DVD/GE/AirPort
Teleo Power/USB/Servo/MultiIO
MaxMSP 4.2 + Jitter 1.1


**********

Date/Time:  2003-06-29 21:29:50 +0900
OS Version: 10.2.6 (Build 6L60)
Host:       Macintosh.local.

Command:    MaxMSP 4.2
PID:        3013

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000018

Thread 0 Crashed:
  #0   0x001eb304 in clock_unset
  #1   0x01cb2b4c in TeleoServo_free
  #2   0x00240b90 in freeobject
  #3   0x002a1164 in vnewobj_free(vnewobj *)
  #4   0x00240b90 in freeobject
  #5   0x002138fc in patcher_free
  #6   0x00240b90 in freeobject
  #7   0x00216ca8 in patcher_close
  #8   0x00244598 in wind_close
  #9   0x00247e4c in wind_quit
  #10  0x001df910 in ae_quit
  #11  0x91b56570 in aeDispatchAppleEvent(AEDesc const*, AEDesc*,
unsigned long, unsigned char*)
  #12  0x91b5a8e4 in sendToSelf(AEDesc const*, AEDesc*, long, long)
  #13  0x91b58124 in AESendMessage
  #14  0x91b5a4e4 in aeSend
  #15  0x96aa68cc in AESend
  #16  0x96aa6a30 in SendAEToSelf(unsigned long)
  #17  0x969d8bd4 in HandleCompatibilityCommandEvent(OpaqueEventRef*)
  #18  0x969bb7c4 in
CompatibilityEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*,
void*)
  #19  0x969a2c54 in DispatchEventToHandlers
  #20  0x969a2fbc in SendEventToEventTargetInternal
  #21  0x969b5494 in SendEventToEventTarget
  #22  0x969c3030 in SendHICommandEvent
  #23  0x96a5b8dc in SendMenuItemSelectedEvent
  #24  0x96a5b7f8 in HandleKeyboardEvent
  #25  0x969a2c54 in DispatchEventToHandlers
  #26  0x969a2fbc in SendEventToEventTargetInternal
  #27  0x969a63d0 in SendEventToEventTargetWithOptions
  #28  0x969ecdf4 in HandleKeyboardEvent(OpaqueEventRef*, unsigned long)
  #29  0x969b288c in
ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*,
OpaqueEventRef*, void*)
  #30  0x969a2d0c in DispatchEventToHandlers
  #31  0x969a2fbc in SendEventToEventTargetInternal
  #32  0x969b5494 in SendEventToEventTarget
  #33  0x969b7258 in ToolboxEventDispatcher(OpaqueEventRef*)
  #34  0x969c8740 in CallEventDispatchHook
  #35  0x969b3c90 in TryEventDispatcher
  #36  0x969a4570 in GetOrPeekEvent
  #37  0x969a4330 in GetNextEventMatchingMask
  #38  0x969a8054 in WNEInternal
  #39  0x969adf0c in WaitNextEvent
  #40  0x0020245c in max_event
  #41  0x00201d98 in max_mainloop
  #42  0x0020206c in nopreemptloop
  #43  0x00201c7c in main

Thread 1:
  #0   0x90073c48 in mach_msg_trap
  #1   0x90005f90 in mach_msg
  #2   0xc00076cc in __ape_internal
  #3   0xc0000dd0 in __ape_agent
  #4   0x90020d48 in _pthread_body

Thread 2:
  #0   0x90042688 in semaphore_timedwait_signal_trap
  #1   0x9003e8b4 in _pthread_cond_wait
  #2   0x90232770 in TSWaitOnSemaphoreCommon
  #3   0x9023b550 in TimerThread
  #4   0x90020d48 in _pthread_body

Thread 3:
  #0   0x9003eaa8 in semaphore_wait_signal_trap
  #1   0x9003e8c4 in _pthread_cond_wait
  #2   0x90232754 in TSWaitOnSemaphoreCommon
  #3   0x90233094 in DeferredTaskThread
  #4   0x90020d48 in _pthread_body

Thread 4:
  #0   0x90073c48 in mach_msg_trap
  #1   0x90005f90 in mach_msg
  #2   0x953ddd90 in XServerMachPort::ReceiveMessage(int&, void*, int&)
  #3   0x953d17c8 in MIDIInPortThread::Run()
  #4   0x953d560c in XThread::RunHelper(void*)
  #5   0x90020d48 in _pthread_body

Thread 5:
  #0   0x90073c48 in mach_msg_trap
  #1   0x90005f90 in mach_msg
  #2   0x901489f0 in __CFRunLoopRun
  #3   0x90180f58 in CFRunLoopRunSpecific
  #4   0x94d9c1c0 in HALRunLoop::OwnThread(void*)
  #5   0x94d911b0 in CAPThread::Entry(CAPThread*)
  #6   0x90020d48 in _pthread_body

PPC Thread State:
   srr0: 0x001eb304 srr1: 0x0200f030                vrsave: 0x00000000
    xer: 0x00000000   lr: 0x001eb300  ctr: 0x9005e2d8   mq: 0x00000000
     r0: 0x001eb300   r1: 0xbfffe550   r2: 0x0050e000   r3: 0x00000000
     r4: 0x00000000   r5: 0x00000000   r6: 0x00000010   r7: 0x00000137
     r8: 0x000000c0   r9: 0xa0220eac  r10: 0xa0220be4  r11: 0xa00044b0
    r12: 0x9005e2d8  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
    r16: 0x00000000  r17: 0xbfffec70  r18: 0x00000000  r19: 0x00000000
    r20: 0x00000002  r21: 0x00000000  r22: 0xbfffec00  r23: 0xbfffeeb0
    r24: 0x00000000  r25: 0xbfffeea0  r26: 0x00000001  r27: 0x0051db08
    r28: 0x01cf0210  r29: 0x00000001  r30: 0x01cf0be8  r31: 0x00000000

Hey Rich,

We have a software upgrade for that board now which fixes both the problem
with the range and the slight jitter you may have noticed.  You'll need a
reprogrammed PIC.

Either you can drop by and we'll reprogram your pic or we'll send you one
and you can send your old one back.

Let Anne (anne@...) know which option you want to pursue.

David

-----Original Message-----
From: Rich Gibson [mailto:rich@...]
Sent: Thursday, June 19, 2003 12:40 PM
To: makingthings@yahoogroups.com
Subject: [makingthings] Servo range?


Hi all,

It seems that my servos are going about 90 degrees under control of the
servo module.  But these servos will go a bit over 180 degrees under
control of another board that I have.

The Servo Module specs say that it generates pulses from 1-2 mS.  This is
slightly less than the .9-2.1mS that my servos say they can do, but that
doesn't seem enough to account for 90 degrees less rotation.

I'm controlling these using the SDK under Linux.

Using TServo_positionMinSet and TServo_positionMaxSet seems to set the
ranges for the mapping used by TServo_positionSet, but that doesn't seem
to set the actual range.

So I'm seeking enlightenment!

Rich





To unsubscribe from this group, send an email to:
makingthings-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Hi all,

It seems that my servos are going about 90 degrees under control of the
servo module.  But these servos will go a bit over 180 degrees under
control of another board that I have.

The Servo Module specs say that it generates pulses from 1-2 mS.  This is
slightly less than the .9-2.1mS that my servos say they can do, but that
doesn't seem enough to account for 90 degrees less rotation.

I'm controlling these using the SDK under Linux.

Using TServo_positionMinSet and TServo_positionMaxSet seems to set the
ranges for the mapping used by TServo_positionSet, but that doesn't seem
to set the actual range.

So I'm seeking enlightenment!

Rich

Hello Jean,

We have been able to duplicate this problem in our lab and
will work to find a solution. The rates you report are about
what we observe. Meanwhile, I guess the workaround is to
avoid situations where a dropped pulse is critical, or to
reduce the data rate so that pulses are not dropped. We
recognize that this is far from optimal and will work to
find and solve the problem as soon as possible.

The MakingThings Stepper Motor Controller module is in fact
under development by me at this time. We should have this
module ready for purchase within about 4 weeks.

In addition to providing control for a bipolar stepper motor
drawing up to 2.5A, we will also bring out the step, direction,
and enable lines to drive an external stepper motor river, as
you suggest.

We are also exploring ways to add more functionality to existing
modules. As you might imagine, many of our modules could generate
the step, direction, and enable signals. However this raises many
questions regarding configuration and device management that have
yet to be worked out. There concept is still in the prelimary
stages, and we can't promise any availability yet.

Sincerely,
Michael Shiloh
MakingThings

> I have been trying to drive stepper motors with Teleo's digital
> out module but I have not been successful. Once in a while a
> pulse gets lost (about one pulse every 200 pulses, in average)
> and thus the position accuracy is lost. I have verified this with
> an oscilloscope at the digital out terminals. This happens even
> with relatively slow data rates (say 300 pulses / second, even
> spaced). I am driving Teleo with Max running in OS9.
>
> This suggests that the only reliable way to drive steppers would
> be to have a stepper indexer module. I have a question and a suggestion.
>
> When does makingthings expect to have a stepper motor controller available?
>
> Suggestion. I would prefer to use my own stepper motor drivers, designed for
my particular stepper motors. Thus I would prefer a module with an indexer only
(no stepper motor drivers included) or at least the option to tap into the step
/ direction signals and bypass the built-in driver.
>
> Jean Marc

am 17.6.2003 16:57 schrieb jmbara@... unter jmbara@...:

> I have been trying to drive stepper motors with Teleo's digital out module but
> I have not been successful. Once in a while a pulse gets lost (about one pulse
> every 200 pulses, in average) and thus the position accuracy is lost. I have
> verified this with an oscilloscope at the digital out terminals. This happens
> even with relatively slow data rates (say 300 pulses / second, even spaced). I
> am driving Teleo with Max running in OS9.

I guess the system overall datarate is just too slow for actually driving
hundreds of pulses a second. But this brings me to the following idea :
Why not just using the audio outs of the computer ? I am not into
electronics but it seems relatively easy to pull up audiolevel
(1.77 V, right) up to 5 V TTL ? No ? Generating the pulses in MSP would be
VERY easy and easy to modulate ... (could be done even without MSP)
If yes : what parts would do that ? I mean pull up the audio to 5V ?
Or am I missing something ?

wolf

I have been trying to drive stepper motors with Teleo's digital out module but I
have not been successful. Once in a while a pulse gets lost (about one pulse
every 200 pulses, in average) and thus the position accuracy is lost. I have
verified this with an oscilloscope at the digital out terminals. This happens
even with relatively slow data rates (say 300 pulses / second, even spaced). I
am driving Teleo with Max running in OS9.

This suggests that the only reliable way to drive steppers would be to have a
stepper indexer module. I have a question and a suggestion.

When does makingthings expect to have a stepper motor controller available?

Suggestion. I would prefer to use my own stepper motor drivers, designed for my
particular stepper motors. Thus I would prefer a module with an indexer only (no
stepper motor drivers included) or at least the option to tap into the step /
direction signals and bypass the built-in driver.

Jean Marc

(a,b)
> Just within the last 30 minutes we found and fixed a bug in the servo
> module firmware which caused this problem. In order to get the new
> firmware, you will need to replace the Microchip PIC on your servo
> modules.
well, thats fast !

> We will send you a programmed PIC and instructions for replacement.

thanks !

wolf

Hello Wolf,

(a,b)
Just within the last 30 minutes we found and fixed a bug in the servo
module firmware which caused this problem. In order to get the new
firmware, you will need to replace the Microchip PIC on your servo
modules.

We will send you a programmed PIC and instructions for replacement.

Our policy is that we will cover the charges of sending the PIC by
surface mail; if you wish, you can pay any additional costs to get faster
service. I don't yet know these prices; as I said, we ony just fixed
the problem.

If you, or anyone, wishes this upgrade, please email anne@...
and indicate how many servo modules you have.

(b1)
The Teleo Network is described in:

http://www.makingthings.com/products/documentation/teleo_user_guide/teleo_system\
.html

In particular, the specifications, including speed are in:

http://www.makingthings.com/products/documentation/teleo_user_guide/teleo_system\
.html#specs

(c)
That information should be up on the website shortly. I'll ask Anne where that
stands, and see if we can email the specs (or post them here)

Sincerely,
Michael Shiloh
MakingThings


On Mon, 16 Jun 2003 wheiniger@... wrote:

>
>
> hi list
> since some of you might have experience:
> I am trying servo motors and a few questions arise
>
> using teleo with carson 13374 "standard" servos
>
> a) my motors "tremble" when not in 0 position. They slightly move back and
> forth irregularly with no pattern.
> Is this normal servo behaviour ?
> If no : Would it go away with "better", more expensive motors ?
>
> b) what i need is smooth movement.
> but they do not move smooth but hopping from step to step. Even with high
> resolution data.
>
> Any hints to get move really smooooth ?
>
> b.1) how fast does Teleo send data ? Is it possible that hopping occours
> because motor can't read position data that fast ?
>
> c) whats the technical data of the motor sold by making things ?
>
> tia
>
> wolf
>
>
>
> To unsubscribe from this group, send an email to:
> makingthings-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

--

hi list
since some of you might have experience:
I am trying servo motors and a few questions arise

using teleo with carson 13374 "standard" servos

a) my motors "tremble" when not in 0 position. They slightly move back and
forth irregularly with no pattern.
Is this normal servo behaviour ?
If no : Would it go away with "better", more expensive motors ?

b) what i need is smooth movement.
but they do not move smooth but hopping from step to step. Even with high
resolution data.

Any hints to get move really smooooth ?

b.1) how fast does Teleo send data ? Is it possible that hopping occours
because motor can't read position data that fast ?

c) whats the technical data of the motor sold by making things ?

tia

wolf

btw : i did the Z-term routine as described on the list earlier.
It seems to do what it is supposed to. looks fine.
but it crashes max as soon as i call t.servo ...

hi

I do have absolutely no chance in getting teleo working

config :

Mac Sys 9.2, Max/MSP 4.1 (powerbook and Quicksilver G4 tested)
system extensions reduced to necessarys
(tried several

Teleo Servomodule (and of course USB and Power)
USB and SERVO Modules are slowly flashing

Sysprofiler sees USB Device

-opening new Max Patch
-selecting t.servo
- Max Window shows : New TeleoServo version 0.1
                      TeleoMaxLib version 1.5
-Max freezes to never come back !
-several tries without success (also with different startup sequences)

on both computers no chance to get anything going

please help

best

wolf

Hi,

I've been asked if Teleo would have any trouble with
overdrive enabled. I've done some experiments and looked
over our critical code and I see no reason why it should
not. However, I don't have any fancy patches so I have
not really exercised Max very thoroughly.

So I'm turning to the list.

Have any of you used Teleo with overdrive enabled? Were
there any problems?

Do any of you have fancy music patches that also use
Teleo? Can you test them with overdrive enabled?

Thanks in advance for any feedback,

Michael Shiloh
MakingThings

michael@...

Hi everyone,

We've just put up our first release of Teleo Max for Mac OS X.

The main difference between the last beta release and this
current release is that I've added more error checking and
reporting to the code that finds and opens the USB port and
then communicates with the Teleo USB Translator.

Our goal is that this hightened communication will be more
re-assuring, while any failures will be easier to debug.

A second big difference is the addition of very nice help
patches,courtesy of Mike Zbyszynski.

We plan to post this on our announce list shortly, but
I'd love to get a bit of feedback from this group first.
In particular, it would be great to know that it works
for those of you who had trouble with our first beta
release not finding your USB port.

Download from:

  http://www.makingthings.com/products/downloads/max_externals.htm

I welcome your feedback, either on this list or privately.

Michael Shiloh
michael@...

Hello Jeff,

Thanks! We have been getting many positive reactions to our system, so
we think we're on to something.

The network protocol is our own proprietary protocol. At the low
level, it is RS-485 peer-to-peer.

The SDK is in beta right now. If you are interested in access to the
beta version drop me a private email and we'll get you a copy. The
final version should be ready in the next few weeks.

Thanks for your interest. Please feel free to ask further questions.

Michael

On Wed, 7 May 2003, jefman391 wrote:

> hi -
>
> congratulations on getting this out - looks like a great system!
>
> curious about the network protocol, are you using CAN?
>
> also, what's the ETA on the SDK?
>
> <Jeff

hi -

congratulations on getting this out - looks like a great system!

curious about the network protocol, are you using CAN?

also, what's the ETA on the SDK?

<Jeff

Hi Michael,

After installed the latest version of TeleoMaxLib2, I can't see an error as
follows anymore:-)

>Jitter installed
>New TeleoServo version 0.1
>TeleoServo: Fatal Error: Failed to open USB port
>”„ error: connect: inlet 1 of t.servo out of range


And Teleo modules mostly works for me. What 'mostly' means is:

1) boot PowerBook
2) launch MaxMSP app, then load servotest.pat
3) t.servo works fine
4) quit MaxMSP app
5) launch MaxMSP and , then load servotest.pat again
6) errors are reported in Max window
     Jitter installed
     New TeleoServo version 0.1
     TeleoMaxLib version 1.5
     TeleoServo: Can not send data to unbound module
     TeleoServo: Can not send data to unbound module
     ...
7) press the white button of Teleo Servo Module
8) t.servo start working
     Bound to MakingThings Teleo Servo version 2.0 at address 5

I have experienced this problem only, once. And I didn't find how to
reproduce. If this is a bug, please fix it. Since 'press the white button'
is not possible when the module is embedded into a system.


Anyway, the latest TeleoMaxLib2 made big progress for me!


michael shiloh wrote:
>Hi Shigeru and others,
>
>I think I found a bug in my driver code that would prevent the
>finding of the Teleo USB device in certain Mac USB
>configurations.
>
>Those of you for whom the Teleo Max OS X beta was failing, can you
>please test my fix? Download
>
>   http://www.makingthings.com/downloads/TeleoMaxLib2.sit
>
>unpack the stuffit archive and place the result (TeleoMaxLib2)
>in
>
>   /Library/CFMSupport
>
>This is all for OS X, not 9. Let me know how it works for you.
>
>Thanks,
>Michael


Shigeru Kobayashi
kotobuki@...

Hi Shigeru and others,

I think I found a bug in my driver code that would prevent the
finding of the Teleo USB device in certain Mac USB
configurations.

Those of you for whom the Teleo Max OS X beta was failing, can you
please test my fix? Download

	 http://www.makingthings.com/downloads/TeleoMaxLib2.sit

unpack the stuffit archive and place the result (TeleoMaxLib2)
in

	 /Library/CFMSupport

This is all for OS X, not 9. Let me know how it works for you.

Thanks,
Michael

Hello Michael,

Yes, I installed MaxMSP for OS 9 in order to run that experiment.

I have 2 partitions on my hard disk drive, one for OS 9 and the other one
for OS X. I have MaxMSP 4.1 installed in the partition. I installed a
package from the following URL to the partition for OS 9:

http://www.makingthings.com/downloads/TeleoMax_macos9_v_1_9_3.sit

I hope this helps:-)


michael shiloh wrote:
>Hello Shigeru,
>
>Very interesting. I presume you installed MaxMSP for OS 9 in order to
>run this experiment. Did you also install the Teleo objects and shared
>library for OS 9? or were you using the OS X version?
>
>Michael
>
>On Wed, 23 Apr 2003, Shigeru Kobayashi wrote:
>
>> Hello,
>>
>> I got a small progress about t.servo issue. I launched MaxMSP under Mac OS
>> 9, and t.servo seemed to work fine. Here is a log that was printed in Max
>> window:
>>
>> MSP/ASIO, no ASIO drivers found in ASIO Drivers folder
>> MSP: Sound Manager 3.6.7
>> Jitter installed
>> New TeleoServo version 0.1
>> TeleoMaxLib version 1.5
>> Bound to MakingThings Teleo Servo version 2.0 at address 5
>>
>>
>> Once I had to press the white button of the Servo Module to see "Bound to
>> MakingThings Teleo...", but anyway, I want to report.
>>
>>
>> Shigeru Kobayashi
>> kotobuki@...


Shigeru Kobayashi
kotobuki@...

Hello Shigeru,

Very useful. Thanks. This provides some clues that I'll test
for in my upcoming test program. The log:

>  #1   0x0190b84c in TeleoServo_free

certainly suggests that I'm freeing something that I should not
be freeing, although I'm sure this is a result of the failed
open of the USB port, which is the real problem.

Michael

On Wed, 23 Apr 2003, Shigeru Kobayashi wrote:

> Hello,
>
> This might be not a good news, but I got an error as follows for several
> times:
>
> Jitter installed
> New TeleoServo version 0.1
> TeleoServo: Fatal Error: Failed to open USB port
> $B!%(B error: connect: inlet 1 of t.servo out of range
>
> Every time when this error occurred, MaxMSP crushed on closing a patch that
> includes t.servo. I don't know whether this is MaxMSP side problem or not,
> but I want to report just to make sure.
>
>
> Sincerely,
>
>
> **********
>
> Date/Time:  2003-04-23 21:05:42 +0900
> OS Version: 10.2.5 (Build 6L29)
> Host:       Macintosh.local.
>
> Command:    MaxMSP 4.2
> PID:        403
>
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000018
>
> Thread 0 Crashed:
>  #0   0x001ab304 in clock_unset
>  #1   0x0190b84c in TeleoServo_free
>  #2   0x00200b90 in freeobject
>  #3   0x00261164 in vnewobj_free(vnewobj *)
>  #4   0x00200b90 in freeobject
>  #5   0x001d38fc in patcher_free
>  #6   0x00200b90 in freeobject
>  #7   0x001d6ca8 in patcher_close
>  #8   0x00204598 in wind_close
>  #9   0x00203c08 in wind_filemenu
>  #10  0x001c63e0 in menu_dobar
>  #11  0x001c2a68 in max_doevent
>  #12  0x001c2474 in max_event
>  #13  0x001c1d98 in max_mainloop
>  #14  0x001c206c in nopreemptloop
>  #15  0x001c1c7c in main
>
> Thread 1:
>  #0   0x90073c48 in mach_msg_trap
>  #1   0x90005f90 in mach_msg
>  #2   0xc00076cc in __ape_internal
>  #3   0xc0000dd0 in __ape_agent
>  #4   0x90020d48 in _pthread_body
>
> Thread 2:
>  #0   0x90042688 in semaphore_timedwait_signal_trap
>  #1   0x9003e8b4 in _pthread_cond_wait
>  #2   0x90232770 in TSWaitOnSemaphoreCommon
>  #3   0x9023b550 in TimerThread
>  #4   0x90020d48 in _pthread_body
>
> Thread 3:
>  #0   0x9003eaa8 in semaphore_wait_signal_trap
>  #1   0x9003e8c4 in _pthread_cond_wait
>  #2   0x90232754 in TSWaitOnSemaphoreCommon
>  #3   0x90233094 in DeferredTaskThread
>  #4   0x90020d48 in _pthread_body
>
> Thread 4:
>  #0   0x90073c48 in mach_msg_trap
>  #1   0x90005f90 in mach_msg
>  #2   0x953ddd90 in XServerMachPort::ReceiveMessage(int&, void*, int&)
>  #3   0x953d17c8 in MIDIInPortThread::Run()
>  #4   0x953d560c in XThread::RunHelper(void*)
>  #5   0x90020d48 in _pthread_body
>
> Thread 5:
>  #0   0x90073c48 in mach_msg_trap
>  #1   0x90005f90 in mach_msg
>  #2   0x901489f0 in __CFRunLoopRun
>  #3   0x90180f58 in CFRunLoopRunSpecific
>  #4   0x94d9c1c0 in HALRunLoop::OwnThread(void*)
>  #5   0x94d911b0 in CAPThread::Entry(CAPThread*)
>  #6   0x90020d48 in _pthread_body
>
> PPC Thread State:
>   srr0: 0x001ab304 srr1: 0x0200f030                vrsave: 0x00000000
>    xer: 0x00000000   lr: 0x001ab300  ctr: 0x9005e2d8   mq: 0x00000000
>     r0: 0x001ab300   r1: 0xbffff390   r2: 0x004ce000   r3: 0x00000000
>     r4: 0x00000000   r5: 0x00000000   r6: 0x00000010   r7: 0x00000137
>     r8: 0x000000c3   r9: 0xa0220eac  r10: 0xa0220be4  r11: 0xa00044b0
>    r12: 0x9005e2d8  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
>    r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
>    r20: 0xbffffea0  r21: 0xffffffff  r22: 0x0055a4d8  r23: 0x0055a4d8
>    r24: 0x00810005  r25: 0x00000077  r26: 0x00000001  r27: 0x004ddb08
>    r28: 0x018ecb70  r29: 0x00000001  r30: 0x018ed4c0  r31: 0x00000000
>
>
> Shigeru Kobayashi
> kotobuki@...
>
>
> To unsubscribe from this group, send an email to:
> makingthings-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

--

Hello Shigeru,

Very interesting. I presume you installed MaxMSP for OS 9 in order to
run this experiment. Did you also install the Teleo objects and shared
library for OS 9? or were you using the OS X version?

Michael

On Wed, 23 Apr 2003, Shigeru Kobayashi wrote:

> Hello,
>
> I got a small progress about t.servo issue. I launched MaxMSP under Mac OS
> 9, and t.servo seemed to work fine. Here is a log that was printed in Max
> window:
>
> MSP/ASIO, no ASIO drivers found in ASIO Drivers folder
> MSP: Sound Manager 3.6.7
> Jitter installed
> New TeleoServo version 0.1
> TeleoMaxLib version 1.5
> Bound to MakingThings Teleo Servo version 2.0 at address 5
>
>
> Once I had to press the white button of the Servo Module to see "Bound to
> MakingThings Teleo...", but anyway, I want to report.
>
>
> Shigeru Kobayashi
> kotobuki@...
>
>
> To unsubscribe from this group, send an email to:
> makingthings-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

--

Hello,

This might be not a good news, but I got an error as follows for several
times:

Jitter installed
New TeleoServo version 0.1
TeleoServo: Fatal Error: Failed to open USB port
”„ error: connect: inlet 1 of t.servo out of range

Every time when this error occurred, MaxMSP crushed on closing a patch that
includes t.servo. I don't know whether this is MaxMSP side problem or not,
but I want to report just to make sure.


Sincerely,


**********

Date/Time:  2003-04-23 21:05:42 +0900
OS Version: 10.2.5 (Build 6L29)
Host:       Macintosh.local.

Command:    MaxMSP 4.2
PID:        403

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000018

Thread 0 Crashed:
  #0   0x001ab304 in clock_unset
  #1   0x0190b84c in TeleoServo_free
  #2   0x00200b90 in freeobject
  #3   0x00261164 in vnewobj_free(vnewobj *)
  #4   0x00200b90 in freeobject
  #5   0x001d38fc in patcher_free
  #6   0x00200b90 in freeobject
  #7   0x001d6ca8 in patcher_close
  #8   0x00204598 in wind_close
  #9   0x00203c08 in wind_filemenu
  #10  0x001c63e0 in menu_dobar
  #11  0x001c2a68 in max_doevent
  #12  0x001c2474 in max_event
  #13  0x001c1d98 in max_mainloop
  #14  0x001c206c in nopreemptloop
  #15  0x001c1c7c in main

Thread 1:
  #0   0x90073c48 in mach_msg_trap
  #1   0x90005f90 in mach_msg
  #2   0xc00076cc in __ape_internal
  #3   0xc0000dd0 in __ape_agent
  #4   0x90020d48 in _pthread_body

Thread 2:
  #0   0x90042688 in semaphore_timedwait_signal_trap
  #1   0x9003e8b4 in _pthread_cond_wait
  #2   0x90232770 in TSWaitOnSemaphoreCommon
  #3   0x9023b550 in TimerThread
  #4   0x90020d48 in _pthread_body

Thread 3:
  #0   0x9003eaa8 in semaphore_wait_signal_trap
  #1   0x9003e8c4 in _pthread_cond_wait
  #2   0x90232754 in TSWaitOnSemaphoreCommon
  #3   0x90233094 in DeferredTaskThread
  #4   0x90020d48 in _pthread_body

Thread 4:
  #0   0x90073c48 in mach_msg_trap
  #1   0x90005f90 in mach_msg
  #2   0x953ddd90 in XServerMachPort::ReceiveMessage(int&, void*, int&)
  #3   0x953d17c8 in MIDIInPortThread::Run()
  #4   0x953d560c in XThread::RunHelper(void*)
  #5   0x90020d48 in _pthread_body

Thread 5:
  #0   0x90073c48 in mach_msg_trap
  #1   0x90005f90 in mach_msg
  #2   0x901489f0 in __CFRunLoopRun
  #3   0x90180f58 in CFRunLoopRunSpecific
  #4   0x94d9c1c0 in HALRunLoop::OwnThread(void*)
  #5   0x94d911b0 in CAPThread::Entry(CAPThread*)
  #6   0x90020d48 in _pthread_body

PPC Thread State:
   srr0: 0x001ab304 srr1: 0x0200f030                vrsave: 0x00000000
    xer: 0x00000000   lr: 0x001ab300  ctr: 0x9005e2d8   mq: 0x00000000
     r0: 0x001ab300   r1: 0xbffff390   r2: 0x004ce000   r3: 0x00000000
     r4: 0x00000000   r5: 0x00000000   r6: 0x00000010   r7: 0x00000137
     r8: 0x000000c3   r9: 0xa0220eac  r10: 0xa0220be4  r11: 0xa00044b0
    r12: 0x9005e2d8  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
    r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
    r20: 0xbffffea0  r21: 0xffffffff  r22: 0x0055a4d8  r23: 0x0055a4d8
    r24: 0x00810005  r25: 0x00000077  r26: 0x00000001  r27: 0x004ddb08
    r28: 0x018ecb70  r29: 0x00000001  r30: 0x018ed4c0  r31: 0x00000000


Shigeru Kobayashi
kotobuki@...

Hello,

I got a small progress about t.servo issue. I launched MaxMSP under Mac OS
9, and t.servo seemed to work fine. Here is a log that was printed in Max
window:

MSP/ASIO, no ASIO drivers found in ASIO Drivers folder
MSP: Sound Manager 3.6.7
Jitter installed
New TeleoServo version 0.1
TeleoMaxLib version 1.5
Bound to MakingThings Teleo Servo version 2.0 at address 5


Once I had to press the white button of the Servo Module to see "Bound to
MakingThings Teleo...", but anyway, I want to report.


Shigeru Kobayashi
kotobuki@...

Hello Michael,

Thank you very much for your quick reply in spite of you are so busy now. I'
m looking forward to a test patch from you after the demo:-) But just to
make sure, I picked up Teleo related files. Please let me know if you find
anything unusual about these files.

[Macintosh:Application Support/Cycling '74/externals] kotobuki% ls -all t.*
-rwxr-xr-x  1 kotobuki  staff  17876 Apr  8 21:10 t.mc10
-rwxr-xr-x  1 kotobuki  staff  17868 Apr  8 21:08 t.mc2
-rwxr-xr-x  1 kotobuki  staff  16204 Apr  4 17:20 t.mio.ain
-rwxr-xr-x  1 kotobuki  staff  15012 Apr  3 22:48 t.mio.din
-rwxr-xr-x  1 kotobuki  staff  14692 Apr  3 22:38 t.mio.dout
-rwxr-xr-x  1 kotobuki  staff  15628 Apr  4 14:31 t.mio.pwm
-rwxr-xr-x  1 kotobuki  staff  15404 Apr  8 21:05 t.servo
-rwxr-xr-x  1 kotobuki  staff  16876 Apr  8 20:45 t.stepper


[Macintosh:/Library/CFMSupport] kotobuki% ls -all
total 2272
drwxrwxr-x   9 kotobuki  admin     306 Apr 10 22:26 .
drwxrwxr-x  37 root      admin    1258 Jan 16 12:16 ..
-rwxrwxrwx   1 root      admin  824525 Apr 11  2002 HotSync Libraries
-rw-r--r--   1 kotobuki  admin   92725 Oct 30 15:59 N065U_Library.shlb
-rw-r--r--   1 kotobuki  admin   92737 Oct 30 15:58 N122U_Library.shlb
drwxrwxr-x   4 root      admin     136 Apr 15  2002 Palm Conduit Library.cfm
-rwxrwxr-x   1 kotobuki  staff    4636 Mar 19 16:04 Service USB Driver CFM
Bridge
drwxrwxr-x   4 root      admin     136 Oct 16  2002 StuffItEngineShell.cfm
-rwxr-xr-x   1 kotobuki  staff   74362 Apr  8 19:36 TeleoMaxLib2


michael shiloh wrote:
>Hello Shigeru,
>
>
>Thanks for running the experiment and providing the results so promptly
>
>> Instead of "USBHighSpeedSerialConverter", "usbserial-011" appeared.
>
>Ah yes. "USBHighSpeedSerialConverter" on OS-9, "usbserial-0xx" on OS-X.
>
>I see nothing unusual about your patch, but I'll test it when I get
>to work (I don't have a servo module at home right now). Anyway,
>I don't think your patch is the problem.
>
>Since the Zterm test worked fine, I think this narrows it down to the
>Teleo Max code that communicates with the serial port.
>
>I think I'll write a little test program that uses the Teleo Max serial
>code to do what you just did with Zterm, and send it to you. I won't
>be able to finish this for a couple of days as we're putting together
>a demo for the Embedded Systems Conference. Once the demo is finished
>I'll be able to work on this test, and I'll let you know as soon as
>it's ready.
>
>Thanks again for your patience,
>
>Michael


Shigeru Kobayashi
kotobuki@...

Hello Shigeru,


Thanks for running the experiment and providing the results so promptly

> Instead of "USBHighSpeedSerialConverter", "usbserial-011" appeared.

Ah yes. "USBHighSpeedSerialConverter" on OS-9, "usbserial-0xx" on OS-X.

I see nothing unusual about your patch, but I'll test it when I get
to work (I don't have a servo module at home right now). Anyway,
I don't think your patch is the problem.

Since the Zterm test worked fine, I think this narrows it down to the
Teleo Max code that communicates with the serial port.

I think I'll write a little test program that uses the Teleo Max serial
code to do what you just did with Zterm, and send it to you. I won't
be able to finish this for a couple of days as we're putting together
a demo for the Embedded Systems Conference. Once the demo is finished
I'll be able to work on this test, and I'll let you know as soon as
it's ready.

Thanks again for your patience,

Michael

On Mon, 21 Apr 2003, Shigeru Kobayashi wrote:

> Hello Michael shiloh,
>
> >The message
> >
> >  > TeleoServo: Can not send data to unbound module
> >
> >means that the Teleo software running on your Mac was not able to
> >communicate with the Teleo module in question (in this case the
> >Teleo Servo). This could be due to the USB driver, the USB port,
> >the cable, the USB Translator, or the Servo module.
> >
> >The first step would be to determine if your Mac can communicate
> >with any Teleo modules.
> >
> >Do you have more Teleo modules (e.g Multi IO, Digital Out, Motor
> >Controller)? Are you able to control them?
> >
> >If you don't have any other Teleo modules, the next step would
> >be to determine whether you can communicate with the USB
> >Translator. Since the USB device emulates a serial port, an
> >easy way to do this is by using a serial terminal emulator
> >such as Zterm.  To test using Zterm do the following:
> >
> >
> >1. Download and install Zterm (e.g. from http://homepage.mac.com/dalverson/
> >zterm/)
> >   Make sure you get the version appropriate to your OS.
> >
> >2. Invoke Zterm. You should be presented with a choice of serial ports to
> >connect.
> >   One of them should be something like "USBHighSpeedSerialConverter".
> >
> >   (If you are not given a choice select "Settings" and then "Modem
> >Preferences")
>
> Instead of "USBHighSpeedSerialConverter", "usbserial-011" appeared.
>
>
> >3. If you've come this far, I assume that "USBHighSpeedSerialConverter"
> >   was presented at Zterm. Select this port (if it didn't automatically
> >   select it for you). You should see a character or two, probably the
> >   '<' sign, appearing on your screen about every 5 seconds. This is a
> >   message from one of the Teleo modules identifying itself.
> >
> >   The USB Translator normally communicates with the Mac in binary mode,
> >   which is why you may see different odd characters.
> >
> >4. Tell the USB Translator to go into ASCII mode by pressing the
> >   <space> bar rapidly twice. You should see:
> >
> >   MAKINGTHINGS : USB Translator V2.0
> >   Command Mode (press '?' for Help)
>
> Yes.
>
>
> >5. Press the white button on your Servo module. You should see
> >   something like:
> >
> >   B A 5
>
> Yes, exactly same as you described.
>
>
> >   (If you have other modules, you should press the white button
> >   on those modules to see each of them report the button press
> >   module.)
>
> Yes. Here is a log when tried with MultiIO module and USB module.
>
>  B A 2
>  B A 3
>
>
> >6. When you are finished with Zterm press 'b' to return to
> >   binary mode, then quit Zterm.
> >
> >Try these steps and post the results on this list, and we'll go
> >from there.
>
> Since the steps you suggested looks OK, so I tried again with my simple
> test patch, and it seems that still I can't connect to the module. I forgot
> to attach the patch in the last post, so I attached this time.
>
> Jitter installed
> New TeleoServo version 0.1
> TeleoMaxLib version 1.5
> TeleoServo: Can not send data to unbound module
> TeleoServo: Can not send data to unbound module
> TeleoServo: Can not send data to unbound module
>
>
> Anyway, thank you very much for your quick and detailed reply.
>
>
> max v2;
> #N vpatcher 304 74 704 374;
> #P number 96 94 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P toggle 135 94 15 0;
> #P newex 96 135 129 196617 t.servo @min=0 @max=90;
> #P connect 2 0 0 0;
> #P connect 1 0 0 1;
> #P pop;
>
>
> Shigeru Kobayashi
> kotobuki@...

Hello Michael shiloh,

>The message
>
>  > TeleoServo: Can not send data to unbound module
>
>means that the Teleo software running on your Mac was not able to
>communicate with the Teleo module in question (in this case the
>Teleo Servo). This could be due to the USB driver, the USB port,
>the cable, the USB Translator, or the Servo module.
>
>The first step would be to determine if your Mac can communicate
>with any Teleo modules.
>
>Do you have more Teleo modules (e.g Multi IO, Digital Out, Motor
>Controller)? Are you able to control them?
>
>If you don't have any other Teleo modules, the next step would
>be to determine whether you can communicate with the USB
>Translator. Since the USB device emulates a serial port, an
>easy way to do this is by using a serial terminal emulator
>such as Zterm.  To test using Zterm do the following:
>
>
>1. Download and install Zterm (e.g. from http://homepage.mac.com/dalverson/
>zterm/)
>   Make sure you get the version appropriate to your OS.
>
>2. Invoke Zterm. You should be presented with a choice of serial ports to
>connect.
>   One of them should be something like "USBHighSpeedSerialConverter".
>
>   (If you are not given a choice select "Settings" and then "Modem
>Preferences")

Instead of "USBHighSpeedSerialConverter", "usbserial-011" appeared.


>3. If you've come this far, I assume that "USBHighSpeedSerialConverter"
>   was presented at Zterm. Select this port (if it didn't automatically
>   select it for you). You should see a character or two, probably the
>   '<' sign, appearing on your screen about every 5 seconds. This is a
>   message from one of the Teleo modules identifying itself.
>
>   The USB Translator normally communicates with the Mac in binary mode,
>   which is why you may see different odd characters.
>
>4. Tell the USB Translator to go into ASCII mode by pressing the
>   <space> bar rapidly twice. You should see:
>
>   MAKINGTHINGS : USB Translator V2.0
>   Command Mode (press '?' for Help)

Yes.


>5. Press the white button on your Servo module. You should see
>   something like:
>
>   B A 5

Yes, exactly same as you described.


>   (If you have other modules, you should press the white button
>   on those modules to see each of them report the button press
>   module.)

Yes. Here is a log when tried with MultiIO module and USB module.

  B A 2
  B A 3


>6. When you are finished with Zterm press 'b' to return to
>   binary mode, then quit Zterm.
>
>Try these steps and post the results on this list, and we'll go
>from there.

Since the steps you suggested looks OK, so I tried again with my simple
test patch, and it seems that still I can't connect to the module. I forgot
to attach the patch in the last post, so I attached this time.

Jitter installed
New TeleoServo version 0.1
TeleoMaxLib version 1.5
TeleoServo: Can not send data to unbound module
TeleoServo: Can not send data to unbound module
TeleoServo: Can not send data to unbound module


Anyway, thank you very much for your quick and detailed reply.


max v2;
#N vpatcher 304 74 704 374;
#P number 96 94 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P toggle 135 94 15 0;
#P newex 96 135 129 196617 t.servo @min=0 @max=90;
#P connect 2 0 0 0;
#P connect 1 0 0 1;
#P pop;


Shigeru Kobayashi
kotobuki@...

Hi Shigeru,

I'm glad you posted your question on this list. It will help
us all share information.

The message

   > TeleoServo: Can not send data to unbound module

means that the Teleo software running on your Mac was not able to
communicate with the Teleo module in question (in this case the
Teleo Servo). This could be due to the USB driver, the USB port,
the cable, the USB Translator, or the Servo module.

The first step would be to determine if your Mac can communicate
with any Teleo modules.

Do you have more Teleo modules (e.g Multi IO, Digital Out, Motor
Controller)? Are you able to control them?

If you don't have any other Teleo modules, the next step would
be to determine whether you can communicate with the USB
Translator. Since the USB device emulates a serial port, an
easy way to do this is by using a serial terminal emulator
such as Zterm.  To test using Zterm do the following:


1. Download and install Zterm (e.g. from
http://homepage.mac.com/dalverson/zterm/)
    Make sure you get the version appropriate to your OS.

2. Invoke Zterm. You should be presented with a choice of serial ports to
connect.
    One of them should be something like "USBHighSpeedSerialConverter".

    (If you are not given a choice select "Settings" and then "Modem
Preferences")

    If you do not see "USBHighSpeedSerialConverter", two possible causes
    are:

    1. The USB port may be hung. Perform these steps to unclog the USB port:

	 1. shutdown the Mac
	 2. unplug the USB cable from the Teleo USB Translator
	 3. unplug the Teleo Network cable from the Teleo USB Translator
	 4. wait about 10 seconds
	 5. plug in the Teleo Network cable to the Teleo USB Translator
	 6. make sure the green LED on the Teleo USB Translator is blinking
	 6. plug in the USB cable to the Teleo USB Translator
	 7. power up the Mac
	 8. try Zterm again

    2. The USB driver may not be installed proplerly. Remove the driver,
       and install it again. The driver (and instructions) are available
       in the Teleo Max Externals at

         http://www.makingthings.com/products/downloads/max_externals.htm

       or directly from the USB manufacturer (FTDI) at

         http://www.ftdichip.com/FTMacDriver.htm

       and download either

         VCP Drivers for Apple OS-8 / OS-9 ( FT232 / FT245 )

       or

         VCP Drivers for Apple OS-X ( FT232 / FT245 )

       as appropriate to your OS.

3. If you've come this far, I assume that "USBHighSpeedSerialConverter"
    was presented at Zterm. Select this port (if it didn't automatically
    select it for you). You should see a character or two, probably the
    '<' sign, appearing on your screen about every 5 seconds. This is a
    message from one of the Teleo modules identifying itself.

    The USB Translator normally communicates with the Mac in binary mode,
    which is why you may see different odd characters.

4. Tell the USB Translator to go into ASCII mode by pressing the
    <space> bar rapidly twice. You should see:

	 MAKINGTHINGS : USB Translator V2.0
	 Command Mode (press '?' for Help)

    If this doesn't work, wait 3 seconds and press the <space> bar
    twice again.

5. Press the white button on your Servo module. You should see
    something like:

	 B A 5

    '5' is the Servo module default address. If you have different
    modules, pressing the button on those modules should yield a
    "button pressed" message from each of those modules, along
    with its address. (If any module addresses have been changed
    from the default, the address reported will be the one you
    changed to.)

    (If you have other modules, you should press the white button
    on those modules to see each of them report the button press
    module.)

6. When you are finished with Zterm press 'b' to return to
    binary mode, then quit Zterm.

Try these steps and post the results on this list, and we'll go
from there.

Sincerely,
Michael Shiloh
michael@...

Hello,

I hesitate to post this kind of question as my first post to this ML, but
anyway, I have a small problem about using Teleo Servo Module.

I'm trying to control Hitec HS-645MG via my Teleo Servo Module. But I got
errors (as follows) anytime when I try to send a message to the module. The
LED of the module keep blinking, so the cable connection looks OK.

Jitter installed
New TeleoServo version 0.1
TeleoMaxLib version 1.5
TeleoServo: Can not send data to unbound module
TeleoServo: Can not send data to unbound module
TeleoServo: Can not send data to unbound module
...

To make sure, I attached the very small testing patch that I used.

I'm sorry for trouble you, but it would be much appreciated if you give me
any suggestions.


Teleo Introductory Set + Teleo Servo Module
Mac OS X 10.2.5
MaxMSP 4.2 + Jitter 1.1
PowerBook G4 rev.B (512MB/30GB/DVD/AirPort)


Shigeru Kobayashi
kotobuki@...