#hp1653b — Public Fediverse posts

The first progress report on the #HP1653B is taking much longer then expected.

Its turned out quite time consuming to produce more modern representations of the data format.

Here is a preview of the blogpost in the first image compared to the original programming manual in the second.

I will probably split the posts in two and only start focusing on the actual Python decoder in a subsequent post.

#analyzer #decoding

The first progress report on the #HP1653B is taking much longer then expected.

Its turned out quite time consuming to produce more modern representations of the data format.

Here is a preview of the blogpost in the first image compared to the original programming manual in the second.

I will probably split the posts in two and only start focusing on the actual Python decoder in a subsequent post.

#analyzer #decoding

The first progress report on the #HP1653B is taking much longer then expected.

Its turned out quite time consuming to produce more modern representations of the data format.

Here is a preview of the blogpost in the first image compared to the original programming manual in the second.

I will probably split the posts in two and only start focusing on the actual Python decoder in a subsequent post.

#analyzer #decoding

No promises yet but I might be able to publish a data decoder for the #hp1652b logic analyzer somewhere tonight together with a (incoherent) blog post.

This decoder is written in Python as opposed to the eventual #Sigrok driver.

#hp1653b

No promises yet but I might be able to publish a data decoder for the #hp1652b logic analyzer somewhere tonight together with a (incoherent) blog post.

This decoder is written in Python as opposed to the eventual #Sigrok driver.

#hp1653b

No promises yet but I might be able to publish a data decoder for the #hp1652b logic analyzer somewhere tonight together with a (incoherent) blog post.

This decoder is written in Python as opposed to the eventual #Sigrok driver.

#hp1653b