search

Bin4ry / deejayeye-modder

Other
358 stars 143 forks source link

responnds as if my syntax is wrong at the prompt. I'm using the standard recommended approach: #233

Open salukikev opened 2 years ago

salukikev commented 2 years ago

I followed the procedure everyone seems to recommend to pair a mismatched mainboard and gimbal. Following along, I get to the command prompt step: "py comm_og_service_tool.py com4 WM160 GimbalCalib JointCoarse" (I'm told WM160 works for Mini2 as well as Mini1- though it's not cited as such) Each time I enter this line and assorted variations I get reply with the usage instructions as below:

C:\DJI>py comm_og_service_tool.py com4 WM160 GimbalCalib JointCoarse usage: comm_og_service_tool.py [-h] (--port PORT | --bulk) [-b BAUDRATE] [-w TIMEOUT] [--dry-test] [-v] [--version] product command ... comm_og_service_tool.py: error: argument product: invalid choice: 'COM4' (choose from 'A2', 'P330', 'P330V', 'P330Z', 'P330VP', 'WM610', 'P3X', 'P3S', 'MAT100', 'P3C', 'MG1', 'WM325', 'WM330', 'MAT600', 'WM220', 'WM620', 'WM331', 'MAT200', 'MG1S', 'WM332', 'WM100', 'WM230', 'WM335', 'WM240', 'WM245', 'WM246', 'WM160', 'WM231', 'WM232', 'WM260')

C:\DJI>

What's going on here?

kilrah commented 2 years ago

--port PORT So you need --port COM4, not just COM4

salukikev commented 2 years ago

Ok, yeah. Thanks! I actually figured it out, I guess I also need -vv. My working command looks like this now: "py comm_og_service_tool.py --port com4 -vv WM160 GimbalCalib LinearHall"

which is quite strange because this video and others all format the command as I referenced and it works for them. Weird. I also solved the mystery of the disappearing COM port by first running "DJI assistant for Consumer Drones" (which includes M2) that holds the Serial port opened else it is viewed only as Mass Storage with no assigned port driver. Sadly, the caper is not yet over, my new response is: "Error: Unrecognized response to calibration command JointCoarse request." Which I take to mean there may be a hardware problem that I need to resolve before proceeding. The gimbal at no point shows any sign of life, and I think it should at least twitch on Initialization. Thanks for the help here. I guess they updated their syntax rules. I wish they'd also cite the Mini2 along with Mini because I'm operating on that assumption from comments but I'd feel a lot more confident investing all this effort with an official endorsement in the documentation.

.