Cloud CPM woes

[DJ Sures]

Holy cow, the new cable works. I guess the RS 232 premade cable that I used as the basis for my RS 422 cable, did not have twisted pairs and the shielding did not prevent "noise". Thanks for all the help.

Woohoo!!

[vtgearhead]

I'm having a persistant issue with loss of communication while bulk-copying files between, e.g. the A: and C: drives. The system is a NABU with floppy controller and F18A video adapter. It boots without incident but locks up 100% of the time during 'PIP C:=A:*.*' operation. Here's an example of the console log:

Code: Select all

6/7/2023 9:08:53 AM Settings saved
Current configuration:
 - Config File: /home/hirsch/NABU Internet Adapter/config.xml
 - Created: 6/6/2023 7:31:38 PM
 - Saved: 6/6/2023 7:31:38 PM
 - COM Port: /dev/ttyUSB0
 - Baud: 115,200 bps
 - Pak Folder: 
 - Use Local Folder: False
 - Prompt for Channel: False
 - Start Serial Server on Startup: False
 - Start TCP Server on Startup: False
 - TCP Server Port: 5816
 - RetroNET Store: /home/hirsch/NABU Internet Adapter/Store
 - Temp Folder: /tmp/NABU Internet Adapter
 - RetroNET TCP Server Port: 5815
 - Autostart RetroNET TCP Server: False
 - Last NABU channel: CPM22C80.nabu
 - Comm Logging: False
 - Comm Log File: /home/hirsch/NABU Internet Adapter/CommLog.txt
 - Console Logging: True
 - Console Log File: /home/hirsch/NABU Internet Adapter/Console.txt

6/7/2023 9:09:23 AM Serial: Init mode
6/7/2023 9:09:23 AM RetroNET TCP Server Incoming Buffer Cleared
6/7/2023 9:09:26 AM Serial: Open http://cloud.nabu.ca/cpm/BIOS_CPM22C80.BIN with handle 0
6/7/2023 9:09:28 AM Serial: Close http://cloud.nabu.ca/cpm/BIOS_CPM22C80.BIN with handle 0
6/7/2023 9:09:28 AM Serial: Open CCPM with handle 0
6/7/2023 9:09:28 AM Serial: Close CCPM with handle 0
6/7/2023 9:09:29 AM Serial: Open http://cloud.nabu.ca/cpm/BIOS_CPM22C80.BIN with handle 0
6/7/2023 9:09:30 AM Serial: Open http://cloud.nabu.ca/cpm/A.dsk with handle 1
6/7/2023 9:09:51 AM Serial: Open http://cloud.nabu.ca/cpm/C.dsk with handle 2
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 13. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 1A. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 19. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 02. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 80. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 57. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 01. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 00. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 80. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 00. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got CD. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 47. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 04. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got CD. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 21. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 04. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 01. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 28. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 00. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 09. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 6E. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 26. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 00. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 7D. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got FE. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 01. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got CA. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 98. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 38. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got FE. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 03. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got C2. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 6B. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 3A. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 00. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 21. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 04. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 00. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 39. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got EB. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 21. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 8D. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 00. Restarting
6/7/2023 9:10:32 AM Serial: Did not receive a hello message. Got 00. Restarting

It transfers about 5 files without incident, then always fails at: 'CLOUDGUI.COM' and never recovers.

I have already checked the obvious. I'm using a 6-foot length of two-twisted-pair CAT-3 cable from my wire bin and have double-checked wiring. This issue appears under both Linux (native on my desktop) and Windows 10 (in a VMware virtual machine). The USB/Serial adapter is the recommended D-Tech unit. I see no such issues when running CP/M 3 booted from diskette, so there's no reason to suspect the NABU. What can I to help track down the issue?

[DJ Sures]

You’re not going to like my response - but the cable is causing a communication issue. You can see it in the log info that was pasted.

1) Check the solder joints. Make sure nothing is loose or frayed

2) the rx needs to be on its own twisted pair. The tx needs to be on its own twisted pair.

3) any shielding needs to be on only one side

[vtgearhead]

I appreciate the input, but I do not believe it's a cabling issue. I can trigger the lockup on any and all attempts at using pip to transfer a file that's greater than one extent in size. Something is going off the rails in software. This cabling setup works perfectly with absolutely everything else besides CP/M. At least one other person I know is seeing the same problem. Both of us have considerable experience with software and the hardware bench.

To reiterate: My cable has (2) twisted pairs - one is for TX and the other RX. It has been visually inspected and checked with an ohmmeter. It works for absolutely everything else I've loaded over the wire except for CP/M copies of files that are larger than one extent.

[vtgearhead]

More observations: If I run a different 'internet adapter' and boot CP/M I have no problems at all bulk copying files. Is there any way to point that adapter (older? different author?) at the newer Cloud CP/M?

[vtgearhead]

Today I switched to the 'NNS' NABU adapter/server and discovered that Cloud CP/M works just fine under that environment. I can copy files to my heart's content with no hiccups or lockups. For a control, I went back immediately to your NABU adapter and the lockups reappear. So, not a cabling issue. I'll just stick to NNS.