On Tuesday 20 August 2013 13:07:25 Viesturs Lācis did opine:

> 2013/8/19 Gene Heskett <[email protected]>
> 
> > On Monday 19 August 2013 16:57:28 Viesturs Lؤپcis did opine:
> > > The thing is that it updates the video very slowly, it takes several
> > > seconds to update the camera image and that is not so good news.
> > > Any ideas, what can I do to improve this? Or is it how it usually
> > > work also for other users?
> > 
> > This is an IP/ethernet camera or USB?  Mine is usb, plugged into the
> > other front port on an atom D525MW board.  The wired mouse is on the
> > other port.
> > 
> > If an IP camera, using ethernet, it needs more power than an ethernet
> > port can supply, so I'm ambiguously confused as to what you meant by
> > plugging it into your router.
> > 
> > > Half a second might be nice. Any chance that the pc is too slow?
> > 
> > Cheese runs this camera in very close to real time when set to show a
> > 640x480 image.  So if thats an atom board, you should be getting
> > similar results, around 15 fps.
> 
> It is USB camera. PC is some unknown mainboard with AMD Athlon XP 2200+
> cpu, single core,1,8 gHz, 512 MB RAM. And it takes up to a 15-20 seconds
> to update camera image.
> 
> > My secondary, not yet addressed problem is in deriving a rock solid
> > mount for this nominally 30mm diameter camera, and one that also
> > represents some heat sinking, in operation it warms up about 25F. 
> > Any slippage or wibbles in the mount and the offsets are all toast. 
> > And I'd like to see the crosshairs timed from the camera output as
> > opposed to the arbitrary 640x480 centered locations as that is
> > potentially a source of heat related error as the pcb holding that
> > teeny sensor moves as the pcb grows in the heat.  But we're likely
> > stuck with that and will have to depend on the rigidity of the mounts
> > we cobble up.
> 
> My current fixture keeps the camera pretty steady, when machine moves
> around, but it is not very hard to move it by hand - that plastic case
> is not meant for tightening screws too hard.
> I think that there is pretty nice way to calibrate the camera - take
> some piece of material and drill a small hole in it. Then to check for
> camera alignment, put that drill in spindle, put that piece of material
> on table, jog the machine so that the drill is in the hole and now move
> the camera to that hole and check for the DRO values - do they match
> the previous offsets or no (or those in tool table, if you have the
> "camera tool" like I do); if there is a difference, update your offsets
> and that is it.
> 
> I edited that togle-caa.ui glade panel file a little:
> 1) I removed those 2 sliders as they were not connected in HAL file to
> anything
> 2) I added few buttons to align part with JohnT's subroutine calls from
> vcp. It looks like this:
> http://picpaste.com/camera-AVAONUNY.png
> 
> There are 2 questions:
> 1) how exactly do I get DRO values also in this camera tab? there is an
> image in wiki page and one sentence that mentions this, but I was not
> able to find detailed explanation;
> 
> 2) I almost broke my router due those damn modes!!! Executing mdi
> command by pressing a vcp button leaves LinuxCNC in joint mode. switch
> to MDI tab, back to Manual and it is world mode again. I was checking
> those alignement subroutines, pressed "start alignment" and started
> jogging to the other point to finish alignment. Guess, what happens,
> when jogging gantry machine in joint mode?!? I was few meters from the
> screen, so I could not tell from the dro, if there were axis letters or
> joint numbers.
> This issue has been mentioned previously here on mailing list, so I
> decided to register a bug report. I found this page:
> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Trackers
> 
> There are links to bug tracker on sourceforge. And I was not able to
> find, how to add new bug report. Clicking the link in the sentence "To
> submit a bug report, click
> [here]<https://sourceforge.net/tracker/?func=add&group_id=6744&atid=1067
> 44> ." brought me to list of existing bug reports. I logged in my
> sourceforge account, reopened the same link and still no chance to add
> bug report.

Veddy old bugzilla, that was the case back about RedHat 6.2, so I started 
submitting bug reports to the mailing list, which they bitched about and 
everytime they bitched I said fix bugzilla, there is no sense I have to 
read every damned bug in the database before it will enable the posting of 
a new bug.  I thought it was fixed by the time I bailed on fedora, but 
maybe not.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
My views 
<http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml>
Sometimes even to live is an act of courage.
                -- Seneca
A pen in the hand of this president is far more
dangerous than 200 million guns in the hands of
         law-abiding citizens.

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to