<azonenberg>
I guess the first question is, are you sure usbtmc3 is correct?
<azonenberg>
and are file permissions appropriate for your user?
<d1b2>
<mubes> Yes, if I try a different device id it barfs, and that device appears/dissapears in my usb tree when I plug/unplug the scope
<azonenberg>
ok
<d1b2>
<mubes> yep
<d1b2>
<mubes> $ ls -al /dev/usbtmc3 crw-rw-rw- 1 root root 180, 3 Jan 29 23:14 /dev/usbtmc3
<azonenberg>
That sounds correct then
<azonenberg>
maybe there is a setting on the scope side to use ethernet or tmc mode?
<d1b2>
<mubes> ...these are exactly the things I miss at this time of night though 😕
<azonenberg>
maybe it can't do both?
<d1b2>
<mubes> I checked for one but didn't see it. I'll re-check
<azonenberg>
(also try fully unplugging ethernet in case there's a hard coded precedence)
<d1b2>
<mubes> yes, thats a good idea
<d1b2>
<mubes> No menu for usbtmc, and I can use usbtmc via the web interface
<d1b2>
<mubes> No difference without LAN
<d1b2>
<mubes> The 1104X-E also has ethernet, so I guess thats how everyone else has been connecting too.
<d1b2>
<mubes> Well, it just responded correctly to *RST so I guess the problem is with reading responses, not sending commands.
<d1b2>
<mubes> Hmm. Reads in SCPITMCTransport::ReadRawData all return 0. For tomorrow.
<d1b2>
<mubes> ah....dmesg is your friend;
<d1b2>
<mubes> [491669.439157] usbtmc 1-10.2:1.0: Device sent reply with wrong MsgID: 48 != 2 [491792.487399] usbtmc 1-10.2:1.0: Device sent reply with wrong bTag: 4 != 6 [491792.487531] usbtmc 1-10.2:1.0: Device sent reply with wrong MsgID: 48 != 2 [491826.576066] usbtmc 1-10.2:1.0: Device sent reply with wrong bTag: 6 != 10 [491826.576205] usbtmc 1-10.2:1.0: Device sent reply with wrong MsgID: 48 != 2 [491874.503231] usbtmc 1-10.2:1.0: Device sent reply with
<d1b2>
wrong bTag: 10 != 14 [491874.503361] usbtmc 1-10.2:1.0: Device sent reply with wrong MsgID: 48 != 2
<azonenberg>
Sounds like you have a bug to report. The question is whether it's against siglent firmware or the kernel tmc driver
<d1b2>
<mubes> Yeah, more digging to do I think. Those comparisons are not constant, which makes me wonder if we're not flushing a buffer somewhere or something like that. Time to sleep on it. Night.