NISMOPC
-
Content Count
800 -
Joined
-
Last visited
Posts posted by NISMOPC
-
-
21 minutes ago, DrVenkman said:I'm confused here - how does ANY of it work if the 130XE is powered down?
Both the WiModem232 and the SDrive-Max are powered by their own 5V USB power supplies. No power is used by the SIO for these.
The nice thing about that is you can select what disk image(s) you want to load on the 8-bit before turning on the computer.
-
1
-
-
18 hours ago, _The Doctor__ said:Need more information on the entire set up.
=> SDrive-Max
130XE => 1050 (D1) => 1050 (D2) => P:R:Connection <
=> WiModem232 (serial port)
As stated, my other SDrive-Max (socketed chip with pin#2 bent up and connected to RX, diode on TX) works flawlessly with this same set-up. This new build is using the chip on board with sub-board and is the one I am having the issues with. Only works when the 130XE is powered up OR when the 130XE is powered down and there is no power getting to the WiModem232. Makes no sense to me.
-
5 minutes ago, DrVenkman said:Sounds like the WiModem232 is stealing the bus, probably in the same way that the SDrive-MAX does without the isolation buffer chip circuit installed. I don't have one of those devices (I use a 15+ year old Lantronix ethernet/RS232 gateway device) so I'm not familiar with their electronics or how they're setup.
Seems accurate, but the sub board chip is supposed to take care of that as stated. So, not sure what is going on.
-
Latest saga....
My current SD-Max is based on the socketed chip version, RX connected to bent up pin #2 on chip. Works flawlessly.
Just because, I decided to build another SD-Max using an UNO R3 with the chip on board and the v3 sub-board.
Set-up using a P:R:Connection with WiModem232 and two 1050 drives all daisy chained. Everything seemed to be working fine and identical results as my other SD-Max until I decided to turn off the computer and tried to load different files on the SD-Max. The touchscreen is non-responsive.
After messing around for a bit, I found out that if I remove the USB power from the WiModem232, the SD-Max works as expected. So the problem is if I have my computer on, I have no issues with the current set-up. If I have the computer off, I have to unplug power to the WiModem232 to be able to use the SD-Max.
My other SD-Max does not have this issue. Thoughts?
Pics of new build...
***brown wire is not being used and is heat shrinked to protect from board
-
18 hours ago, toddtmw said:I had to flip it, so you know...
I kept the board oriented with the cable and the usb/power ports on the same side, and that means everything else is backward, but then I did angled shots to help orient everything.
Thanks!
-Todd
I noticed you do not have a DIODE inline on the TX and are not using the #2 pin up on the socketed chip for the RX signal. Are you using this as your only connection via the SIO or is it daisy chained with other hardware? It will have conflicts with other hardware if you are attempting to use it within SIO daisy chain.
-
1
-
-
-
-
19 minutes ago, pixelpedant said:Well, the FG99 works in the Navarone (at least for me it does). It's just that almost nothing else does in combination with it.
Aha! I did not think to try it alone, but then defeats the purpose of the Navarone, right?
-
Ha! Actually bought a Navarone NOS in box not too long ago just because I wanted to have it in my collection. Never had one or possibly ever saw one back when I first got my TI in the 80's, so when one popped up for a good price I bought it.
...and no the FG99 does not work in the Navarone. First thing I tried...
-
About 2+ years back shopgoodwill was a great place to get retro stuff cheap. I would be on there all the time. Things were going for great, reasonable and acceptable prices and I actually added quite a bit to my collection. I have since stepped completely away from that site. Prices are inflated (only assumption is inside job to jack prices up) and sometimes, if you do not check, shipping and handling has become ridiculous as well. Go elsewhere for your goods. They are no longer beneficial to collectors...
-
SOLVED: Guess you can teach an old dog "old" tricks. I did not pay attention to the sectors on the disk I was attempting to image. Finally took a look and added up all the files. 707 sectors. SOB! I was trying to duplicate a physical SD image to a DD formatted disk on the SDrive-Max.
Anyhow, I created a <new> image and formatted it single D and all is well. Duplicated the 1050 physical floppy without any issues.
My S-Drive is operating as it should be and I finally figured out what was wrong. Me...
...back to the basics.
Guys, I appreciate all the information you provided and to Rybags...
On 6/22/2019 at 9:55 PM, Rybags said:Check the disk types of virtual and real floppies - Error 139 can occur if you try to access sectors outside the normal 720 that 810 type disks are limited to. Also note Dos 2.5 can't deal with double density disks either (720 sectors @ 256 bytes per sector)
...I should have paid a little more attention to this. I was using 1050, but this should have given me the proper insight into actual issue and I overlooked.
EDIT: This was all while using DOS 2.5 for those interested.
-
1
-
-
3 hours ago, slx said:I dug out a Rana 1000 and got the following results:
...
Overall I can't say I'd find the user interface of sdrive.atr or SDrive Max particularly intuitive.
SOLVED: Guess you can teach an old dog "old" tricks. I did not pay attention to the sectors on the disk I was attempting to image. Finally took a look and added up all the files. 707 sectors. SOB! I was trying to duplicate a physical SD image to a DD formatted disk on the SDrive-Max.
Anyhow, I created a <new> image and formatted it single D and all is well. Duplicated the 1050 physical floppy without any issues.
My S-Drive is operating as it should be and I finally figured out what was wrong. Me...
...back to the basics.
EDIT: This was all while using DOS 2.5 for those interested.
-
4
-
-
54 minutes ago, DrVenkman said:You may have missed the edit to my original reply the other night, but I encountered the same error you did after I had created and formatted a new disk image on my SDMax. However, after rebooting the Atari back to DOS, I was able to successfully copy a physical disk to the new image. I just couldn’t do it until AFTER I had rebooted the Atari.
I did see it (and thank you!), but still had no luck. Same ERROR- 139 no matter what procedure I attempt. Figured I'd have others try same procedure and post their results. Might be an issue, might not. I just haven't seen may posts of individuals duplicating physical floppy images to SDrive-Max atr images, so I don't have much to go on.
-
2 hours ago, Mr Robot said:The documentation I said I'd write is coming along but it looks like you don't need it now!
This is exactly what is needed. Excellent information for current and future users of SDrive-Max builds!!!
-
1
-
-
57 minutes ago, slx said:Finally got mine to work with RX on bent out pin 2 and TX with a diode. Works without extra PSU on an 800XL (no other machines tested yet). I put in a switch to allow re-connection of pin 2 with the board for programming (I know it's a bit big but it was the smallest one around).
Still have another with the OSHPark V3 sub-board that will not work, makes strange SIO sounds. RX LED on the Arduino never lights up, so I suspect an intermittent fault in the SIO cable (which shows continuity between all the required pins on the plug and the connections on the sub-board) or cold solder joint .
Would you be able to test something for me? Having issues with trying to create <new> image, format it then copy a physical floppy from 1050 drive to the new image. Keeps erorring out ERROR- 139.
I started a separate thread with this issue, but figured since you just completed your build (I did the pin to to RX as well, just no switch yet).
-
3 minutes ago, SS said:Try to see if you can write to this blank ATR on your SDrive-MAX. It is DOS 2.5 formatted "extended density". I would also leave the 1050 compatibility switched on the SDrive-MAX just 'cause. It probably shouldn't make a difference but I'd try it anyway so that both drives are acting like 1050s.
Will give it a shot tomorrow. Thanks
-
18 minutes ago, Rybags said:Check the disk types of virtual and real floppies - Error 139 can occur if you try to access sectors outside the normal 720 that 810 type disks are limited to. Also note Dos 2.5 can't deal with double density disks either (720 sectors @ 256 bytes per sector)
Re SIO comms - you don't really need to check every emulated drive on an emulated physical type, if SIO works for drive 1 then it should be fine for the remainder.
But as you said, there's potential for problem if there's multiple devices of the same ID that can respond to commands.
These floppies I have (new old stock) are what I've used forever since the 80's. I've copied images from 1050 to 1050 on them a few times. Didn't think it would be any different using them to copy to a SDrive-Max image.
I tried to use the 1050 option in the [cfg] menu as well to see if any changes, but nothing.
-
6 minutes ago, DrVenkman said:Very weird. I just tried it and it seemed to work without issue.
What I did:
- Boot D1: with a DOS 2.5 image
- Swap that image to the D2: slot, leaving D1: open
- Use the SDM "New" menu command to create a new disk
- Use the DOS 2.5 format command to format (I) the new .ATR in the D1: slot, which makes the >NEW< image appear with the "SDMxxxxxx" filename
- Use the DOS 2.5 duplicate disk command (J) to copy D2: (my previously-booted DOS 2.5 image) to D1: (the newly-created disk image).
It took a few minutes on my 48K 800 that I happened to be using, but it worked fine. Both disks have the same content, and the newly-created image is in fact bootable - I powered off my 800 and rebooted with the new image still in D1:.
I am able to do this within the Sdrive-Max. It's when I am trying to copy a physical floppy disk to the newly created image. I didn't see you mention anything about physical floppies in your post.
-
OK, so now that I have my replacement SDrive-MAX built and working properly, I am trying to image a floppy disk from one of my 1050's to a new ATR image on the SDrive-MAX. All sio communications are working. I am able to switch from drive to drive, load from all drives, read from all drives, etc. (via SDrive-MAX and both 1050's). So I know there are no SIO communications issues.
I have tried several different options with below steps and continually get ERROR -139
Load DOS 2.5 via 1050 Drive 1
Create new image and format via SDM Drive 2
Swap DOS 2.5 floppy with floppy I want to image
Option (J) Duplicate Disk
Source,Destination D1,D2 [ENTER]
I've tried duplicating floppy from 1050 Drive 1 to SDM Drive 2, 1050 Drive 2 to SDM Drive 1, etc. etc.
I've also tried loading DOS 2.5 from SDM Drive 1, emptying that drive and duplicating from 1050 to SDM Drive 2.
Every time it reads the source floppy, then beeps and spits out the error message. Nothing else happens.
I have no issues duplicating disks from 1050 Drive 1 to 1050 Drive.
NOTE: I always turn off whatever physical 1050 drive I am using in SDM so there are no conflicts with drive #'s
Error-133 Device or file not open.
This error occurs when truing to access a file or device that has not been OPENed. A common cause of this is a mistake in your file specification, either on OPEN or when trying to access the device.
-
9 hours ago, BigBen said:I made the setup again and tested. Sorry for my confusion, here is the correct description:
Pin (0) RX line goes to the bent Pin2 of the Atmega.BigBen - Just to be clear on this. RX to Pin 2 is the correct connection to make. Leave TX as is WITH the diode inline?
-
2 hours ago, Mr Robot said:You're using a 4148 diode there, people were having problems with that and switched to a Schottky diode for the lower voltage drop (this may have been a 1088XEL only problem). You're saying a diode is required on TXD doing it this way and the 4148 is OK? We know it's not required for the SMD solution.
In this comment you are pretty specific about it being Pin 3, not pin2. The previous comment (with pictures) said Pin 2. A later picture showed Pin 3 which matched what you were saying below. Now we are back to pin 2 again?
Total confusion now 🤪 Glad I did not change mine yet. Will wait for final agreeable pin and wire before doing anything.
-
2 minutes ago, Mr Robot said:You probably should have quoted the bit about the switch as well...
Fixed!
-
1
-
-
26 minutes ago, Mr Robot said:I didn't post that picture BigBen did. It's also wrong, he has since posted a correct picture, it's pin 3 not pin 2.
I need to knock up some instructions for all this, don't I?
Mr Robot - That would be great. I was just reading that portion of the thread when I saw he re-posted regarding PIN 3. I am still not quite comfortable with the direction.
It states: "Arduino Uno Atmega put out of the DIL socket and bent out Pin3, put it in the socket and connect with SIO Pin3."
Am I to understand that I do not solder the SIO pin 3 connection directly to the board but I will solder it to the pin 3 of the socket that I bent out (with inline diode)?
And it does not need reconnected for programming since I will program via USB connection IF I need to?UPDATE: Was posting this same time as above post. Just went and read that link of information Mr Robot. Thank you...
THIS clarifies it!QuoteWhat bigben is saying is that pin 3 on the ATmega chip (TX) should be bent out of the socket and the wire that you previously soldered to pin 1-TX on the UNO board should be soldered to it, so desolder that wire from the UNO board (it goes to SIO pin 3) and solder it to the chip leg.
If you want to update the firmware at some later date you will need to reconnect that pin back to the UNO, so you should probably fit a switch.
ATmega chip Pin-3 - - UNO BOARD DIP Socket Pin-3 \ - SIO Connector Pin-3
You no longer need the diode, it never worked in the first place.
-
4 minutes ago, JR> said:Yes, you can just leave pin 2 out of the socket, or install a switch to re-connect it when re-programming.
See here (picture from Mr. Robot post earlier in thread) :
Well hot diggity dog [email protected]! - How did I miss that!
Guess I'll build another one with a generic chip on board version with the sub board as a backup then.
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
SDrive-MAX ATX support
in Atari 8-Bit Computers
Posted
Still seems odd my other SD-Max works perfectly fine.
It's an official ATARI (NOS) serial cable and works just fine with everything previously. Just not this different version SD-Max.