Hi Derek and fellow CNC zoners
My first posting, just joined today. No better way to introduce oneself than with an answer to a previously un-replied issue, followed by a query of my own.
First the answer:
As you say, the baud rate for an ANCA 2000 controller is specified as a word (2 bytes) at segment 4000, offset 22Hex, namely address W4000:22 in "ANCA speak". This is achieved by entering the command "I" from the Diagnostics Page, which is Page 7, from the Main menu, that you can drill back to, via th ESC key. At the Diagnostics page, you will see a cluttered full screen of:-
1 = DISPLAY OUTPUT LOGICALS
2 = DISPLAY INPUT LOGICALS
3 = DISPLAY OUTPUT PHYSICALS
4 = DISPLAY INPUT PHYSICALS
5 = DISPLAY AUXILIARYINPUTS etc.
You want to Inspect memory and alter if if necessary at address W4000:22 (Hex). Do this via the I command at this screen, which results in the following line, in the middle of the existing, uncleared screen, requesting the address of the memory location in question, namely:-
memory locn ? _
to which you reply W4000:22 (followed by a carriage return key). i.e:
memory locn ? W4000:22 <cr>
which yields the word at that location, which say for 9600(decimal) would be:-
since (16**3)*2 + (16**2)*5 + (16**1)*8 + (16**0)*0 = 9600.
Entering a carriage return <cr> will maintain the contents and step onto the next word address and display it's contents. Typing in the new hex value followed by the <cr> will replace the word contents and step onto the next address. On my ANCA, the contents are as shown for an arbitrary 6 word range from offset 22H
I'd also like to know what offset 24H determines, also 9600 as shown.
On the other hand, if you are looking at a byte addresses, the W prefix is not used. eg the byte address for segment 4000 offset 8A is simply 4000:8A which happens to be the byte of value 04 that controls 8 data, No Parity, 1 Stop bit. I'm yet to discover the bit definitions for this byte. I'd also like to know why one should use 8,N,1 for DNC communications and 7,E,2 for any other kind of terminal emulation at the PC end, without changing anything at the ANCA end!
Hope this helps, if not yourself then anyone else who is following this thread with a similar issue, since there have been no replies documented to date.
Now my query:
My ANCA has decided to stop being able to receive files via the RS232 link, after having the controller serviced at great expense, for a battery replacement and lost settings. It fails the acid test, namely the "^T Test Communications" from DNC on the ANCA with a "!! TEST FAIL !!" at the ANCA after 2 secs, connected to a PC running DNC5. The test also fails after a "T Test Communications" at the PC end, with an instantaneous "!! TEST FAIL !!" at the PC. My ANCA Com speed is 9600 as above and I have tried permutations of 9600:N,8,1 9600:E,7,1 9600:E,7,2 at the DNC5, PC end, to no avail.
Running a Terminal Coms program at the PC end shows "[!T/<cr>" (excluding the quotes) being instantaneously received at the PC end, in response to a ^T at the ANCA running DNC. This is only if the PC coms is set for E,7,2 or E,7,1 otherwise garbled if N,8,1 (as per my reference above).
Divorcing DNC at the ANCA (namely option 5, form the page 8 , OUT Program option) from the equation and just doing an RS232 INPUT (option 3) and sending data from the PC fails but OUTPUT (option 4) to the PC works, with the PC set for E,7,2 or E,7,1
It's not a wire continuity or crossover issue. An RS232 breakout panel shows correct levels for each Tx line and a loopback connector substituted at the controller board cable, verifies coms at the PC end with an echo. Almost indicating that the Rx input to the comms port on the controller is dead.
Does anyone know of a local loopback test at the ANCA end, to verify that it's Tx can talk to it's own Rx line?
The only fly in the ointment, is the PC end has been replaced with a faster unit, but with an identical disk image to the original, after the old PC died. (RIP). The serial Com port on the newer PC echoes nicely to the null modem, replaced at the ANCA controller end, for test purposes.
Nothing has changed with the previously successful serial line between the ANCA and PC, which I believe is a 3 wire connect 2-3, 3-2, 7-7 between them and a local 4-5, 6-8-20 at each end of the D25's. I've even tested with a laptop right at the ANCA controller and fastidiously connected. I'm clutching at straws at the moment and thinking maybe a rise time issue on the PC Tx line, which may need capacitor smoothing. No too silly but I'm running out of tricks.
Any constructive suggestions most welcome.