Aurora installed, but crashes when opening

Message Topic Search Topic Options Post Reply Create New Topic Printable Version

   Tease!

Am going to have the pass the buck on to Michael on this one. Sorry.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version
LightChristmas Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Beta Testers Joined: 15 Oct 2007 Location: Equality, IL Online Status: Offline Posts: 993	Quote Reply Posted: 08 Sep 2008 at 9:18pm
	Tease! Am going to have the pass the buck on to Michael on this one. Sorry.


Jonathan Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Beta Testers Joined: 07 Sep 2008 Location: SoCal Online Status: Offline Posts: 1237	Quote Reply Posted: 08 Sep 2008 at 9:10pm
	Ok, so now I have two "networks". One for the USB485 (COM 4) and one for wiLink (COM 5). No 340 error message in sequencer... ...but... ...wait for it... ...Scheduler STILL won't open! Exact same error as before. (http://picasaweb.google.com/JDalquist/Misc?authkey=liRAJMnmwA8#5243340308749911074)
	~Jonathan

LightChristmas Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Beta Testers Joined: 15 Oct 2007 Location: Equality, IL Online Status: Offline Posts: 993	Quote Reply Posted: 08 Sep 2008 at 8:08pm
	EUREKA!!!! The only way that I could generate an EC 340 was to leave the Network entry blank! You need to complete both items in the Serial Network Config box. Network Number should be set to Net1 and the COM port set to 4. As an analogy, when we were running Spectrum, it was essentially Network 1, even though we had no extra choices. Under Aurora, we can have MANY networks as defined by the controller configuration. This way you could have the RS485 dongle controlling lights in your yard on Network1 and controlling another set of controllers via WiLink on Network2; or any of an almost infinte number pf combinations. Edited by LightChristmas - 08 Sep 2008 at 8:14pm


Jonathan Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Beta Testers Joined: 07 Sep 2008 Location: SoCal Online Status: Offline Posts: 1237	Quote Reply Posted: 08 Sep 2008 at 4:42pm
	I haven't set any COM ports up yet in Aurora. Would they be the same as they were for Spectrum? In my case, COM4 was the USB485, and COM 5 was wiLink. Without hooking anything up I tried to add a new "network" for COM 5, but I got a 340 error and the program exited. When I get a chance I'll drag the controllers and out plug them in to see if that makes a difference. As of now, I do not have any "network" set up. So instead I unplugged the mouse completely and used the touch pad. I had the same error message scheduler always shows me, and the program shut down. Back to square one.
	~Jonathan

autotime Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 05 Sep 2008 Location: alaska Online Status: Offline Posts: 39	Quote Reply Posted: 07 Sep 2008 at 10:46pm
	i am having problems when program open when i start a new sequence it loads then just exits program.. is there a quick fix for this??? thanks tim


LightChristmas Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Beta Testers Joined: 15 Oct 2007 Location: Equality, IL Online Status: Offline Posts: 993	Quote Reply Posted: 07 Sep 2008 at 10:32pm
	Going to go waaay out on a limb here, but is there a possibility that your mouse is using the same com port as Aurora and or the scheduler? In Aurora Sequencer, change the com port to some high number (like 5) and see what happens.


Jonathan Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Beta Testers Joined: 07 Sep 2008 Location: SoCal Online Status: Offline Posts: 1237	Quote Reply Posted: 07 Sep 2008 at 8:38pm
	Yes, as part of my own troubleshooting I uninstalled 1.0.0 and installed 1.0.0b. The only difference I noticed is that 1.0.0b installed the full program version and did not require me to unlock the demo. (Maybe it remembered that info from the first install, I don't know.) I've had several restarts since then just to be sure. With scheduler, there seems to be a link between where on the screen the mouse is at when the program opens and when the program fails. Not clicking anything mind you, but just mouseover. Let me show you what I mean. I've uploaded a short video clip of what happens whenever I open Scheduler: http://picasaweb.google.com/JDalquist/Misc?authkey=liRAJMnmwA8#5243452112963499650
	~Jonathan

LightChristmas Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Beta Testers Joined: 15 Oct 2007 Location: Equality, IL Online Status: Offline Posts: 993	Quote Reply Posted: 07 Sep 2008 at 6:24pm
	Have you installed ver 1.00b or are you still using 1.0? If not, it might be a good idea to do so.


Jonathan Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Beta Testers Joined: 07 Sep 2008 Location: SoCal Online Status: Offline Posts: 1237	Quote Reply Posted: 07 Sep 2008 at 6:14pm
	I don't get that far, although I can see the calender in the background. I just open up the program and the error pops up immediately. I have the choice of saying Ok or Cancel, but both cause the program to end. On rare occasion the error doesn't pop up and I can fiddle around with the program. But there is no pattern that seems to indicate why that might be the case. Out of the last ten times I tried to open the program, it only opened twice. Withf the two times the program opened, a mouseover random days caused the same error message to appear and again shut it down.
	~Jonathan

LightChristmas Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Beta Testers Joined: 15 Oct 2007 Location: Equality, IL Online Status: Offline Posts: 993	Quote Reply Posted: 07 Sep 2008 at 5:04pm
	As far as the scheduler goes, is it crashing as soon as you click on the calendar, or what? NMI