#7146 - 11/24/04 09:27 AM
Re: Leopard stuck
|
samai
newbie
Registered: 11/10/04
Posts: 3
Loc: Houston , Texas USA
|
As far as I can tell the CPU is seated properly. I left the Leopard unit unplug last night. Just now I tried it again. The reload completed successfully. I received the message saying that it is restarting the control unit. Yet no response.
|
|
Top
|
|
|
|
|
#7148 - 11/24/04 09:44 PM
Re: Leopard stuck
|
R.Brett
newbie
Registered: 11/22/04
Posts: 4
Loc: Melbourne, Australia
|
Hi. Just to add to this saga... I thought I was really stupid, having just received a new Leopard II myself, and I could not get any screens to work after two nights of failed attempts... Then I read this thread... I have the identical problem on a brand-new Leopard II here as well... 
|
|
Top
|
|
|
|
|
#7150 - 11/25/04 10:11 PM
Re: Leopard stuck
|
R.Brett
newbie
Registered: 11/22/04
Posts: 4
Loc: Melbourne, Australia
|
Well, the problem was solved about 1hr after posting last night. Problem is, I didn't apply proper engineering principle of changing one thing at a time, I changed a whole lot at once, as follows...
1. Downloaded V311 of Leo executive from other discussion forum link, upgraded from v308.
2. Played around changing param 6 to 0 from 3 as eariler thread entry discussed (why? still don't know!)
3. Wrote quick screen 1 & used sample program as listed earlier:
IF Variable #63 = 255
THEN Variable #63 = 1
END
...and it worked. I'm assuming 1 & 2 are irrelevant (?), and its me being a newbie at all of this not knowing to set screen at start of program as per above. I assumed screen 1 would default, (actually, I said if screen was touched anywhere (button 0) send screen 1, which does not work)....
After this, applying first two lines above to start of the real program, and everything is working fine, thanks to all those who posted suggestions in this thread!
Cheers! 
|
|
Top
|
|
|
|
|
#7151 - 12/05/04 06:05 PM
Re: Leopard stuck
|
samai
newbie
Registered: 11/10/04
Posts: 3
Loc: Houston , Texas USA
|
It worked!
1. I Downloaded V311 of Leo executive from other discussion forum link, upgraded from v308.
2. Wrote quick screen 1 & used sample program as listed earlier:
IF Variable #63 = 255
THEN Variable #63 = 1
END
Now to the next question. Does the button on the module does anything?
|
|
Top
|
|
|
|
#20872 - 02/08/09 02:54 PM
Re: Leopard stuck
[Re: Guy Lavoie]
|
dahlheim
junior
Registered: 12/31/08
Posts: 41
|
does this button work yet (the reset button)? i can't seem to make it work, and i believe i have done exactly what Guy is describing here, a programming error resulting in continuous serial port data and inability to connect to the controller with c-max. i am unable to reload the executive within four seconds of power-up either (serial port already in use)...
|
|
Top
|
|
|
|
|
#20876 - 02/08/09 07:36 PM
Re: Leopard stuck
[Re: Guy Lavoie]
|
dahlheim
junior
Registered: 12/31/08
Posts: 41
|
i was wondering about that. funny, the only thing i did on the pc was load in the program with the obvious error which would certainly cause transmission of eight serial messages on each program pass. the only things i am AWARE of on the pc which use that port are the Leo and HAL (to communicate with the Leo), and i made sure nothing HAL-related is running.
immediately after downloading the program to the Leo, i was getting a message saying "lost connection" when trying to connect to the controller, which made me think my "runaway" serial messages were the issue. on a computer reboot though, now i get the "serial port already in use" message no matter what i do, even if the Leo is off. i guess i need to look into how to tell if anything else is grabbing that port...
|
|
Top
|
|
|
|
|
#20877 - 02/08/09 08:02 PM
Re: Leopard stuck
[Re: dahlheim]
|
dahlheim
junior
Registered: 12/31/08
Posts: 41
|
AHA! thanks again, Guy. any chance i can pay you to stay on this forum forever? 
i don't know what was grabbing the port, but Portmon.exe (utility) said something was. i rebooted again, probably fourth or fifth time, ran portmon.exe, which then connected to the port ok (perhaps kept some other rogue thing from grabbing it? i dunno) and after a few tries was able to reload the executive quickly enough on power-up.
|
|
Top
|
|
|
|
|
#20883 - 02/09/09 02:12 PM
Re: Leopard stuck
[Re: Guy Lavoie]
|
dahlheim
junior
Registered: 12/31/08
Posts: 41
|
by the way, for the "forum files", thanks to sloppy programming i've managed to repeat the same "runaway serial messages" error and it appears to me that such behavior can cause windows to report the serial port as being in use even after one powers down the connected controller (Leo2 in my case). rebooting the windows machine with the Leo powered off, followed by running cmax, then plugging the Leo back in and quickly attempting to reload the executive eventually fixes the problem again. each time i've done this, i've run Portmon.exe (find it at microsoft's web site via google) prior to cmax, to watch the port activity. i've no idea if this step is necessary.
|
|
Top
|
|
|
|
Moderator: Dan Smith, Monte G, ADI Tech Support, Guy Lavoie
|
2747 Members
19 Forums
3837 Topics
22722 Posts
Max Online: 67 @ 08/16/11 03:08 PM
|
|
|
|
|
|
1
|
2
|
3
|
4
|
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
|
26
|
27
|
28
|
29
|
|
|
|
|
|
