I have tried to do the OTG without success, i use Ubuntu 16.04 with DHCP server and have assigned
a static IP to the OTG device (Ugreen model, not same as the mentioned ones) based on its MAC address, but still cannot see the camera image when i retrieve it through this IP (with the same method that i retrieve it when in hotspot connection mode to my linux machine, after green wireless icon in camera is stable).
I can ping the address, but cant get it show an IPv4 in avahi-discover command for example.
Any insight on this matter would be greatly appreciated, is there any specific mode i
should enable to make the streaming work or should try again with a different OTG device perhaps ?
On your Linux DHCP server, can you see the MAC address of the USB OTG Ethernet adapter to verify that the correct device is getting an IP address?
Are the LEDs on the USB OTG adapter lit?
Turn off the Wi-Fi on your THETA V with the side button
If you are just checking connectivity, the Wi-Fi LED will be off
Do any of the client mode scripts here work. You will need to edit the script and insert the IP address assigned to the THETA from your Linux DHCP server. You will also need to use Digest Authentication for the client-mode commands and change the username and password for digest authentication. If thatās too much of a hassle, thereās a test script to find the IP address of the THETA. Make sure Wi-Fi is turned off.
Currently trying to make it a little easyer to find your theta on the networkā¦
Iām trying to setup a loop code that looks for any devices up to a current text limit and display them in a list.
Using node. Js and dns.lookup
Hopefully it will be a good tool for this forum, listing all of your connected theta devices on your ethernet hub.
**update
This current method will not work, theta will not show up.
Iāll have to try to find the device by searchingā¦
Http 192.168.x.xxx/osc/info and request a responce
The setup was as simple as giving a static IP to the MAC address of the OTG device. I notice though
that sometimes the ping to the inner address (i also set static address to all interfaces involved with their MAC addresses) is not working. I do some restarts of the DHCP server in combination with the camera reconnect and eventually i can ping it, usually it comes up after some tries in ping of the front device IP, i am still not 100% sure why this happen, so when i find a protocol about it will return with more information.
Note that after this i can access the camera flawlessly without any issue.
If anyone wants my DHCP setup files to use as sample, can contact me and i can send them.
Thanks for this information. Itās cool that people are pioneering this type of 360 camera usage and sharing information.
Does your application use the THETA with streaming, image file, or video file?
If youāre using it with image file or video file using client mode API, note that the example I provided doesnāt have the correct HTTP header. It still works in my tests, but we should probably use the correct header just in case RICOH makes the API more strict in the future. The correct header should specify:
Content-Type: application/json;charset=utf-8
Accept: application/json
The API reference and header example, Iām referring to is here:
Currently have my theta on for 19hours using the y cable,
Seams to have no use limit, (using my app that updates every second to get devices current uptime)
This is cool that you have a setup where you can see the current state of the THETA V from anywhere in your network and also send it commands. Looks like youāre really making solid progress with your project.
Thank you, Iāve given up on adding the feature of auto theta discovery, since it will be alot of work and there is much simpler things todo.
Also trying to find a way todo a full room 360 projection.
Currently I have a 180 lense on a 1080p projector,
Would be nice to enjoy and share a full room with the theta and also communicate to others as if they were in a room with you. That would be a good goal of mine for this.
(using a sample video from YouTube)
Not the best setupā¦ Just wanted to see how it would look
The expensive part would be the warping software, which you can see they donāt use in that video lol,
Iām mainly getting the same experience as that.
Just took apart my projector today to try it out,
Iāve had the lense for sometime now,
A better application would be a Lazer micro projector since as they advertise they donāt need to be focused, and controlled lighting, plus mobility.
Itās just another project on the list.
So far it seams promising.
You can see the pixels since itās 1080p so every pixel is about 1 cm x 2cm
Also I think the aim of my electron project is going to change since Iāve found out you can do a lot more with node js then Iāve expected,
Currently planning to make a page or server that receives the commands and forwards them back to a web page on the local network so any device that can use a web page can control the theta and get info from it, possibly get info about the device outside of the network as well.
Currently setting this up, and trying to setup a standard for requesting infoā¦ In a Api format.
Has anyone tested the Ethernet streaming with a Z1? I would like to see if it can hold a charge indefinitely. Also, the bigger size of the Z1 body may help with heat.
I found the problem in USB ethernet now , and it work perfectly.
USB ethernet adapter: UGREEN 100Mbps
The Theta V default set gateway to 192.168.1.1
But my home router set gateway to 192.168.96.1
That is really a problem in USB ethernet mode. Since in WIFI client mode it get IP with DHCP in a network regardless of gateway setting. But in USB ethenet mode, it require the router gateway in 192.168.1.1.
I am using the UGreen 100Mb lan adapter and i canāt find Theta V in router.
The lan led of adapter lit and it is fully functional when i connect to my notebook.
But then when i connect it to ThetaV, lan led lit but i can not found it in router.
If i connect Theta V through WIFI and client mode, i can find it in router again.
Note that in the tests, the camera is assigned an IP address from the router. So, it is going to be something like 192.168.1.100 (not the 192.168.1.1 in Access Point mode).
the camera should be in client mode.
Use the official RICOH mobile app to configure client mode on the camera before you connect the camera with Ethernet.
