TheMontezuma Posted February 3, 2016 Share Posted February 3, 2016 (edited) I started a new topic: "OS X issues" with focus only on the OS X specific problems/changes, etc. The Logic Analyzer helped me to understand the lower communication speed over Bluetooth. The timing of the Bluetooth stack in the OS X seems to be ugly. Instead of expected ~50ms pauses between data chunks I observed ~250ms pauses (200ms additional delay in OSX BT stack?) Additionally bigger data chunks were not transmitted in one shot. With "bigger" I mean a diskette sector + checksum (129 bytes), There was a 200ms pause in between. The virtual serial port is opened with O_NDELAY parameter, so the "read()" and "write()" calls are non blocking. The "write()" call will not necessarily process all bytes. It returns the number of bytes that could be written. The still awaiting bytes have to be sent in the next "write()" call (in a loop) and this happens for 129 bytes (sent in to chunks: 126 + 3) At the end, the data transfer was successful, but I don't have any idea how to improve that Edited February 3, 2016 by TheMontezuma Quote Link to comment Share on other sites More sharing options...
TheMontezuma Posted February 5, 2016 Author Share Posted February 5, 2016 After looking at the code and thinking it over, I think that this issue simply reveals a poor design of the application Normally GUI applications start threads to execute lengthy or blocking tasks, so the user can still interact with the GUI. AspeQt/RespeQt has a SIOWorker QThread, but if it is blocked, the GUI is blocked as well... That's why the serial port is opened in a non blocking mode and every IO operation exits after a timeout to keep the application responsive 1 Quote Link to comment Share on other sites More sharing options...
Smokeless Joe Posted February 6, 2016 Share Posted February 6, 2016 I just started using RespeQt with DrVenkman's Jan 31, 2016 build. I love it, but if I cmd-Q or RespeQt > Quit RespeQt, it tells me that it quit unexpectedly. Clicking the red button will close it without error. Definitely minor, but annoying. Any ideas what's going on? Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted February 7, 2016 Share Posted February 7, 2016 I just started using RespeQt with DrVenkman's Jan 31, 2016 build. I love it, but if I cmd-Q or RespeQt > Quit RespeQt, it tells me that it quit unexpectedly. Clicking the red button will close it without error. Definitely minor, but annoying. Any ideas what's going on? Glad it's working for you! I get the same error, for what it's worth. I think it's got to be some kind of bug in either Qt itself or in the application close/shut down process. Doesn't seem to harm anything or damage any of the loaded .ATR images so far as I can tell, just a silly annoyance. Quote Link to comment Share on other sites More sharing options...
Dmitry Posted April 20, 2016 Share Posted April 20, 2016 (edited) deleting Edited April 20, 2016 by Dmitry Quote Link to comment Share on other sites More sharing options...
Dmitry Posted April 20, 2016 Share Posted April 20, 2016 (edited) Sorry for the weirdness, was testing some posting from code. Edited April 20, 2016 by Dmitry Quote Link to comment Share on other sites More sharing options...
TheMontezuma Posted August 7, 2016 Author Share Posted August 7, 2016 I got a new Mini Mac and I downloaded RespeQt-r3, but I'm not able to get it running with my SIO2PC/USB cable. The virtual serial port is visible under /dev When I change the handshake to NONE, I see at least the RespeQt log window the "GetStatus" command. However the answer (status) is not reaching the ATARI. I was able to setup Bluetooth connection with my SIO2BT and everything works well. My SIO2PC/USB cables are OK (work perfectly on a WIndows and on a Linux machines), so I suspect the serial port driver or the USB hardware (Mini Mac has only USB 3.0 ports). Any ideas? Quote Link to comment Share on other sites More sharing options...
Joey Z Posted August 7, 2016 Share Posted August 7, 2016 (edited) I got a new Mini Mac and I downloaded RespeQt-r3, but I'm not able to get it running with my SIO2PC/USB cable. The virtual serial port is visible under /dev When I change the handshake to NONE, I see at least the RespeQt log window the "GetStatus" command. However the answer (status) is not reaching the ATARI. I was able to setup Bluetooth connection with my SIO2BT and everything works well. My SIO2PC/USB cables are OK (work perfectly on a WIndows and on a Linux machines), so I suspect the serial port driver or the USB hardware (Mini Mac has only USB 3.0 ports). Any ideas? there are tty devices, and cua devices, maybe try the other? (just a shot in the dark) Edited August 7, 2016 by Joey Z Quote Link to comment Share on other sites More sharing options...
JoSch Posted August 7, 2016 Share Posted August 7, 2016 I bought the SIO2PC-USB dongle from Lotharek and used the OSX driver, he links to on his website. That works fine for me. Quote Link to comment Share on other sites More sharing options...
TheMontezuma Posted August 7, 2016 Author Share Posted August 7, 2016 A driver update from FTDI has helped. Quote Link to comment Share on other sites More sharing options...
tuf Posted August 20, 2016 Share Posted August 20, 2016 A driver update from FTDI has helped. I might have missed this, but does this imply that an SIO2BT works with respeQt? Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted August 20, 2016 Share Posted August 20, 2016 I might have missed this, but does this imply that an SIO2BT works with respeQt? It most certainly does. Configure RespeQt for your BT virtual COM port and select "Handshaking: None". Quote Link to comment Share on other sites More sharing options...
tuf Posted August 20, 2016 Share Posted August 20, 2016 It most certainly does. Configure RespeQt for your BT virtual COM port and select "Handshaking: None". Ok this is exciting. I noticed since updating my U1MB my OS slots have changed - which OS provides the SIO2BT patching? Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted August 20, 2016 Share Posted August 20, 2016 Ok this is exciting. I noticed since updating my U1MB my OS slots have changed - which OS provides the SIO2BT patching? You can use SIO2BT with any OS by turning on HSIO+SIO2BT in the U1MB PBI BIOS. You can do this without using the SIDE HDD and it's compatible with cartridges. Imminent update supports faster SIO2BT speeds too. Of course you can still use a patched version of the High speed OS if you prefer, or if you use SDX, optionally configure its SIO driver for SIO2BT. PBI high speed driver takes precedence over everything else when enabled, though. Quote Link to comment Share on other sites More sharing options...
tuf Posted August 21, 2016 Share Posted August 21, 2016 You can use SIO2BT with any OS by turning on HSIO+SIO2BT in the U1MB PBI BIOS. You can do this without using the SIDE HDD and it's compatible with cartridges. Imminent update supports faster SIO2BT speeds too. Of course you can still use a patched version of the High speed OS if you prefer, or if you use SDX, optionally configure its SIO driver for SIO2BT. PBI high speed driver takes precedence over everything else when enabled, though. Working! I should note that I had to select "SOFTWARE (SIOBT)" under handshake method to get it working in RespeQt. This is with a U1MB and the PBI SIO2BT options enabled, as you suggested. Thanks for the help! Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted August 21, 2016 Share Posted August 21, 2016 Working! I should note that I had to select "SOFTWARE (SIOBT)" under handshake method to get it working in RespeQt. This is with a U1MB and the PBI SIO2BT options enabled, as you suggested. Thanks for the help! Yes: I had a blonde moment there. Software handshake. Quote Link to comment Share on other sites More sharing options...
Joey Z Posted April 11, 2017 Share Posted April 11, 2017 After looking at the code and thinking it over, I think that this issue simply reveals a poor design of the application Normally GUI applications start threads to execute lengthy or blocking tasks, so the user can still interact with the GUI. AspeQt/RespeQt has a SIOWorker QThread, but if it is blocked, the GUI is blocked as well... That's why the serial port is opened in a non blocking mode and every IO operation exits after a timeout to keep the application responsive yes, this should be fixed. Have we talked about this ever? I'd appreciate it if you could add an issue to github, more things that really should be fixed, to add to the ever growing list..... Quote Link to comment Share on other sites More sharing options...
Level42 Posted September 7, 2017 Share Posted September 7, 2017 I stil have the issue that sometimes I can drag and drop files into the drive positions but sometimes I have to click the disk icon (or folder icon) and go through the menu to mount an ATR or folder. Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted September 7, 2017 Share Posted September 7, 2017 I stil have the issue that sometimes I can drag and drop files into the drive positions but sometimes I have to click the disk icon (or folder icon) and go through the menu to mount an ATR or folder. This isn't a strictly-OS X issue though; I have the same problem running on my RPi boxes, though I don't think I've seen it in (very limited) use with my Win10 box. Of course, my Win10 box is VASTLY overpowered compared to my Pi's, so maybe it's just that the (inefficient) core code just executes faster on my (much faster) Winbox? 1 Quote Link to comment Share on other sites More sharing options...
Level42 Posted September 8, 2017 Share Posted September 8, 2017 (edited) Encountered this behavior when I first used it so I'm a bit surprised it still isn't fixed. It's annoying as hell.....o well....it's free software. Edited September 8, 2017 by Level42 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.