JYE Tech Forum

Except of course for the frame type where it's part of the data. If it weren't for that case, you wouldn't need the frame ID at all, as that byte can determine the frame type, in spite of it not having a consistent name, or in some cases a name at all. Looking things over, it begins to make sense. T...

That's the document I've been looking at, and it doesn't look right. The frame ID for all the frames types after the disconnect frame is 0xC0. Those frames aren't even ask the same type. Those look more like copy/paste errors than a wire protocol.

I'm working on adding support for the DSO112A to sigrok, and recently ran into problem with the serial interface documentation. The frame ID's for all the frames after the disconnect frame are 0xC0. I'm pretty sure that's not right. Any chance there's an updated version of the manual somewhere? Poss...

So I found it on github (https://github.com/JYEtech/jyeLab) but it doesn't look like anything has happened to it. No more commits since the first day, and nobody has forked it on github. On the other hand, comparing it to the documented protocol for the DSO112A (good job publishing those!), it might...