Re: [Elphel-support] Elphel 353 server

[Daniel Rouan]

Oleg,

I changed the cable with a spare one (for my application I had to buy longer
cables) but the result is the same.

By the way I'm doing the tests with one unique sensor (the other one is at 
another
place, far away) : is that a problem ? are the 3 connectors on the mux board  
equivalent
to make the test ?

regards,

Daniel

 
Le 9 févr. 2017 à 18:10, Oleg  a écrit :

> Daniel,
> 
> I see. Must be something wrong with either cables, sensor boards or a mux 
> board (but it was detected and programmed) - the boards are usually more 
> reliable than the cables.
> 
> If possible try to reconnect the long cables that connect the mux board 
> (0353-00-08) and sensors (0353-00-15) - see the 3D model (cables not shown).
> First try the sensor side then the mux side. 
> 
> If that doesn't work - you might have to send us the camera. Contact 
> sa...@elphel.com for details.
> 
> Best regards,
> Oleg Dzhimiev
> Electronics Engineer
> phone: +1 801 783  x124
> Elphel, Inc.

___
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com

Re: [Elphel-support] Elphel 353 server

[Daniel Rouan]

Oleg,Just after ending the previous email, I changed to the connector that  is theclosest from the DC/DC converter FKC08-48. (silver box) and the msg returnedby dmesg is changed : the sensor is found ! (see attached).But, the browser (firefox) cannot connect anymore.regards,  Daniel {\rtf1\ansi\ansicpg1252\cocoartf1038
{\fonttbl\f0\fswiss\fcharset0 Helvetica;}
{\colortbl;\red255\green255\blue255;}
\paperw11900\paperh16840\margl1440\margr1440\vieww9000\viewh8400\viewkind0
\pard\tx566\tx1133\tx1700\tx2267\tx2834\tx3401\tx3968\tx4535\tx5102\tx5669\tx6236\tx6803\ql\qnatural\pardirnatural

\f0\fs24 \cf0 Linux version 2.6.19 (andrey@inspiron) (gcc version 3.2.1 Axis release R64/1.64) #4 Thu Nov 4 20:21:16 MDT 2010\
Setting up paging and the MMU.\
On node 0 totalpages: 8192\
  DMA zone: 32 pages used for memmap\
  DMA zone: 0 pages reserved\
  DMA zone: 8160 pages, LIFO batch:0\
  Normal zone: 0 pages used for memmap\
Linux/CRISv32 port on ETRAX FS (C) 2003, 2004 Axis Communications AB\
Built 1 zonelists.  Total pages: 8160\
Kernel command line: root=/dev/mtdblock3 init=/linuxrc rootfstype=jffs2\
PID hash table entries: 256 (order: 8, 1024 bytes)\
Dentry cache hash table entries: 8192 (order: 2, 32768 bytes)\
Inode-cache hash table entries: 4096 (order: 1, 16384 bytes)\
Memory: 41376k/65536k available (1740k kernel code, 24160k reserved, 605k data, 72k init)\
Calibrating delay loop... 199.47 BogoMIPS (lpj=997376)\
Mount-cache hash table entries: 1024\
NET: Registered protocol family 16\
SCSI subsystem initialized\
usbcore: registered new interface driver usbfs\
usbcore: registered new interface driver hub\
usbcore: registered new device driver usb\
NET: Registered protocol family 2\
IP route cache hash table entries: 512 (order: -2, 2048 bytes)\
TCP established hash table entries: 2048 (order: 0, 8192 bytes)\
TCP bind hash table entries: 1024 (order: -1, 4096 bytes)\
TCP: Hash tables configured (established 2048 bind 1024)\
TCP reno registered\
Check hardware configuration of Elphel 353 camera\
Elphel 10349/10369 IO extension board is not present\
fast_timer_init()\
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.\
io scheduler noop registered (default)\
Serial: CRISv32 driver $Revision: 1.78 $ <6>ttyS0 at I/O 0xb0026000 (irq = 68) is a CRISv32\
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize\
PPP generic driver version 2.4.2\
ETRAX FS 10/100MBit ethernet v0.01 (c) 2003 Axis Communications AB\
eth0: changed MAC to 00:40:8C:CD:00:00\
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2\
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx\
ide: ETRAX FS built-in ATA DMA controller\
ide: Elphel 353 io extension board not found, skipping initialization\
Initializing USB Mass Storage driver...\
usbcore: registered new interface driver usb-storage\
USB Mass Storage support registered.\
usbcore: registered new interface driver usbserial\
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic\
usbcore: registered new interface driver usbserial_generic\
drivers/usb/serial/usb-serial.c: USB Serial Driver core\
drivers/usb/serial/usb-serial.c: USB Serial support registered for Belkin / Peracom / GoHubs USB Serial Adapter\
usbcore: registered new interface driver belkin\
drivers/usb/serial/belkin_sa.c: USB Belkin Serial converter driver v1.2\
drivers/usb/serial/usb-serial.c: USB Serial support registered for cp2101\
usbcore: registered new interface driver cp2101\
drivers/usb/serial/cp2101.c: Silicon Labs CP2101/CP2102 RS232 serial adaptor driver v0.07\
drivers/usb/serial/usb-serial.c: USB Serial support registered for Garmin GPS usb/tty\
usbcore: registered new interface driver garmin_gps\
drivers/usb/serial/garmin_gps.c: garmin gps driver v0.28\
drivers/usb/serial/usb-serial.c: USB Serial support registered for MCT U232\
usbcore: registered new interface driver mct_u232\
drivers/usb/serial/mct_u232.c: Magic Control Technology USB-RS232 converter driver z2.0\
drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303\
usbcore: registered new interface driver pl2303\
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver\
ETRAX FS stream co-processor driver v0.01, (c) 2003 Axis Communications AB\
stream co-processor: init done.\
axisflashmap: ...\
NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3,3V 8-bit)\
Additional Info: ID byte3=0x0, byte4=0x1d\
Bad block table found at page 65472, version 0x01\
Bad block table found at page 65408, version 0x01\
Flash is rated 30 ns, modifying bif_core_rw_grp3: old=0x6300483, new=0x631\
NAND 128MiB 3,3V 8-bit: 0x0800 bytes of NAND flash memory.\
axisflashmap: Set to boot from NAND flash, making NAND flash primary device.\
axisflashmap: flash read 512 bytes at 0x0004, data: 00 b0 05 f0 25 ff ed 9c\
axisflashmap: partition table offset 10, data: ef be 84 00 2d 0e 00 00\
axisflashmap: Found a valid partition table at 0xc02fd9ae-0xc02fda3a.\
offset 

Re: [Elphel-support] Elphel 353 server

[Daniel Rouan]

Oleg,

Sorry for the flood of messages…

Apparently I can send commands through the port 8081, such bimg, but for 
instance
the image returned is 1 px gif.  As if the sensor was not actually running.

Is there some command to make a deeper test ?

Daniel

Le 10 févr. 2017 à 13:36, Daniel Rouan  a écrit :

> Oleg,
> 
> Just after ending the previous email, I changed to the connector that  is the
> closest from the DC/DC converter FKC08-48. (silver box) and the msg returned
> by dmesg is changed : the sensor is found ! (see attached).
> 
> But, the browser (firefox) cannot connect anymore.
> 
> regards,
> 
>   Daniel
> 
>  
> 
>  
> Le 10 févr. 2017 à 13:15, Daniel Rouan  a écrit :
> 
>> Oleg,
>> 
>> I changed the cable with a spare one (for my application I had to buy longer
>> cables) but the result is the same.
>> 
>> By the way I'm doing the tests with one unique sensor (the other one is at 
>> another
>> place, far away) : is that a problem ? are the 3 connectors on the mux board 
>>  equivalent
>> to make the test ?
>> 
>> regards,
>> 
>>  Daniel
>> 
>>  
>> Le 9 févr. 2017 à 18:10, Oleg  a écrit :
>> 
>>> Daniel,
>>> 
>>> I see. Must be something wrong with either cables, sensor boards or a mux 
>>> board (but it was detected and programmed) - the boards are usually more 
>>> reliable than the cables.
>>> 
>>> If possible try to reconnect the long cables that connect the mux board 
>>> (0353-00-08) and sensors (0353-00-15) - see the 3D model (cables not shown).
>>> First try the sensor side then the mux side. 
>>> 
>>> If that doesn't work - you might have to send us the camera. Contact 
>>> sa...@elphel.com for details.
>>> 
>>> Best regards,
>>> Oleg Dzhimiev
>>> Electronics Engineer
>>> phone: +1 801 783  x124
>>> Elphel, Inc.
>> 
> 

___
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com

Re: [Elphel-support] Elphel 353 server

[Daniel Rouan]

Many thanks Oleg for your advices.

It works now with the sensor connected to J2.

The web server is now OK and I got images.

Finally it was indeed a question of cable and proper connection.

By the way the small plastic clip that presses the cable on the pins of the 
connector 
is broken and I replaced it by a piece of cardboard (rapped with several pieces 
of scotch
tape to reach the right thickness) inserted together with the cable end:  this 
may explain 
a previous bad connection.

regards,

   Daniel
 
Le 10 févr. 2017 à 15:14, Oleg  a écrit :

> Daniel,
> 
> So, your current connections are (10359 - mux board (its connectors are 
> marked as J1-4), 10353 - system board):
> 10359 J1 - 10353
> 10359 J2 - sensor
> 
> J1 is for the system board.
> One of the sensors sould always be connected to J2, so:
> * If the sensor is single it should go to J2.
> * If 2 sensors then J2 and J3 (or J2 and J4)
> 
> What's the firmware revision, btw - 8.2.16 ?
> 
> Try:
> 1. in telnet:
> mv /etc/autocampars.xml /etc/autocampars.xml_bkp
> sync
> reboot -f
> Check the 'dmesg' output.
> 
> This will generate a new configuration file. It could have been generated for 
> other connection scheme where no sensors were detected at the 1st boot after 
> firmware update.
> 
> 
> 2. If you connect the sensor directly to the system board and regenerate the 
> config file (as in 1.) - and the sensor gets detected - then you should be 
> able to get images. After 
>  
> Note:
> if the camera gets stuck at 'starting hardware sequencers', in telnet:
> killall -9 php
> There won't be images but the web server will work. 
>  
> Best regards,
> Oleg Dzhimiev
> Electronics Engineer
> phone: +1 801 783  x124
> Elphel, Inc.

___
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com

[Elphel-support] sensor board, informations

[julie]

Hi, :-)

I'm in a french team of film makers, and we want to build an open source
camera. We are looking for an high or average definition (at least
1920x1080) open source Sensor Board compatible with raspberry Pi,  that
could allow use to use any objective (including old photographic
objective). We wanted to create a snapPi cam but with a better sensor
board that the ones sold by adafruit Raspberry pi compagny.

I see you sell a lot of open hardware  camera components (393...)
including sensor boards, do you have any sensor compatible with
Raspberry Pi  ?

What connexions do you use for your sensor boards ?

Yours sincerely


Julie Go


___
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com

Re: [Elphel-support] sensor board, informations

[Elphel Support]

Hello Julie,

I'm afraid we can not help you with the sensor boards compatible with Raspberry 
Pi - our sensor boards are only compatible with the earlier Elphel cameras, 
designed more than 10 years ago. All our sensor boars use the 30-conductor flex 
cables - we can use both standard 0.5 mm pitch flex cables and our improved 
(shielded signals, thick power lines) ones, compatible with both parallel (up 
to 14 bit) and high speed serial (up to 8 differential pairs + clock pair).

All Elphel cameras are designed around FPGA that is used for image 
processing/compression - it is not the case with the Pi.

Andrey

 On Fri, 10 Feb 2017 03:17:48 -0800 julie wrote 
 

  Hi, :-)
  I'm in a french team of film makers, and we want to build an open source 
camera. We are looking for an high or average definition (at least 1920x1080) 
open source Sensor Board compatible with raspberry Pi,  that could allow use to 
use any objective (including old photographic objective). We wanted to create a 
snapPi cam but with a better sensor board that the ones sold by adafruit 
Raspberry pi compagny. 
 
 I see you sell a lot of open hardware  camera components (393...) including 
sensor boards, do you have any sensor compatible with Raspberry Pi  ?
 What connexions do you use for your sensor boards ? 
 
 Yours sincerely 
 
 
 
 Julie Go
 
 
 
 ___ 
Support-list mailing list 
Support-list@support.elphel.com 
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com 





___
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com