<< return to Pixycam.com

SOLVED — Pixy firmware 2.0.5: Signature Data Being Lost (Again)

Pixy Software
#1

UPDATE Problem is solved with new firmware 2.0.8.
http://cmucam.org/attachments/download/1155/pixy_firmware-2.0.8.hex

I’ve updated the firmware to version 2.0.5 and PixyMon to 2.0.4.

I defined 4 colours with PixyMon, then disconnected the USB cable and connected the camera to an Arduino. Signatures were lost.

I double-checked back with PixyMon: no signatures.

I performed the test 3 times: define signatures, unplug, replug: same results.

So I had no alternative but to downgrade firmware to 1.0.2.

Could you please confirm this issue and fix it?

This seems to be the same issue as with the previous version 1.0.2 discussed at http://www.cmucam.org/boards/8/topics/4056?r=4401#message-4401, except that the issue was raised randomly and not at 100%.

Thank you and best regards,

#2

This is definitely not being seen on our end. Although there have been some changes on how Pixy deals with corrupt flash… Do you have more than 1 pixy you can test with? Also – try selecting action->restore default parameters before setting signatures, see if that changes things.

#3

I did perform a “Restore default parameter values” and double-checked the issue before reporting it.

I’ve just tried one more time:

  • update firmware to 2.0.5
  • perform a “Restore default parameter values”
  • disconnect and connect the camera
  • define signatures
  • check the signatures are operational
  • disconnect and connect the camera
  • check again the signatures: all gone!

I only have one Pixy and it works fine with the previous release. I’m using Mac OS X.

So I’m sorry to confirm the issue with my Pixy on firmware 2.0.5.

I’ve downgraded to 1.0.2 and the Pixy works fine as expected.

Please find the trace.

Pixy programming state detected.
Programming... (/Users/ReiVilo/Desktop/smartCamera/CMUcam5 Pixy/pixy_firmware-2.0.5.hex)
done!
Please wait a few seconds while Pixy resets...
Pixy detected.
> runprogArg 8 1
response: 0 (0x0) 
error: Pixy has stopped working.
Pixy detected.
> runprogArg 8 1
response: 0 (0x0) 
error: Pixy has stopped working.
Pixy detected.
> runprogArg 8 1
response: 0 (0x0) 
> cc_clearAllSig
response: 0 (0x0) 
> run
> prm_restore
All parameters have been erased and restored to their defaults!
response: 0 (0x0) 
> close
> Pixy detected.
> runprogArg 8 1
response: 0 (0x0) 
> runprog 8
response: 0 (0x0) 
> runprogArg 8 1
response: 0 (0x0) 
> runprogArg 8 1
response: 0 (0x0) 
> runprog 8
response: 0 (0x0) 
> runprog 0
response: 0 (0x0) 
> runprogArg 8 1
response: 0 (0x0) 
> cam_getFrame 0x21 0 0 320 200
response: 0 (0x0) 
> cc_setSigRegion 0 1
HINT(REG1)  region (user-selected region)? (select region with mouse) 142 66 26 26
Signature set!
response: 0 (0x0) 
> runprogArg 8 1
response: 0 (0x0) 
> cam_getFrame 0x21 0 0 320 200
response: 0 (0x0) 
> cc_setSigRegion 0 5
HINT(REG1)  region (user-selected region)? (select region with mouse) 161 65 30 29
Signature set!
response: 0 (0x0) 
> runprogArg 8 1
> response: 0 (0x0) 
> cam_getFrame 0x21 0 0 320 200
response: 0 (0x0) 
> cc_setSigRegion 0 4
HINT(REG1)  region (user-selected region)? (select region with mouse) 153 75 34 42
Signature set!
response: 0 (0x0) 
> runprogArg 8 1
> response: 0 (0x0) 
> cam_getFrame 0x21 0 0 320 200
response: 0 (0x0) 
> cc_setSigRegion 0 3
HINT(REG1)  region (user-selected region)? (select region with mouse) 169 84 40 40
Signature set!
response: 0 (0x0) 
> runprogArg 8 1
> response: 0 (0x0) 
error: Pixy has stopped working.
Pixy detected.
> runprogArg 8 1
> runprogArg 8 1
response: 0 (0x0) 
> runprogArg 8 1
response: 0 (0x0) 
> runprog 8
response: 0 (0x0)
#4

The way Pixy deals with corrupt flash is different in this release. Something isn’t quite right with your pixy’s flash which is why I think you are losing signatures between power cycles. You’re welcome to use the release you prefer… but there’s a problem (likely) that’s being ignored and might bite you later!

How are you powering your Pixy?

#5

I’m powering the Pixy through USB.

Are you suggesting my Pixy is defective?

#6

Hi all,

I can report this is happening with my Pixy as well: I cannot make it through more than one
action before the display says “error: Pixy has stopped working.”. For example when I try
to train a signature it works. But when I then try the pan/tilt demo it only works for about
20 seconds and then:

cc_setSigRegion 0 1
HINT(REG1) region (user-selected region)? (select region with mouse) 109 49 113 119
Signature set!
response: 0 (0x0)
runprogArg 8 1
response: 0 (0x0)
cam_getFrame 0x21 0 0 320 200
response: 0 (0x0)
cc_setSigRegion 0 1
HINT(REG1) region (user-selected region)? (select region with mouse) 180 138 48 45
Signature set!
response: 0 (0x0)
runprogArg 8 1
response: 0 (0x0)
runprog 2
response: 0 (0x0)
error: Pixy has stopped working.
Pixy detected.
runprogArg 8 1
response: 0 (0x0)
error: Pixy has stopped working.
Pixy detected.
runprogArg 8 1
response: 0 (0x0)

Even if I leave the Pixy stopped but plugged in I get these messages about once a minute or more.

All the Best

#7

An addition note in case it helps track this down; While leaving the pixy idle (not running any actions)
but plugged in, as I mentioned I get several repeated stops and starts. But additionally I just saw this
message:

runprogArg 8 1
error: Pixy has stopped working.
error: procedure unsupported.
Pixy detected.
runprogArg 8 1
error: Pixy has stopped working.
Pixy detected.
runprogArg 8 1
response: 0 (0x0)
error: Pixy has stopped working.
Pixy detected.
runprogArg 8 1
response: 0 (0x0)

#8

Hi Trent,
Your Pixy is having trouble with USB communications. I suspect your USB cable – do you have another cable you can try? Also, what OS are you using?

thanks!

#9

Hi Rei,
Your Pixy is possibly defective. Some people are experiencing flash issues when using their own power supplies, but never with USB. We’ll contact you.

thanks!

#10

Hello all,
We corresponded with Rei and concluded it was not a hardware issue and found a way to improve the firmware. We just posted (2.0.6 PixyMon, 2.0.8 firmware) that fixes this issue. Download the PixyMon package which includes the new firmware. You’ll be asked if you want to upgrade your firmware when you run PixyMon.

http://cmucam.org/projects/cmucam5/wiki/Latest_release

Thank you!