Problems with new API/ExtIO
Posted: Tue Jul 12, 2016 10:13 am
Dear SDRPlay team,
thanks for the updated API / ExtIO!
I installed it this morning on my HP7 Stream tablet (Win10 32bit) and first had trouble to get HDSDR started. Several HDSDR error wndows came up (floating point errors, address violation, ...) with the ExtIO named as reason. Since I'm logged in as standard user, I reinstalled it all when logged in as Admin, and then I could start it with HDSDR under the Admin account. Going back as standard user it still did not work, but the error messages I got have been others (I did not log them). I restarted the system and reset HDSDR (got the feeling, that something in the registry might be not ok), and then it worked. So, the installation is not very comfortable ....
However, if I let the LO at constant frequency it seems to work well and stable, but when changing the LO, a few seconds later HDSDR crashes without a dedicated error message. It's the windows systems that reports that HDSDR does not work properly anymore. No idea what the reason is, but it happens always after changing LO. Before updating, with the older API/ExtIO it worked stable for hours on that system.
So, it seems that there's something to fix in the ExtIO and the installation procedure (API and ExtIO).
Another minor bug is with the station display feature: It seems not to show every station. For example, I had a station on 17880 this morning, which the ExtIO station display did not show, but the HDSDR included Frequency Manager did identify it - and both did run on the same EIBI list (offline) I updated this morning. It seems that your station display does not identify every station from within the database.
Maybe you could have a look at the bugs I noted. Thanks!
73 de Eckhard
thanks for the updated API / ExtIO!
I installed it this morning on my HP7 Stream tablet (Win10 32bit) and first had trouble to get HDSDR started. Several HDSDR error wndows came up (floating point errors, address violation, ...) with the ExtIO named as reason. Since I'm logged in as standard user, I reinstalled it all when logged in as Admin, and then I could start it with HDSDR under the Admin account. Going back as standard user it still did not work, but the error messages I got have been others (I did not log them). I restarted the system and reset HDSDR (got the feeling, that something in the registry might be not ok), and then it worked. So, the installation is not very comfortable ....
However, if I let the LO at constant frequency it seems to work well and stable, but when changing the LO, a few seconds later HDSDR crashes without a dedicated error message. It's the windows systems that reports that HDSDR does not work properly anymore. No idea what the reason is, but it happens always after changing LO. Before updating, with the older API/ExtIO it worked stable for hours on that system.
So, it seems that there's something to fix in the ExtIO and the installation procedure (API and ExtIO).
Another minor bug is with the station display feature: It seems not to show every station. For example, I had a station on 17880 this morning, which the ExtIO station display did not show, but the HDSDR included Frequency Manager did identify it - and both did run on the same EIBI list (offline) I updated this morning. It seems that your station display does not identify every station from within the database.
Maybe you could have a look at the bugs I noted. Thanks!
73 de Eckhard