Y-Cam Camera

[purps]

OK, I made a Y-Cam template and checked it in.... I think.

I'm assuming one would need to do a sqlCVS Update before the new template is available?

Matt, following confirmation of the above, if you would be so kind as to test it and let us know how you get on. If you have tried to install the camera already, please remove it in web admin, reset the camera to factory settings, reboot your core (just to be safe).

Cheers,
Matt.

[tschak909]

Did you check it in using sqlcvs diff?

If so, please make sure you've checked in both the DCE and IR repositories. (The template is stored in the DCE tables, the code is stored in the IR tables)

-Thom

[gtsupport]

Hi guys,

Many thanks to Purps for trying to setup a new template for this camera.  Just a note, my MAC address for the camera is 00:0D:F0:55:CB:7B which doesn't fall within the range suggested in this thread.  This aside, I'm sure I can alter this in the template afterwards.

I am just in the middle of a firmware upgrade for the camera, which will reset everything to factory afterwards.  I'll try and add it then with the new template.  Just a quick one though, how do I get, or make sure I've already got the new template?
*Just checked and there isn't a template for it yet*

Great response from everyone else as well, thanks guys, the community spirit is flying high! 

Matt

[purps]

Did you check it in using sqlcvs diff?

If so, please make sure you've checked in both the DCE and IR repositories. (The template is stored in the DCE tables, the code is stored in the IR tables)

-Thom

Yes, diff. I checked in everything DCE related, but not IR, will do it again.

[purps]

Hi guys,

Many thanks to Purps for trying to setup a new template for this camera.  Just a note, my MAC address for the camera is 00:0D:F0:55:CB:7B which doesn't fall within the range suggested in this thread.  This aside, I'm sure I can alter this in the template afterwards.

I am just in the middle of a firmware upgrade for the camera, which will reset everything to factory afterwards.  I'll try and add it then with the new template.  Just a quick one though, how do I get, or make sure I've already got the new template?
*Just checked and there isn't a template for it yet*

Great response from everyone else as well, thanks guys, the community spirit is flying high! 

Matt

I'll add another MAC range to the template.

In theory the camera should be PnP once all this is in place. Have you done a sqlcvs update?

Cheers,
Matt.

[purps]

Template modified and checked in (dce and ir repositories).

[gtsupport]

I've just completed the sqlcvs update, and can't find the new template.  Can you tell me the number of the template, I'll try and select it that way?

Even with everything on the camera set back to factory, it doesn't seem to work on the orbiter, still working fine in the browser.  One question, I remember reading about the IP address range that the core issues, its given my camera a 192.168.80.130 address, which as I remember is for hardware outside of the LinuxMCE system.  Am I right about this, and does it matter?

I've got further questions that might be related to this, but I'm going to start another thread, as it will get too mixed up otherwise.

Thanks all.

Matt.

[purps]

It may take a while to find its way in, I have no idea what the procedure is, timescales etc after it has been checked in.

Make sure the network cable is unplugged when you reset to factory settings, remove the camera in web admin, then reset the core. When core has restarted, then plug your camera back in - this is crucial. The whole point of the template is that it makes the camera PnP i.e. orbiter should pop up with a message saying that your Y-Cam has been detected. This may not be necessary, but let's play it safe (this is what has worked for me with the Panasonic for example). The only thing that should be left to do is to set the username and password in the camera's admin page (use "dceadmin" and "dcepass" for now).

Cheers,
Matt.

[gtsupport]

Righto, off to try that now...

No joy.  The sqlcvs was updated, I checked all the dce and IR boxes, it said it finished successfully.  Rebooted the core, then plugged the camera in.  Nothing on the core, or other MD to tell me that anything was detected.

One thing I just thought of regarding mac addresses, at the moment its plugged via cable to the internal network, it also has a wireless mode which will be used later once I've moved the wireless router to the internal network.  Perhaps this will have a mac address within the range discussed earlier??

it still works in the browser, so I can make use of it for now, perhaps it takes time for the new template to get into the system, and onto my core?

Thanks for the help.

Matt.

[purps]

FYI the template is called "Y-Cam IP Camera" and is # 2163.

[gtsupport]

Ah, that template is not found so I will leave it overnight, and try a sqlcvs update tomorrow.  Hopefully it'll appear by then.

Matt

[DragonK]

Matt,

I had a problem with a different template that I couldn't get to. Here is the reply from another thread that worked for me.

Did you select all repos, or did you select all tables within dce? Make sure to not do the former, but only the latter

So only choose the tables wintin DCE to update.


Karel

[Marie.O]

sqlCVS can be a bitch. When you create new templates, make sure to
* Add the manufacturer, followed by a diff commit for the IR repo
* Add the template codes, followed by a diff commit for IR repo
* Diff commit the DCE repo
* Try to get a hold of someone with sqlCVS approval priviliges to approve your batches

The ticket to success with sqlCVS is micro commit stuff, and make sure to commit the dependent records (IR repo stuff) first.

[purps]

Karel, I just selected everything in dce and everything in ir, I didn't select everything.

Possy, when I go into sqlCVS now, it says "no changes" (unsurprisingly), does this mean it was successful?

Cheers,
Matt.

[Marie.O]

It means, sqlCVS can't find any changes