StefanoGinobili
 lvl.2
Flight distance : 422818 ft
Italy
Offline
|
Hello Cetacean,
yes, I was using the same USB cable to connect the P4P to the PC and to the Mac. I just unplugged to USB cord type-A connector from the (not working) PC and plugged it to the (working well) Mac.
After your suggestion I also tryed another cable... but the result didn't changed 
The strange thing is that, in previous days, the same P4P worked well with the same PC. When I installed the firmware 1.03.0418 I remember I calibrated the P4P vision sensors using the PC.
So today I tryed to lookup for previous versions of DJI Assistant 2 and, after googling a while, I found the following:
- DJI Assistant 2 - 1.0.8
- DJI Assistant 2 - 1.1.0
And... none of them worked!
Maybe the following could be useful for DJI software engineers...
Sniffing (by Wireshark) communication between the Electron app and the underlying Root application (v1.1.0-2), I captured the following (until after the P4P has been powered on):
GET /general HTTP/1.1
Host: localhost:19870
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket
Origin: file://
Sec-WebSocket-Version: 13
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) DJIAssistant2/0.0.1 Chrome/47.0.2526.110 Electron/0.36.7 Safari/537.36
Accept-Encoding: gzip, deflate
Accept-Language: en-US
Sec-WebSocket-Key: ************
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: *************
Server: DJIDeviceService
Access-Control-Allow-Credentials: false
Access-Control-Allow-Methods: GET
Access-Control-Allow-Headers: content-type
Access-Control-Allow-Origin: file://
Date: Sun, 11 Jun 2017 18:58:50 GMT
.?{
"APP_STATUS": "in_sync",
"EVENT": "app_ver_notify"
}
.w{
"APP_VERSION": "1.1.0",
"EVENT": "app_ver",
"HASH_SERVICE": "8fa2ce06a145ca4faf4e622067122fed53b49ec8"
}
.|{
"AUTOTEST_ENABLED": false,
"DEBUGGER_ENABLED": false,
"EVENT": "debug_status",
"FACTORY_ENABLED": false
}
.`{
"CONFIG_STATUS": "ERROR",
"EVENT": "app_ui_mode",
"IS_AUTO_UPGRADE_MODE": false
}
.Q{
"EVENT": "push_system_info",
"OS_TYPE": "Win",
"OS_VERSION": 192
}
.....e... ...G...\.......&..._................~.~{
"ERROR": "SUCCESS",
"LOGIN_EMAIL": "stefano.***@***.it",
"LOGIN_STATUS": true,
"SEQ": "nhs9mczp"
}
.!{
"EVENT": "login_success"
}
While uncommenting line "mainWindow.webContents.openDevTools()" in file "%ProgramFiles(x86)%\DJI Product\DJI Assistant 2\AppFiles\main.js:113", here is what the console is logging until after the P4P has been powered on...
Hope this helps.
Thank you all ;)
|
|
Captain
First Officer
lvl.4
Second Officer
.
. Do you know if exists another kind of software talking with the P4P on a Windows PC? This just to try to understand if the issue is driver-side or application-side. Plugging the P4P RC on the same PC, the DJI Assistant app works well, but from Device Manager it seems it is not using the same "Vision (Interface 3)" driver. It uses the "DJI USB Virtual COM" driver instead.