Users who have downloaded version 1.01, please download this update. The changes are for wireless SIO2PCs (like Bluetooth) and mainly to make the Options Dialog error-proof, so correct options are selected/disabled depending the chosen handshake method. A patched OS rom is also included for users who own a OS switching upgrade like Ultimate 1MB. It is required for wireless SIO2PC usage. The ROM supports high-speed operation with wired SIO2PC devices.

a8w hat geschrieben:Users who have downloaded version 1.01, please download this update. The changes are for wireless SIO2PCs (like Bluetooth) and mainly to make the Options Dialog error-proof, so correct options are selected/disabled depending the chosen handshake method.

mainly Options Dialog?



Rather timing alignment (delays between ACK and COMPLETE), as described in the SIO2BT doc.
You are making progress, keep trying Ray

You need to double the delay, otherwise SIO transmission can look like that (recorded with AspeQt 1.01-update-1):


At the picture above you can also see that Atari and AspeQt need 4 command frame repetitions to get synchronized (at the beginning and in case of loosing sync). What's wrong Ray?

a8w hat geschrieben:A patched OS rom is also included for users who own a OS switching upgrade like Ultimate 1MB. It is required for wireless SIO2PC usage. The ROM supports high-speed operation with wired SIO2PC devices.

The timeout is rather too small (80ms for NTSC), I messured BT delays up to 150ms (worst case).

And you could just give credit to me and merge my code...

If users report any timing problems i will readjust them, but my tests proved more than satisfactory. I don't rely on oscilloscopes but rather on extensive field tests and practical results. Oh I give you all the credit for SIO2BT, not much credit for making the software closed and limiting it to only the hardware you sell though. I would normally don't care as it is your business decision, but when you go around criticizing me for not making the source for AspeQt easily available (it is available to supporters), that coming from a guy who makes his software proprietary, and which only works with a given set of MAC ids, it sounds a bit like a double-standard.

In any case I thought you and Joey were going to improve RespeQt but what i found is that you guys didn't even release the latest corrections since July 2015. So maybe it's time to stop bothering me and start working on RespeQt


Respeqt-fully yours,
Ray

a8w hat geschrieben:If users report any timing problems i will readjust them, but my tests proved more than satisfactory. I don't rely on oscilloscopes but rather on extensive field tests and practical results.

Good that you are not developing safety relevant applications.

a8w hat geschrieben:Oh I give you all the credit for SIO2BT, not much credit for making the software closed and limiting it to only the hardware you sell though. I would normally don't care as it is your business decision, but when you go around criticizing me for not making the source for AspeQt easily available (it is available to supporters), that coming from a guy who makes his software proprietary, and which only works with a given set of MAC ids, it sounds a bit like a double-standard.

If you recall, I published the source code (and not only binaries) for two (at that time) open source projects: AspeQt and sio2bsd, both modified for Bluetooth communication. In the manual I also described how to configure a generic Bluetooth module, so everyone could set it up (I know some people did).
I consider the Android App (which I developed from scratch) as a bonus feature. It is bundled to the hardware, but this is not a secret (you can read about it in the manual). I'm not making money on that, it just covers the material costs and some project related expenses. I introduced bundling mainly to protect myself from unfair competitors and to be able to provide support to the users. There are many different BT transceivers on the market and many possibilities to do things wrongly, so I wouldn't be able to troubleshoot.
At the end, the Atari Fans have a choice if they want to support the SIO2BT project (and benefit from the Android app) and if not - they still can use sio2bsd or AspeQt/RespeQt software with generic BT transceivers.

a8w hat geschrieben:In any case I thought you and Joey were going to improve RespeQt but what i found is that you guys didn't even release the latest corrections since July 2015. So maybe it's time to stop bothering me and start working on RespeQt

I'm not the maintainer of the RespeQt project. I jumped in, because one of the SIO2BT users asked me, if the Bluetooth functionality could be merged to the RespeQt project. I asked Joey and commited my changes.
And once again, I wouldn't say no if you would ask me for including my source code in AspeQt.
Now I'm simply afraid that the SIO2BT project's reputation can suffer when people start using AspeQt 1.01.

Never mind, I warned the community and since I can not stop you from developing the code based on the "extensive field tests and practical results" I only hope that you take a look again at the RespeQt source code and release some improvements to the AspeQt.

Couple of factual corrections:

- I don't use an oscilloscope because i don't have one, so i have to rely to my field tests, and no i am not developing a safety device so i don't have to worry about it.

- You say people can use a generic BT device, but the device you sell is already generic , i purchased the exact same one for a couple of dollars. You simply took a generic device captive by including MAC ID check in your SIO2BT software. It is very easy to de-compile and remove the MAC id table from your code, liberate it and call it SIO2BTLibre, obviously I will not do that.

Does the following look familiar?:

DeviceListActivity

Code: Alles auswählen

        if (bondedDevices.size() > 0) {
            findViewById(R.id.title_paired_devices).setVisibility(0);
            for (BluetoothDevice bluetoothDevice : bondedDevices) {
                String address = bluetoothDevice.getAddress();
                String name = bluetoothDevice.getName();
                if (C0000a.m10a(address)) {
                    this.f2c.add(name);
                    this.f4e.add(address);
                }
            }
            return;
        }
        this.f2c.add(getResources().getText(R.string.none_paired).toString());


If it was to recover your costs, maybe you already did, and can consider making the software open. I can actually tell you how many you sold already, it must be tiring to release a new version every time you add a new MAC ID into your program code

How about creating your own design of the hardware and making it work at higher baud rates, BT has a wider bandwidth than only 19,200bps. I abandoned my BT project because I don't have enough technical background to do that, maybe you can, and get even more credit. I never made AspeQt to work only with my SIO2PC device even though I designed the hardware myself, yet you guys got upset because I promoted my device with links in AspeQt and decided to remove them from the code. The only tangible change to AspeQt, under the name RespeQt, is removing those references, and once that is done the progress stopped.

- You say you only contributed to RespeQt because of the BT code, but i just read somewhere that you are also working on adding PCLINK to RespeQt, so obviously BT code wasn't the only reason. By the way my folder image code is all mine and it is not copied from anybody else. I like to learn while I code so I would never just cut and paste code from someone else's development.

In any case you just worry about your reputation with your own software, and I worry with mine.
I don't want to discuss this any more.

a8w hat geschrieben:I don't use an oscilloscope because i don't have one

It was a logic analyzer and you would benefit from having one

a8w hat geschrieben:It is very easy to de-compile and remove the MAC id table from your code, liberate it and call it SIO2BTLibre, obviously I will not do that.

I "hacked" my Android app myself before I released it, so I'm not really impressed. One day I will open the source code. And you are really a jealous person... Is this all you can in regard to Android?

a8w hat geschrieben:You say you only contributed to RespeQt because of the BT code, but i just read somewhere that you are also working on adding PCLINK to RespeQt, so obviously BT code wasn't the only reason.

Yes, it was. After I've done it I realized that people are interested in PCLINK so I'm going to implement it (if possible with code re-use from sio2bsd giving credits to KMK).

a8w hat geschrieben:In any case you just worry about your reputation with your own software, and I worry with mine.

???

a8w hat geschrieben:I don't want to discuss this any more.

Me neither. Although it was fun to read your answers