Hi greiny,
Thanks for your interest in the Intel® Aero™ Platform for UAVs.
You are right, it is strange that the sample code only works when connecting both cameras. Please let us investigate this issue, we will contact you back as soon as we have some useful information.
Have a nice day!
Best Regards,
-Jose P.
Hello Carlos,
There's a place where I can see the module as detected which is at the ports numbering.
The option 1 was current so tried option 2, set Windows* 8.1/10 WHQL Support to Disabled and changed Boot Mode to UEFI only. This didn't changed the outcome though, same error as showed first in the thread.
Then reverted back (Windows* 8.1/10 WHQL Support Enabled) and I'm still getting that error.
Hi Gabriel,
Thanks for your interest in the Intel® RealSense™ Technology.
I would like to recommend you to take a look at the FaceTracking.cpp and FaceTracking.cs samples in the Intel RealSense SDK, those samples show how to use the face tracking features including face detection, so you may use them as a reference to your own code.
In case you are using the RealSense SDK R3, the source code of these samples is located in this path $(RSSDK_DIR)/sample/face/. Also, you can find additional information regarding the Face Tracking and Recognition Module in the SDK R3 Documentation: Face Tracking and Recognition.
Moreover, in the RealSense SDK R2, the DF_FaceTracking (C++) sample is located here: $(RSSDK_DIR)/sample/DF_FaceTracking and the DF_FaceTracking.cs here: $(RSSDK_DIR)/framework/CSharp/DF_FaceTracking.cs. Also the Face Tracking and Recognition module information can be accessed on this site: Face Tracking and Recognition.
Hope this information helps.
Regards,
-Yermi A.
OK I just installed the update KB4022716 and rebooted my computer. I then turned VHT mode back on (still running the latest Intel version 19.51.1.1) and opened about 60 tabs of YouTube in multiple Chrome sessions just to max out my Internet. It started off fine and I thought the issue was fixed. But then after about 10 minutes every device dropped off my network for about 30 seconds (same symptoms as before). I know every device dropped off my network because I have 2 chromecast casting continuously and they would disconnect. I also have a few IP cameras being recorded continuously to a server and during the outage the clips are missing.
I then checked the event log and it logged the same error as before:
5007 - TX/CMD timeout (TfdQueue hanged)
I do not know if this update addressed the lockup issue, however. I will need to a few days to know for sure.
: Thank you very much for providing that link.
Sure, remember that the Intel warranty is for 3 years. If you are interested in that option, please get in contact with Intel directly:
Chat support:
http://intelsupportchat.force.com/icslivechat/ics_tech_processor_ww_english_Chat,
For phone support, depending on your location, you will see the contact information on the links below:
EMEA contact information: http://intel.ly/28QeAF3
APAC contact information: http://intel.ly/1ITfjUF
LAR contact information: http://intel.ly/29c0rW4
North America: Phone Number 1-916-377-7000, Monday - Friday 7:00 AM to 5:00 PM (Pacific Time).
Any questions, please let me know.
Regards,
Alberto R
Hi, I have studied the example in C++, but the example is for real time and it doesn't work in my project. I am using SDK R2, because face tracking example project don't work in R3 and I think my project will not work too with R3.
So I have the image but I don't know how to make face algorithm recognize it.
Looking at your wpa_supplicant.conf file, I don’t see anything wrong. In this case I’d recommend you to re-flash your Edison to the image 159, which is available to download here: http://downloadmirror.intel.com/25028/eng/edison-image-ww25.5-15.zip, and the instructions to flash the Edison on this other site: Flashing your Board.
Let me know your results.
Regards,
-Yermi A.
Hi Alberto,
I get the same error message for both 18 and 25 for the firmware update tool.
The link you provided to the firmware is for a different NUC than the 6i7KYK. The latest BIOS I see for this NUC is 0048 dated May 24, 2017.
I have investigated more regarding what you need to accomplish and unfortunately it is an unsupported use case and cannot be done. My apologies for any inconvenience it may cause.
Regards,
-Yermi A.
Hi, sorry if this is a dumb question. I have a broken version of Python 2.7 with a horrible mix of VS libraries that I cant debug. I figure what the hey, I'll just rebuild everything from source, including SCIPY, etc, using Visual Studio FORTRAN, C++, MKL, etc. What could go wrong :-)
I have VS 2017 for C++, but only an evaluation copy of FORTRAN compiler. My assumption is that any Fortran-related DLL's, etc, that get built will all survive the loss of the compiler license, but I wanted to check first.
Thoughts?
The base frequency that Intel lists (the 1.3GHz you reference) is what can be sustained at 4.5W. It will drop to 800MHz at low CPU utilization, but that shouldn't be due to throttling most of the time. The 400MHz times you have noticed are definitely throttling, but more likely to be due to temperature rather than exceeding PL1. On my system I have only seen those frequencies when there has been a lot of heat build-up, particularly near the Esc key corner of the system.
Hi cburdick, please share the markings of your Intel(R) X710, this information is available in the white sticker label in the actual network adapter.
regards,
Vince
My question is - which version of Intel Rapid Storage Technology should
I install for the situation I describe below?
I have a Dell XPS 8100 desktop from 2010 in which I just installed a new
1TB WD Black Performance (WDC WD1003FZEX-00K3CA0) system hard drive and
it also has an old 640GB WD (WDC WD6400AAKS-75A7B0) data hard drive from
2010.
This Dell is running Windows 7 Home Premium SP1 64-bit and the original
Intel Rapid Storage Technology v9.5.0.1037, dated 10/2/2009.
After I restored a Macrium Reflect image from the old system hard drive
to the new hard drive everything appears to be working fine except that
the Temporary Internet Files settings for Internet Explorer 11 are gone.
When I try to restore and save these settings I keep getting this error
message:
Please select a value between 8 and 8 for how much disk space Temporary
Internet Files may use.
Some people are able to fix this problem by reinstalling Intel RST.
But I don't know which version of Intel RST I should install with the
original desktop components from 2010, a hard drive from 2010, and a new
system hard drive from 2017.
Which version of Intel Rapid Storage Technology should I install for the
situation I describe above?
Thanks!
Hello Mishal,
I will mark this thread as resolved by now. If you have updates just post them and we will continue with the discussion.
Last you might receive a short survey. We will appreciate if you take a couple minutes to provide some feedback.
Regards
Jose H.
Hi Kfscotde,
Please let us know if you have other assistance needed for your 82579V Ethernet controller.
Regards,
Vince
Updated the BIOS, now let's hope for the best!
Understood!
Hello RenzoT
I was asking you to enter Windows 10 Setting while you are logged within the Windows. You have probably looked in Bios settings.
Regards
Leon
rpm is for Redhat/Fedora, so that's clearly not relevant here.
I've followed the bitbake breadcrumbs as best I can and compiled icamerasrc (the particular version for the joule), but I get errors when trying to run it:
(gst-inspect-1.0:17041): GLib-GObject-CRITICAL **: g_param_spec_enum: assertion 'g_enum_get_value (enum_class, default_value) != NULL' failed
(gst-inspect-1.0:17041): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion 'G_IS_PARAM_SPEC (pspec)' failed
I do get the expected output from gst-inspect-1.0 icamerasrc:
Factory Details:
Rank none (0)
Long-name icamerasrc
Klass Source/Video
Description CameraSource Element
Author Intel
Plugin Details:
Name icamerasrc
Description Template icamerasrc
Filename /srv/maverick/software/gstreamer/lib/gstreamer-1.0/libgsticamerasrc.so
Version 1.0.0
License LGPL
Source module my-plugin-package
Binary package GStreamer
Origin URL http://gstreamer.net/
GObject
+----GInitiallyUnowned
+----GstObject
+----GstElement
+----GstBaseSrc
+----GstPushSrc
+----Gstcamerasrc
Implemented Interfaces:
GstCamerasrc3AInterface
Pad Templates:
SRC template: 'src'
Availability: Always
Capabilities:
EMPTY
Element Flags:
no flags set
Element Implementation:
Has change_state() function: 0x7f21cf5dc920
Element has no clocking capabilities.
Element has no URI handling capabilities.
Pads:
SRC: 'src'
Pad Template: 'src'
Element Properties:
name : The name of the object
flags: readable, writable
String. Default: "camerasrc0"
parent : The parent of the object
flags: readable, writable
Object of type "GstObject"
blocksize : Size in bytes to read per buffer (-1 = default)
flags: readable, writable
Unsigned Integer. Range: 0 - 4294967295 Default: 4096
num-buffers : Number of buffers to output before sending EOS (-1 = unlimited)
flags: readable, writable
Integer. Range: -1 - 2147483647 Default: -1
typefind : Run typefind before negotiating
flags: readable, writable
Boolean. Default: false
do-timestamp : Apply current stream time to buffers
flags: readable, writable
etc etc, but there is no 'device-name' as indicated in the suggested test pipeline:
gst-launch-1.0 icamerasrc device-name=0 io-mode=3 ! video/x-raw,format=NV12,width=1920,height=1080 ! vaapisink dmabuf-alloc-tiled=true So when I try to run it:
[dev] [mav@maverick-joule ~]$ gst-launch-1.0 icamerasrc device-name=0 io-mode=3 ! video/x-raw,format=NV12,width=1920,height=1080 ! vaapisink dmabuf-alloc-tiled=true
(gst-launch-1.0:17538): GLib-GObject-CRITICAL **: g_param_spec_enum: assertion 'g_enum_get_value (enum_class, default_value) != NULL' failed
(gst-launch-1.0:17538): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion 'G_IS_PARAM_SPEC (pspec)' failed
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
WARNING: erroneous pipeline: no property "device-name" in element "camerasrc0"
Hi SeanVree,
Please let me if you still need assistance regarding I219-V and I211 Ethernet Connection.
regards,
Vince