TashTalk USB

[Bolacore]

Anything interesting of note different between those two caps? I think I remember @NJRoadfan mentioning a few of the quirks of the IW II in that we should use DDP Long headers for NBP as otherwise it responds to all of them (or did I have that backwards?). I'm sure he would have a good idea based on the capture too.

 

[iigs123]

Here is a small capture of the LCII looking up Imagewriters. This is from a little rust program that I added that just opens tashtalk & capture, closing when you hit enter. Two extra bytes at the end when compared to nbd-lookup's packet.

wireshark decodes exactly the same, and only shows the frame length being different. The two extra bytes are 91 5E.

 

[Bolacore]

Interesting, nothing looks that different beyond it using NBP broadcast requests which we dont do yet. Any chance you could take a capture of the ones TailTalk makes for comparison? I assume that was the one that had the extra 0x91 0x5E right?

 

[iigs123]

Here is nbp-lookup's capture for entity =:ImageWriter@*

 

[Bolacore]

ahh yeah that seems like just the CRC then - I think this is likely us not using the broadcast request option. Out of curiosity if you have just these two in the network (So your modern machine direct to the ImageWriter) does it see it then? In the LC case I dont see any responses back either - was the IW on at the time?

 

[iigs123]

in the LC_IWII capture I did have the printer and LC II on, and the ImageWriter showed up in chooser. I didn't notice the lack of responses. Interesting - but they must have been on the wire for them to show up in the chooser.

I do sometimes see Localtalk framing error/aborted warnings. Perhaps the response was dropped or ignored on the tailtalk side.

 

[Bolacore]

Oh that would be kinda interesting - do you consistently see that framing / aborted warning after every tailtalk generated (Or even the LC II one when the IW would respond) NBP lookup?