support program connection problem

jverroen

New Member
Joined
Aug 20, 2007
Messages
7
Location
Lelystad, The Netherlands
I have a problem with the most recent firmware upgrade.

First the software DO detect the D100  ( on com 1 )
When asking for the firmware version from the D100( or back-up the present firmware ) the application starts to search for a com-port again. This time the software does NOT find the D100 and cycles/search thru all the com-ports, this ends in a blue screen on a non-valid com port.

The software was put on a different brand laptop with the same result
Changing com 1 to a USB connected com adapter shows the same result

To be updated Dynon D100 ( resent version)
Uploaded software  3.01
When running the software it shows VS 2.5.7 (!?)
Laptop HP with 9 pins rs232 and windows XP professional SP2

D100 connected via RS232 port on computer
Wiring is a dedicated update-cable, wiring double checked and is ok ( TX and RX crossed)

Jörgen
 

dynonsupport

Dynon Technical Support
Staff member
Joined
Mar 23, 2005
Messages
13,226
Where are you seeing a version number of 2.5.7?

In any case, you should not be crossing the TX and RX lines on the cable that goes between the EFIS and the PC. This would definitely cause connectivity problems between the PC and the EFIS.
 

jverroen

New Member
Joined
Aug 20, 2007
Messages
7
Location
Lelystad, The Netherlands
I made an seperate PC 'update cable' so I can update the D100 and D120 outside the aircraft. So only 12V, gnd and the TX-RX are connected. I expect this must work too?

The software do find the D100 ( on comm1) but search again after a version check and this time don't find a attached D100/D120

Thanks for the help..

Jörgen
 

dynonsupport

Dynon Technical Support
Staff member
Joined
Mar 23, 2005
Messages
13,226
This usually implies one of two things:

Either the instrument that the support program is something other than the EFIS (the initial comm port detection routines are looking for serial data streams, but is not looking too hard for Dynon data in particular, so other devices can fool it).

But also, if the PC TX / EFIS RX wire were not connected, the PC would hear the EFIS, but would not be able to get commands back to the EFIS. These commands are needed for both a full firmware detect, and any upload/download operations.
 

jverroen

New Member
Joined
Aug 20, 2007
Messages
7
Location
Lelystad, The Netherlands
I'M VERY DISAPPOINTED: found out I DO need reading spectacles..
I had made a TX connection to pin 21 instead of 22. Because the innitial ( one way ) connection looked fine I didn't expected the wrong connection.

Thanks for the reply, units updated and like it!

regards, Jörgen
 
Top