Connection error after lights working fine for awhile???

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Simply letting the lights run
2.
3.

What is the expected output? What do you see instead?
Lights should keep displaying, but after awhile I get a connection error and 
they just shut off..rebooting they work again....  This didn't happen to me 
before when I had 50 LED but I added 50 more.  I have ample power supply so not 
sure what is going on

What version of the product are you using? On what operating system?
Windows 7 latest Prismatik

Please provide any additional information below.

Original issue reported on code.google.com by Newyears...@gmail.com on 24 May 2013 at 3:30

[GoogleCodeExporter]

Also I thought maybe I had connection issues but unplugging my USB to my 
Arduino..the lights flash their proper working test...

Also..using Arduino and Adalight software the lights work fine even after they 
stop in Prismatik..so clearly something is happening with Prismatik.

Original comment by Newyears...@gmail.com on 24 May 2013 at 3:32

[GoogleCodeExporter]

could you please attach log file with maximum log level (Experimental->Log 
level = 3)? 

Original comment by tim.hell...@gmail.com on 24 May 2013 at 12:00

• Changed state: MoreInfoNeeded

[GoogleCodeExporter]

could you please attach log file with maximum log level (Experimental->Log 
level = 3)? 

Original comment by tim.hell...@gmail.com on 24 May 2013 at 12:00

[GoogleCodeExporter]

I will turn logging on and attach it when it happens again.

Last night it ran all night fine and still on in the morning..just now it quit 
again.  When it quits it must be hardware related because going into Processing 
arduino software throws an array error for the com port.

If I unplug the USB and back in the lights flash through their normal working 
pattern..but still gives me the error..simply rebooting solves it.

I will attach log file soon as I have it.

Original comment by VacDo...@gmail.com on 25 May 2013 at 8:24

[GoogleCodeExporter]

ALso where are the log files stored? 

Original comment by VacDo...@gmail.com on 25 May 2013 at 8:24

[GoogleCodeExporter]

Hey..usually I have to reboot to get them going..this time I just closed 
Prismatik and ran it as administrator and now they have come back on????  Could 
it be related to that??? Normally quitting it and starting it back doesn't 
work..in fact I just tried it a min ago..didnt work..tried with admin this time 
and now it worked without rebooting.

Original comment by VacDo...@gmail.com on 25 May 2013 at 8:26

[GoogleCodeExporter]

Okay it messed up again.  Where can I find the log file?

Original comment by Newyears...@gmail.com on 26 May 2013 at 11:23

[GoogleCodeExporter]

Uhh..the log file is like 17 Gigs...one of them anyways..there are a bunch 
labeled log.0 log.1 etc..which one do I post?

Original comment by Newyears...@gmail.com on 26 May 2013 at 11:26

[GoogleCodeExporter]

Original comment by Newyears...@gmail.com on 26 May 2013 at 11:27

Attachments:

• Prismatik.4.log

[GoogleCodeExporter]

18:29:43:797 Warning: virtual void LedDeviceAdalight::open() Serial device 
"COM3" open fail 

This is the error I keep getting..appears my com port stops responding..the 
last few times I have been able to unplug, replug, run Prismatik as admin and 
it starts working again...???

Original comment by Newyears...@gmail.com on 26 May 2013 at 11:35

[GoogleCodeExporter]

Original comment by tim.hell...@gmail.com on 27 May 2013 at 10:17

• Changed state: Accepted

[GoogleCodeExporter]

My guess is that maybe my PSU is not powerful enough and my USB power is 
fluctuating causing the com port to drop (or act as if the USB to arduino was 
unplugged)

I have put a powered USB hub to see if solves the issue.

Original comment by Newyears...@gmail.com on 29 May 2013 at 12:55

[GoogleCodeExporter]

i believe it is Prismatik's bug, which we encountered before.

Original comment by tim.hell...@gmail.com on 29 May 2013 at 10:56

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

My lights ran fine for nearly 2+ days this time..then last night I went to 
bed..turned the lights off with the hotkey..turned TV off (I leave my HTPC 
on)...came back in morning and the error is back.

I have not tried running another software and see if the bug happens..might 
have to try that to see if it's the software causing it or something else.

But since you say you think is Prismatik bug..that's good to know..but any idea 
of the problem? Or a solution?

Also, once the bug happens the com port is inaccessible until I reboot..even if 
I run Ambibox or Arduino processing software they both can't access the port.

Seems hardware issue but you are saying a bug might be causing this to happen?  
Also I didn't remember this problem happen when I had 50 LED, it started after 
I added 50 more LED.

Original comment by Newyears...@gmail.com on 29 May 2013 at 3:12

[GoogleCodeExporter]

Would plugging into a 3.0 or 2.0 point make any difference?  Or is that 
unrelated?  I use a 2.0 but could try a 3.0?

Original comment by Fulfille...@gmail.com on 29 May 2013 at 4:12

[GoogleCodeExporter]

I will try Ambibox tonight and see if the problem stops..but I much prefer 
Lightpack..I hope you guys can fix it..if so I will donate! :)

Also the Aero issues.

Original comment by Newyears...@gmail.com on 29 May 2013 at 4:53

[GoogleCodeExporter]

Wll I tried Ambibox and I cant even get it to work..with playclaw it has MUCH 
better FPS with Aero than lightpack but it would never work right so I cant 
even test it :( 

Original comment by Newyears...@gmail.com on 30 May 2013 at 12:54

[GoogleCodeExporter]

what do you mean saying "never work right"?

Original comment by tim.hell...@gmail.com on 30 May 2013 at 2:05

[GoogleCodeExporter]

I finally got Ambibox working and lights quit there too..so is hardware 
related..I have no reformatted my system and I left off some devices and 
drivers to see if that helps..so far lights have ran for 24 hours..only problem 
is they wont work in XBMC now...in any mode..they flicker on then shut off..not 
sure why? doesnt matter if I have it on WinAPI or D3D.

I have XBMC set to fullscreen window mode..normally prismatik works but now 
doesnt...not sure why???

Original comment by Fulfille...@gmail.com on 30 May 2013 at 11:48

[GoogleCodeExporter]

Bah.somehow i turned on dead zone..so thats why..nevermind is working now.  I 
will report back later...see how long they work..maybe it was a driver conflict.

Original comment by Fulfille...@gmail.com on 30 May 2013 at 11:51

[GoogleCodeExporter]

I Just wanted to update you even though I don't hear from you often.  I 
determined Prismatik wasn't the problem as the same thing happened in Ambibox 
once I Got it going.  

I determined it wasn't some conflicting drivers I Thought it might be.

SO then I pulled my Arduino off the mount on my TV and took it out of the 
box..I noticed when moving it..touching it slightly it would reproduce the 
error.  I think my wiring was loose and or faulty and causes the port to short 
out as I could manually cause the issue repeatedly with touching the board.  I 
rewired with new wires and removed sticky tape of back of arduino and now have 
set it on the table on a plastic case..and so far it has worked for 24 hours..I 
think my issue was when I added 50 more LED I must have pulled some wires semi 
loose OR there was interference  from not being fully closed and touching 
contacts to the TV.

I will update you again later...so far so good. 

Original comment by Newyears...@gmail.com on 1 Jun 2013 at 6:59

[GoogleCodeExporter]

Just an update: They are still working as of right now..that's over 36 hours 
straight now...so I think I have fixed it..not software after all!  Yay!

Will keep you updated.

Original comment by Newyears...@gmail.com on 2 Jun 2013 at 6:14

[GoogleCodeExporter]

thank you Newyears1978. Sorry for such a long period of silence, we are still 
working on software and we have a little time for responses, but we pay 
attention to every update we get, and sometimes we have nothing to answer and 
current tasks keep us away from investigation. I'm glad you've resolved the 
problem, and thanks for sharing the solution with us!

Original comment by tim.hell...@gmail.com on 1 Jul 2013 at 8:20

• Changed state: Done