Print

[bmwcyclist]

My solenoid was not retracting. I adjusted it as per troubleshooting instructions from Sun re marketing.

Solenoid appears to be working properly, but I am getting an 82 error.

I noticed when the heads are in the center of the drive the horrendous noise goes away. I don't know if that's irrelevant.

Any suggestions?

By the way, I don't have BLUN a disk format that I can use with the floppy EMU.

Here is the video https://youtube.com/shorts/qLkUoe_MRj4?si=rPQIEWjpsAYduMhY

[sigma7]

... the video

In the video it looks like maybe the wire going to the solenoid is rubbing on the flywheel... (?)

By the way, I don't have BLUN a disk format that I can use with the floppy EMU.

Assuming BLUN was supposed to be "BLU in" --

Although I suspect BLU won't be helpful here compared to something like https://github.com/stepleton/NeoWidEx, I think the straight DC42 file should work after unzipping, is that not the case?

[AlexTheCat123]

It doesn't appear that your drive is making it through the self-test that occurs right after the brake releases. The heads seem to move once and then give up. You should be seeing a bit more movement, and the heads should be slowly sweeping the entire surface of the disk as they perform a seek test.


I'd suggest hooking the drive up to either NeoWidEx or your ESProFile (with the switch on the ESProFile PCB flipped to the DIAG position) next. If you choose ESProFile, just connect to the board over serial at 115200 baud to access the diagnostic interface.


Then maybe try to read the status of the Widget controller and let us know exactly what it says. On ESProFile, it's the Get Controller Status command under the Widget-Specific Commands submenu, but I'm not sure what it's called in NeoWidEx. That should give you a good bit of info about the health of the controller, and can help us figure out where to look next.

[bmwcyclist]

In the video it looks like maybe the wire going to the solenoid is rubbing on the flywheel... (?)

Just the angle of the camera.

 I think the straight DC42 file should work after unzipping, is that not the case?

Nope. FloppyEMU does not show it in the menu.

[bmwcyclist]

If you choose ESProFile, just connect to the board over serial at 115200 baud to access the diagnostic interface.


Then maybe try to read the status of the Widget controller and let us know exactly what it says. On ESProFile, it's the Get Controller Status command under the Widget-Specific Commands submenu, but I'm not sure what it's called in NeoWidEx. That should give you a good bit of info about the health of the controller, and can help us figure out where to look next.

Will do! thanks!

[bmwcyclist]

Although I suspect BLU won't be helpful here compared to something like https://github.com/stepleton/NeoWidEx, I think the straight DC42 file should work after unzipping, is that not the case?

The unzipped NeoWidEx is also .dc42. FloppyEMU is not seeing it. Not sure how to get this in a format I can boot from.

[bmwcyclist]

I'd suggest hooking the drive up to either NeoWidEx or your ESProFile (with the switch on the ESProFile PCB flipped to the DIAG position) next. If you choose ESProFile, just connect to the board over serial at 115200 baud to access the diagnostic interface.

I connected to the ESProfile.

Menu comes up and I get the "clunk" of the solenoid but I think my terminal settings might be wrong because when I try to choose a menu item I get garbage (screenshot attached)

[AlexTheCat123]

ESProFile's tester mode uses ANSI escape codes to clear the screen between commands and move the cursor around, so try switching to a program that supports them. The garbage characters you're seeing are the escape codes, so clearly your current program doesn't support them. I don't use Windows much, so I don't have any concrete suggestions off the top of my head, but a quick search suggests that Microsoft Terminal might support them.

[sigma7]

uses ANSI escape codes ... try switching to a program that supports them

I think this effectively means "try changing your terminal software's settings to emulate a smart terminal eg. VT100, instead of TTY."

(Then if your software can't do "smart terminal" try a different emulator.)

[AlexTheCat123]

I think this effectively means "try changing your terminal software's settings to emulate a smart terminal eg. VT100, instead of TTY."

(Then if your software can't do "smart terminal" try a different emulator.)

Yeah, exactly!

[bmwcyclist]

this is what I am getting:

Please select an option: .[2J.[HCommand confirmation failed!
It doesn't look like you have the diagnostic Z8 ROM fitted in your ProFile, which is needed for all commands in this menu.
Do you want to continue anyway (return for yes, 'n' to cancel)? .[2J.[H.[2J.[HESProFile Diagnostic Mode - Version 1.0

[bmwcyclist]

I am not having much luck with BLU either.

FloppyEMU, CiderPress2 and BMOW diskcopy 4.2 converter all say both the .sit and the .zip version of the BLU.DC42 are NOT DiskCopy 4.2 images.

[sigma7]

FloppyEMU, CiderPress2 and BMOW diskcopy 4.2 converter all say both the .sit and the .zip version of the BLU.DC42 are NOT DiskCopy 4.2 images.

Guessing that you need to extract the files from the zip archive, rather than trying to access them through Window's viewer into the zip archive.

ie. on the desktop, right-click the .zip file and select extract to get the dc42 file.

[bmwcyclist]

Guessing that you need to extract the files from the zip archive, rather than trying to access them through Window's viewer into the zip archive.

Nope. I directly extracted the files from the archives using 7-zip and Stuffit for windows.

[sigma7]

I directly extracted the files from the archives

Please attach the extracted dc42 file and perhaps a clue will appear...