On Friday, 28 June 2019 08:40:41 UTC+2, ar...@personalrecharge.com wrote:
> On Wednesday, 26 June 2019 15:10:02 UTC+7, Jan Panteltje wrote:
> > On a sunny day (Wed, 26 Jun 2019 00:00:48 -0700 (PDT)) it happened Castorp
> > <nikolaibeev@gmail.com> wrote in
> > <d44bba7e-bf77-4edc-bacd-fb3c58f47dc2@googlegroups.com>:
> >
> > >On Wednesday, 26 June 2019 07:13:43 UTC+2, Jan Panteltje wrote:
> > >> On a sunny day (Tue, 25 Jun 2019 18:45:09 -0700 (PDT)) it happened
> > >> arjen@personalrecharge.com wrote in
> > >> <c9b0fc07-7bc5-448f-8a88-9f8a8ec4770b@googlegroups.com>:
> > >>
> > >> >On Wednesday, 26 June 2019 03:44:34 UTC+7, Gerhard Hoffmann wrote:
> > >> >> Am 25.06.19 um 11:41 schrieb Castorp:
> > >> >> > On Tuesday, 25 June 2019 09:46:03 UTC+2, ar...@personalrecharge.com wrote:
> > >> >>
> > >> >>
> > >> >>> the sub-d connectors are quite poor in quality, it may play a role, but
> > >> >im supprised as to why it doesnt work. just to be sure, can you see if
> > >> >its pin 1 on 1, etc? as i cannot see the whole cable on your image.
> > >> >> >
> > >> >> > I just checked it with a multimeter. It's 1 to 1, 2 to 2... 9 to 9.
> > >> >> >
> > >> >> > I guess you're using the correct port (Serial 2). So I don't know what could
> > >> >be wrong.
> > >> >>
> > >> >> maybe one of the plugs is in the inverted direction?
> > >> >> It would look 1:1 but it isn't. check the pin NUMBERS.
> > >> >> Gerhard
> > >> >
> > >> >I'Ve tried it both ways, straight and reversed, both with similar results,
> > >> > odd thing beeing if i connect the cable straight, pin number to pin number
> > >> >and omit pin 1-6-9, i dont get the fault at start up, but i get the fault
> > >> >as soon as the controller unit attempts to communicate with the RF unit.
> > >> > ive seen a serial test protocol in the service manual, i guess that's the
> > >> >next stop, and some nice AMP sub-D connectors would be good also.
> > >> >
> > >> >Gotta say, you guys have a nice online community here, everyone's very helpful,
> > >> > Thank you all! i really appreciate that!
> > >> >
> > >>
> > >> To see what the situation is, use a voltmeter on pin 2 and 3 of the things,
> > >> the Tx pin should be negative several volts,
> > >> and the Rx pin should be around zero volts.
> > >> Meaure it on both sides, then you know what Rx and Tx is,
> > >> and cross connect those:
> > >> Rx to TX on the other sde, and Tx or Rx on the other side.
> > >> All other ways are guesswork.
> > >>
> > >> Check baudrate and parity settings.
> > >
> > >I don't think you have any control over the settings and baud rate.
> > >
> > >About the pin numbering - I checked that too. They match.
> >
> > The same goes for the hardware handshake lines,
> > it is not often used these days I think, but it is posssible older equipment uses DTR (data terminal ready, output) on pin 4
> > and DSR (data set ready, input) on pin 6,
> > same for
> > RTS (request to send, output) on pin 7,
> > and CTS (clear to send, input) on pin 8.
> >
> > And there is also
> > DCD (data carrier detect, input) on pin 1.
> >
> > So you cannot connect the cable 1 to 1.
> >
> > RTS (out) should go to CTS (in),
> > and CTS (in) to RTS (out).
> >
> > And DTR (out) shoudl go to DSR (in),
> > and DSR (in) to DTR(out)
> >
> > Or this (with 2 and 3 swapped):
> > https://en.wikipedia.org/wiki/Null_modem#/media/File:D9_Null_Modem_Wiring.png
> > https://en.wikipedia.org/wiki/Null_modem
> >
> > So you can loop back too, ig no handshake is needed by connecting CTS to RTS on the same connector, and DTR to DSR, etc.
> >
> > Hopefully this does not create more confusion ;-)
> >
> > It is simple actually.
>
> Allright then, did some trouble shooting and found that the power supply of the RF unit had a shorted tantalum capacitor, and no negative voltages present, so i replaced the capacitors, and now it communicates, and the voltages on the power supply seem to be within range. However, now i get a calibration error on the device, so that's the next puzzle to solve.
Good job!
Do you have Source connected to IN on the RF unit with a short BNC-BNC cable?