search

famiclone6502 / DIY_Datalink_Adapter

Timex Datalink Notebook Adapter emulator for Raspberry Pi Pico or Arduino, works with the original software to sync your watch.
BSD 3-Clause "New" or "Revised" License
23 stars 1 forks source link

Notebook Adapter not found error! #4

Closed Igor22113377 closed 1 year ago

Igor22113377 commented 1 year ago

I have a problem. I dont know gow to connect it to the vm. Please help! #1

famiclone6502 commented 1 year ago

I have a problem. I dont know know to connect it to the vm. Please help! #1

Can you provide more information about which step of the process you're stuck at? What have you tried so far, and also what VM software and version are you using?

I've tried to provide known supported scenarios in the readme. If there's any deviation you're aware of, like a version number, it will help to know.

Igor22113377 commented 1 year ago

@famiclone6502 Of course! So im using Oracle Virtual Box version 7.1 or 7.2 i forgot. Datalink software is 2.1d and i have some issues with connecting this adapter. So i was stuck with pipes to connect it, i marked it as COM2 (adapter) and it was showing up in windows xp as COM3, because i marked it like that. So i think i connected it successfully, i opened datalink software and i tried to upload files. No light is showing up (i am using raspberry pi pico) and also the error is showing. It just dont connect and the software is not thinking that this is an notebooka adapter.

Igor22113377 commented 1 year ago

I have a problem. I dont know know to connect it to the vm. Please help! #1

Can you provide more information about which step of the process you're stuck at? What have you tried so far, and also what VM software and version are you using?

I've tried to provide known supported scenarios in the readme. If there's any deviation you're aware of, like a version number, it will help to know.

Of course! So im using Oracle Virtual Box version 7.1 or 7.2 i forgot. Datalink software is 2.1d and i have some issues with connecting this adapter. So i was stuck with pipes to connect it, i marked it as COM2 (adapter) and it was showing up in windows xp as COM3, because i marked it like that. So i think i connected it successfully, i opened datalink software and i tried to upload files. No light is showing up (i am using raspberry pi pico) and also the error is showing. It just dont connect and the software is not thinking that this is an notebooka adapter.

famiclone6502 commented 1 year ago

Is XP the host or VM OS? I don't think it will work in either situation. The software works with Windows 2000 at latest I think. But also, it's normal to get an error initially after attempting a sync, as it seems to be a necessary step. Once you receive the error, only then should you connect the adapter as a COM port to the VM and retry.

Igor22113377 commented 1 year ago

Is XP the host or VM OS? I don't think it will work in either situation. The software works with Windows 2000 at latest I think. But also, it's normal to get an error initially after attempting a sync, as it seems to be a necessary step. Once you receive the error, only then should you connect the adapter as a COM port to the VM and retry.

I will try after i finish school with windows 98 SE

Igor22113377 commented 1 year ago

Is XP the host or VM OS? I don't think it will work in either situation. The software works with Windows 2000 at latest I think. But also, it's normal to get an error initially after attempting a sync, as it seems to be a necessary step. Once you receive the error, only then should you connect the adapter as a COM port to the VM and retry.

Well it does not work

famiclone6502 commented 1 year ago

Can you try it with VMWare Workstation 16 and a 98 VM?

Igor22113377 commented 1 year ago

Can you try it with VMWare Workstation 16 and a 98 VM?

Well its not cheap

famiclone6502 commented 1 year ago

I use the free version to sync my watch.

Igor22113377 commented 1 year ago

I use the free version to sync my watch.

I will try after. Thanks

Igor22113377 commented 1 year ago

Is XP the host or VM OS? I don't think it will work in either situation. The software works with Windows 2000 at latest I think. But also, it's normal to get an error initially after attempting a sync, as it seems to be a necessary step. Once you receive the error, only then should you connect the adapter as a COM port to the VM and retry.

I cant connect it like that. I have to turn off the virtual machine to connect the adapter. In Virtual Bax there is the setting "serial ports" and i am using it as host device. Is that right or no? Because i cannot connect that i dont know how to commect it differently. I can only connect the pico like the normal usb (like pendrives or so) and the software is working with windows XP too, because i am using Windows XP Pro, 32-Bit Version. So how i can connect it? As an notebook adapter and after i see an error i have to connect it as a usb device? I will try after your reply with Workstation 16. Thanks for help man

Igor22113377 commented 1 year ago

Is XP the host or VM OS? I don't think it will work in either situation. The software works with Windows 2000 at latest I think. But also, it's normal to get an error initially after attempting a sync, as it seems to be a necessary step. Once you receive the error, only then should you connect the adapter as a COM port to the VM and retry.

And one more thing - I use the EXACT same watch as you. First Data Link 150 From 1994 I think. My uncle got it as a present from his boss.

Igor22113377 commented 1 year ago

I use the free version to sync my watch.

So i installed windows 98 on workstation, and nothing happends. I am connecting after the error, and nothing.

Igor22113377 commented 1 year ago

I use the free version to sync my watch.

@famiclone6502

famiclone6502 commented 1 year ago

Unfortunately my stuff is boxed up at the moment, so I can't create a great step-by-step. But I'll try my best to provide hints. Please keep trying different scenarios until one works.

I'm using the VMware Workstation 16 Player. This doesn't mean it won't work in another one like Virtual Box, I just know this worked best for me.

You may need to double check in the Datalink software under File, Advanced that you have the Timex Datalink 150 selected, then after clicking Next... make sure Serial is selected, and that Timex Notebook Adapter is selected. You can use the Test function here similarly to get the test pattern for the watch.

Your watch also needs to be on the correct mode, and it will revert back after timing out, so using the test pattern will help make sure things will sync properly. You may have to shield the light around the watch to ensure only the light from the Pico is being seen, change the distance between them as sometimes further away works better than closer. A consistent test pattern beep means it will likely sync without fail.

Another thing you have to consider is the Pico shows up as a USB device to your host operating system (the one running VMware). You can't connect this as a USB device to Windows 98, because Windows 98 doesn't have USB drivers for the Pico. But, with virtual machine software like VMware, it will be able to present it as a serial device, which Windows 98 should be able to understand and talk to. You also need to make sure that "VMWare tools" is installed inside the Windows 98 VM, which provides drivers for many things like the video and maybe serial too.

Good luck and let me know if this helps!

Igor22113377 commented 1 year ago

Unfortunately my stuff is boxed up at the moment, so I can't create a great step-by-step. But I'll try my best to provide hints. Please keep trying different scenarios until one works.

I'm using the VMware Workstation 16 Player. This doesn't mean it won't work in another one like Virtual Box, I just know this worked best for me.

  • After booting Windows 98 SE...

  • I can't remember if I connect the Pico now or not (but try it here)

  • Run the Datalink Software and try to sync, you'll get an error that the notebook adapter is not found

  • It could be that you're supposed to connect the Pico to the host PC now (so try it here next time)

  • In VMWare, go to Manage, Virtual Machine settings, there should be a serial port here (if not, add it, you may have to let Windows install drivers and reboot the VM)...

  • Check "connected" and use physical serial port that corresponds to the Pico. If you're not sure, check this before and after connecting the Pico. The new one that shows up is the one you want to connect...

  • Click OK.

  • Now click Retry in the Timex Datalink. Hopefully it won't error and try to sync.

You may need to double check in the Datalink software under File, Advanced that you have the Timex Datalink 150 selected, then after clicking Next... make sure Serial is selected, and that Timex Notebook Adapter is selected. You can use the Test function here similarly to get the test pattern for the watch.

Your watch also needs to be on the correct mode, and it will revert back after timing out, so using the test pattern will help make sure things will sync properly. You may have to shield the light around the watch to ensure only the light from the Pico is being seen, change the distance between them as sometimes further away works better than closer. A consistent test pattern beep means it will likely sync without fail.

Another thing you have to consider is the Pico shows up as a USB device to your host operating system (the one running VMware). You can't connect this as a USB device to Windows 98, because Windows 98 doesn't have USB drivers for the Pico. But, with virtual machine software like VMware, it will be able to present it as a serial device, which Windows 98 should be able to understand and talk to. You also need to make sure that "VMWare tools" is installed inside the Windows 98 VM, which provides drivers for many things like the video and maybe serial too.

Good luck and let me know if this helps!

Man you are amazing! I will try tommorrow. Thank you for help!

famiclone6502 commented 1 year ago

Also, sometimes the Pico will show up as a USB drive like when you initially programmed it. I don't know how to prevent this, but it's part of why the step for running the Timex sync helps. So, if it shows up as a USB drive with files in it, it's not acting as a Timex adapter, so you're going to have to disconnect or reset it. This may take some trial and error of when you can/can't attach it as a serial device to the VM.

If you're able to connect it as a serial device to the VM and it doesn't reset and stays connected, you should be in the clear to sync.

Good luck!

Igor22113377 commented 1 year ago

Also, sometimes the Pico will show up as a USB drive like when you initially programmed it. I don't know how to prevent this, but it's part of why the step for running the Timex sync helps. So, if it shows up as a USB drive with files in it, it's not acting as a Timex adapter, so you're going to have to disconnect or reset it. This may take some trial and error of when you can/can't attach it as a serial device to the VM.

If you're able to connect it as a serial device to the VM and it doesn't reset and stays connected, you should be in the clear to sync.

Good luck!

It shows up as "usb serial device com3" is that right? @

famiclone6502 commented 1 year ago

If it's COM3 on the host, you connect it to the VM as a serial port. Use physical COM3 port when configuring the Serial device and check "Connect" then click OK. Note that connecting it on startup might cause issues, so you may want to uncheck that option.

Inside Windows 98 itself, it may be assigned something else like COM2. VMware is translating it from your host machine to the VM.

Igor22113377 commented 1 year ago

If it's COM3 on the host, you connect it to the VM as a serial port. Use physical COM3 port when configuring the Serial device and check "Connect" then click OK. Note that connecting it on startup might cause issues, so you may want to uncheck that option.

Inside Windows 98 itself, it may be assigned something else like COM2. VMware is translating it from your host machine to the VM.

It doesnt work. I am doing exacly it exacly as you told me and it doesnt work. I dont know why, but i really want to sync this watch.

famiclone6502 commented 1 year ago

Can you walk me through, step-by-step what you're doing? What happens when you do each step?

Igor22113377 commented 1 year ago

Can you walk me through, step-by-step what you're doing? What happens when you do each step?

Ok, so here's what i am doing.

  1. Power up the VM
  2. I connect the raspberry pico to host
  3. I am powering up the Timex Data Link software (I installed some more WristApps)
  4. I am seeing the error
  5. I am connecting pico here maybe
  6. And i am seeing the error once again.
famiclone6502 commented 1 year ago

I'm not seeing where you connected the COM port to the VM. Can you elaborate on when/how you're doing that?

Igor22113377 commented 1 year ago

I'm not seeing where you connected the COM port to the VM. Can you elaborate on when/how you're doing that?

In last message, i described COM port as Raspberry pico so:

  1. I started the VM
  2. I connected pico to the host.
  3. I connected the COM port to the VM (or after i saw the error)
  4. I am launching the Data Link software
  5. Once i see the error, i am unplugging COM port and i plug it once again
  6. And... Nothing. I see the error once again.

Thanks for help!

Igor22113377 commented 1 year ago

I'm not seeing where you connected the COM port to the VM. Can you elaborate on when/how you're doing that?

So, can you tell me, how to reset raspberry pico? Just copy the 2 files on the pico, and then format it?

famiclone6502 commented 1 year ago

When you hold down the reset button on the pico and connect it to the PC, it should show up like a USB drive (like a folder). Drag and drop DIY_Datalink_Pico.uf2 into the folder and it will immediately unmount itself and start acting like a Datalink Adapter. Run the Datalink software and try to sync, after the error try to connect it as a COM port in VMware.

Note: If you have a Pico W, it will need an external LED, but if it's an original Pico, it should use the internal LED.

Igor22113377 commented 1 year ago

When you hold down the reset button on the pico and connect it to the PC, it should show up like a USB drive (like a folder). Drag and drop DIY_Datalink_Pico.uf2 into the folder and it will immediately unmount itself and start acting like a Datalink Adapter. Run the Datalink software and try to sync, after the error try to connect it as a COM port in VMware.

Note: If you have a Pico W, it will need an external LED, but if it's an original Pico, it should use the internal LED.

Yeah, ok. I will try to reset it, and maybe it will work.

Igor22113377 commented 1 year ago

When you hold down the reset button on the pico and connect it to the PC, it should show up like a USB drive (like a folder). Drag and drop DIY_Datalink_Pico.uf2 into the folder and it will immediately unmount itself and start acting like a Datalink Adapter. Run the Datalink software and try to sync, after the error try to connect it as a COM port in VMware.

Note: If you have a Pico W, it will need an external LED, but if it's an original Pico, it should use the internal LED.

I am doing it exacly as you told me, and it doesn't work

Igor22113377 commented 1 year ago

When you hold down the reset button on the pico and connect it to the PC, it should show up like a USB drive (like a folder). Drag and drop DIY_Datalink_Pico.uf2 into the folder and it will immediately unmount itself and start acting like a Datalink Adapter. Run the Datalink software and try to sync, after the error try to connect it as a COM port in VMware.

Note: If you have a Pico W, it will need an external LED, but if it's an original Pico, it should use the internal LED.

Please, help me. It doesnt work. What im doing wrong here? Im doing it exacly as you told me.

1st, i open up the machine on windows 10 pro, 2nd i am connecting pico to the VM as a COM Device, and after i run the orginal timec datalink software, and i see the error once again. And once i see the error, i unplug and reconnect pico to the vm, and it doesnt work no matter what i am doing.

famiclone6502 commented 1 year ago

I'm afraid I'm not able to provide more help at this time. When I am able to provide new instructions I will let you know.

Igor22113377 commented 1 year ago

I'm afraid I'm not able to provide more help at this time. When I am able to provide new instructions I will let you know.

Hello,

Do you have time to provide me help at this time? I uninstalled the VM Workstation so i have to install it once again. If not, thats ok, because i have an old CRT TV that is working. If you can help me, tell me that i can record the video of the marks and plug in the pendrive to the TV, And then play it and sync it to the watch. It will work or dont? Greetings

MuddledBox commented 1 year ago

@Igor22113377 I have recreated your scenario and I believe I know how to make it work, because I did with VMWare Workstation 16 Player, Windows 98SED, a Raspberry Pi Pico with External LED (white, 47ohm resistor across GND and pin 18).

  1. Determine which COM port in Windows is the Pico. Mine was COM7
  2. Add a serial port via Player>Manage>Virtual Machine Settings
  3. Click "Add" in the bottom left
  4. Use physical serial port, and select your COM device. Mine was COM7
  5. Ensure "Connected" is unchecked
  6. Ensure "Connect at power on" is unchecked
  7. Start the VM
  8. Open the Timex software
  9. Intentionally fail the first device check
  10. Go to Player>Manage>Virtual Machine Settings
  11. Open the serial port you just made
  12. Click "Connected"
  13. Retry via the Timex software dialog
  14. Timex will recognize your device
  15. Test it, and you will see the LED blinking
  16. Place the watch 1.5 inches away from the LED. I shielded the watch from external light by using a toilet paper tube
  17. Test it via the Timex software till you get a beep from the watch!

Reference Image

Igor22113377 commented 1 year ago

@Igor22113377 I have recreated your scenario and I believe I know how to make it work, because I did with VMWare Workstation 16 Player, Windows 98SED, a Raspberry Pi Pico with External LED (white, 47ohm resistor across GND and pin 18).

  1. Determine which COM port in Windows is the Pico. Mine was COM7

  2. Add a serial port via Player>Manage>Virtual Machine Settings

  3. Click "Add" in the bottom left

  4. Use physical serial port, and select your COM device. Mine was COM7

  5. Ensure "Connected" is unchecked

  6. Ensure "Connect at power on" is unchecked

  7. Start the VM

  8. Open the Timex software

  9. Intentionally fail the first device check

  10. Go to Player>Manage>Virtual Machine Settings

  11. Open the serial port you just made

  12. Click "Connected"

  13. Retry via the Timex software dialog

  14. Timex will recognize your device

  15. Test it, and you will see the LED blinking

  16. Place the watch 1.5 inches away from the LED. I shielded the watch from external light by using a toilet paper tube

  17. Test it via the Timex software till you get a beep from the watch!

Reference Image

Thank you very much, this question is quite offtopic, but i have this watch and the indiglo is not working. The watch shut down and i got it to the watch service, the guy popped out the battery and inserted it, and it works but without the indiglo. It will work, when i insert the new battery? Thanks

MuddledBox commented 1 year ago

@Igor22113377 interesting enough my indiglo was not working either till I programmed the watch. Now it works great. I believe indiglo not working is a common issue!

Igor22113377 commented 1 year ago

@Igor22113377 interesting enough my indiglo was not working either till I programmed the watch. Now it works great. I believe indiglo not working is a common issue!

Seriously? It shuted down and after it was not working and you programmed the watch and it magicly started working? Interesting, and whats your name and E-mail!

MuddledBox commented 1 year ago

@Igor22113377 let's keep the messaging on here. I want to make sure others can search for this information and it helps them later. In my researching the Datalink watches, TONS have their indiglo broken. I have no idea why this is, and mine was broken until I programmed it. I can only suspect that the watch gets in a weird left field state until it gets programmed for the first time.

Igor22113377 commented 1 year ago

@Igor22113377 interesting enough my indiglo was not working either till I programmed the watch. Now it works great. I believe indiglo not working is a common issue!

I dont have serial ports as you can see. Why? I am using Workstation Pro 17 premium version

image

MuddledBox commented 1 year ago

@Igor22113377 you will have to add those serial ports with the "Add" button in the bottom left. The machine has to be shut down for this.

  1. Shut down the machine
  2. Right click on the Windows 98 virtual box
  3. Click "Add" (in the bottom left hand corner)
  4. Reference my image for how it should look

help image

MuddledBox commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

Igor22113377 commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

MuddledBox commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive.

If the LED is blinking, you just need to align it now!

Igor22113377 commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive.

If the LED is blinking, you just need to align it now!

Thank you, without you it will be imposible. I did it after i wrote the last message, it detected it, but after the software got big brain moment and got the knowlege that it is not the orginal datalink adapter. I had to just reboot windows 98 and it works. Thanks a lot!

MuddledBox commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive. If the LED is blinking, you just need to align it now!

Thank you, without you it will be imposible. I did it after i wrote the last message, it detected it, but after the software got big brain moment and got the knowlege that it is not the orginal datalink adapter. I had to just reboot windows 98 and it works. Thanks a lot!

No problem @Igor22113377! Glad you got it working. @famiclone6502 issue is now closed. Feel free to take any of the materials I provided above and add them to your readme.md if desired.

famiclone6502 commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive. If the LED is blinking, you just need to align it now!

Thank you, without you it will be imposible. I did it after i wrote the last message, it detected it, but after the software got big brain moment and got the knowlege that it is not the orginal datalink adapter. I had to just reboot windows 98 and it works. Thanks a lot!

No problem @Igor22113377! Glad you got it working. @famiclone6502 issue is now closed. Feel free to take any of the materials I provided above and add them to your readme.md if desired.

Thank you so much @MuddledBox for your assistance! I have updated the readme.md with your instructions and credited you.

I'm not sure I want to close this yet, since I don't fully understand why VMware Workstation needs this workaround.

I'm sorry I couldn't explain it better, @Igor22113377 I didn't forget about you, but I've been unfortunately too busy lately and haven't had a chance to set this up again.

There is another project that is more active that could be helpful in the future: https://hackaday.com/2023/07/18/modern-software-brings-back-the-timex-datalink/

Their software doesn't have a GUI, but I would love to explore making a modern application that 1:1 replicates the features of the original software on a modern OS by leveraging that library.

I'm also wanting to resume programming custom apps for the watch. I really want to make something that can chime every 30 minutes during work hours. Right now, it's chiming every hour during that period.

Igor22113377 commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive.

If the LED is blinking, you just need to align it now!

Thank you, without you it will be imposible. I did it after i wrote the last message, it detected it, but after the software got big brain moment and got the knowlege that it is not the orginal datalink adapter. I had to just reboot windows 98 and it works. Thanks a lot!

No problem @Igor22113377! Glad you got it working. @famiclone6502 issue is now closed. Feel free to take any of the materials I provided above and add them to your readme.md if desired.

Thank you so much @MuddledBox for your assistance! I have updated the readme.md with your instructions and credited you.

I'm not sure I want to close this yet, since I don't fully understand why VMware Workstation needs this workaround.

I'm sorry I couldn't explain it better, @Igor22113377

I didn't forget about you, but I've been unfortunately too busy lately and haven't had a chance to set this up again.

There is another project that is more active that could be helpful in the future:

https://hackaday.com/2023/07/18/modern-software-brings-back-the-timex-datalink/

Their software doesn't have a GUI, but I would love to explore making a modern application that 1:1 replicates the features of the original software on a modern OS by leveraging that library.

I'm also wanting to resume programming custom apps for the watch. I really want to make something that can chime every 30 minutes during work hours. Right now, it's chiming every hour during that period.

Thank you very much, you, and @MuddledBox Are a good human beings. Also, can you make a calculator for the watch, and do like a program to install more WristApps than one to the watch? It will be great, when wristapps like that will exist. Some ideas: More games, such as Pong game for Timex you own (150) and a program that can download more than one wristapp at the same time, because i dont like that i cant have a CopyMe Game and a stopwach, and a timer at the same time, thats not good. If you will do a wristapps, i will be grateful because it is a good watch and still some people use it. You can make a snake game too, but i am afraid that thats impossible, because of the screen. And a melody composer would be great, because some of the orginal melody's are weird. One more time, Thank you, @MuddledBox and @famiclone6502 Y'all are great people! If i will get another issue, i will contact via this issue if it will be open. @famiclone6502 Consider this ideas to wristapps! Greetings.

MuddledBox commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive. If the LED is blinking, you just need to align it now!

Thank you, without you it will be imposible. I did it after i wrote the last message, it detected it, but after the software got big brain moment and got the knowlege that it is not the orginal datalink adapter. I had to just reboot windows 98 and it works. Thanks a lot!

No problem @Igor22113377! Glad you got it working. @famiclone6502 issue is now closed. Feel free to take any of the materials I provided above and add them to your readme.md if desired.

Thank you so much @MuddledBox for your assistance! I have updated the readme.md with your instructions and credited you.

I'm not sure I want to close this yet, since I don't fully understand why VMware Workstation needs this workaround.

I'm sorry I couldn't explain it better, @Igor22113377 I didn't forget about you, but I've been unfortunately too busy lately and haven't had a chance to set this up again.

There is another project that is more active that could be helpful in the future: https://hackaday.com/2023/07/18/modern-software-brings-back-the-timex-datalink/

If the Timex data link "serial device" is plugged in at startup of Windows 98 SE or 2000, it will briefly disconnect, throwing a non-critical error. This occurs in VirtualBox and VMWare Workstation. It has to be manually reconnected. In the case of VirtualBox, there is no way to do that, which is bad. In VMWare Workstation, it can be reconnected - or initially connected with that "Connected" checkbox.

If I try to replace the data link device (in reality my Pico) with a null modem emulator like com0com, there is a different result. In fact, it won't disconnect on boot up. There has to be SOMETHING causing this to disconnect, and I believe it to be the USB to serial device disconnects trying to get recognized when booting occurs, as Windows 98 SE or 2000 is looking for devices, the serial device gets confused, and crashes.

Worth nothing the Pico / Timex serial device lights up briefly before crashing, leading me to believe Windows is doing something to recognized and communicate the device, as it crashes at the same time on each boot. All I really know is the workaround is to connect the device later as I described above, so we skip this OS boot-up "looking for device" business that causes the serial device crash.

Igor22113377 commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive.

If the LED is blinking, you just need to align it now!

Thank you, without you it will be imposible. I did it after i wrote the last message, it detected it, but after the software got big brain moment and got the knowlege that it is not the orginal datalink adapter. I had to just reboot windows 98 and it works. Thanks a lot!

No problem @Igor22113377! Glad you got it working. @famiclone6502 issue is now closed. Feel free to take any of the materials I provided above and add them to your readme.md if desired.

Thank you so much @MuddledBox for your assistance! I have updated the readme.md with your instructions and credited you.

I'm not sure I want to close this yet, since I don't fully understand why VMware Workstation needs this workaround.

I'm sorry I couldn't explain it better, @Igor22113377 I didn't forget about you, but I've been unfortunately too busy lately and haven't had a chance to set this up again.

There is another project that is more active that could be helpful in the future: https://hackaday.com/2023/07/18/modern-software-brings-back-the-timex-datalink/

If the Timex data link "serial device" is plugged in at startup of Windows 98 SE or 2000, it will briefly disconnect, throwing a non-critical error. This occurs in VirtualBox and VMWare Workstation. It has to be manually reconnected. In the case of VirtualBox, there is no way to do that, which is bad. In VMWare Workstation, it can be reconnected - or initially connected with that "Connected" checkbox.

If I try to replace the data link device (in reality my Pico) with a null modem emulator like com0com, there is a different result. In fact, it won't disconnect on boot up. There has to be SOMETHING causing this to disconnect, and I believe it to be the USB to serial device disconnects trying to get recognized when booting occurs, as Windows 98 SE or 2000 is looking for devices, the serial device gets confused, and crashes.

Worth nothing the Pico / Timex serial device lights up briefly before crashing, leading me to believe Windows is doing something to recognized and communicate the device, as it crashes at the same time on each boot. All I really know is the workaround is to connect the device later as I described above, so we skip this OS boot-up "looking for device" business that causes the serial device crash.

This is not disturbing me at all, but it would be always better to get this fixed up. Unfortunatly, i cannot do this because im not a programmer.

Offtopic, but @MuddledBox Whats your name? @famiclone6502 Whats your name, because we never got the pleasure to get our names! My name is Igor.

famiclone6502 commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive. If the LED is blinking, you just need to align it now!

Thank you, without you it will be imposible. I did it after i wrote the last message, it detected it, but after the software got big brain moment and got the knowlege that it is not the orginal datalink adapter. I had to just reboot windows 98 and it works. Thanks a lot!

No problem @Igor22113377! Glad you got it working. @famiclone6502 issue is now closed. Feel free to take any of the materials I provided above and add them to your readme.md if desired.

Thank you so much @MuddledBox for your assistance! I have updated the readme.md with your instructions and credited you. I'm not sure I want to close this yet, since I don't fully understand why VMware Workstation needs this workaround. I'm sorry I couldn't explain it better, @Igor22113377 I didn't forget about you, but I've been unfortunately too busy lately and haven't had a chance to set this up again. There is another project that is more active that could be helpful in the future: https://hackaday.com/2023/07/18/modern-software-brings-back-the-timex-datalink/

If the Timex data link "serial device" is plugged in at startup of Windows 98 SE or 2000, it will briefly disconnect, throwing a non-critical error. This occurs in VirtualBox and VMWare Workstation. It has to be manually reconnected. In the case of VirtualBox, there is no way to do that, which is bad. In VMWare Workstation, it can be reconnected - or initially connected with that "Connected" checkbox.

If I try to replace the data link device (in reality my Pico) with a null modem emulator like com0com, there is a different result. In fact, it won't disconnect on boot up. There has to be SOMETHING causing this to disconnect, and I believe it to be the USB to serial device disconnects trying to get recognized when booting occurs, as Windows 98 SE or 2000 is looking for devices, the serial device gets confused, and crashes.

Worth nothing the Pico / Timex serial device lights up briefly before crashing, leading me to believe Windows is doing something to recognized and communicate the device, as it crashes at the same time on each boot. All I really know is the workaround is to connect the device later as I described above, so we skip this OS boot-up "looking for device" business that causes the serial device crash.

So the problem possibly lies with the Pico itself? Is my code crashing or is the Pico library crashing? It does seem to reset to bootloader mode on me when it reboots, instead of just rebooting to normal mode. Can I prevent bootloader mode somehow? If it crashed and just re-ran my code, it'd probably be fine. Maybe a modified bootloader could help work around this issue.

If it's not my code contributing to the crash when Timex software initializes the serial port, maybe this needs to be reported to the Pico team. Or maybe I need to somehow recognize and accept that input from the serial port in my code. I had serial monitoring software and didn't notice initialization issues in the Arduino version, but it uses a different library.

Ideally I would love to have a Win9x USB serial driver for the Pico so that we don't have to pass through serial communication via virtualization. This would allow older laptops to directly use it instead of sourcing all the parts for the Arduino serial version. I know this was a dumb idea with a predicable outcome, but I made some attempts at forcing what I thought might be similar 9x drivers to install with the Pico's hardware ID, but they would all BSOD. I thought they might be meant for the same serial USB chip.

@Igor22113377 As for making wrist apps, I am not very skilled. I am modifying existing apps that are open source, or making minor hex changes to the behavior of existing apps. The custom chime behavior is my primary use case, as no modern watch seems to have this ability. Those you mentioned would be beyond my skill set. I would encourage you to learn how to code these. If you do make apps, please share them on GitHub with us.

Igor22113377 commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive.

If the LED is blinking, you just need to align it now!

Thank you, without you it will be imposible. I did it after i wrote the last message, it detected it, but after the software got big brain moment and got the knowlege that it is not the orginal datalink adapter. I had to just reboot windows 98 and it works. Thanks a lot!

No problem @Igor22113377! Glad you got it working. @famiclone6502 issue is now closed. Feel free to take any of the materials I provided above and add them to your readme.md if desired.

Thank you so much @MuddledBox for your assistance! I have updated the readme.md with your instructions and credited you.

I'm not sure I want to close this yet, since I don't fully understand why VMware Workstation needs this workaround.

I'm sorry I couldn't explain it better, @Igor22113377 I didn't forget about you, but I've been unfortunately too busy lately and haven't had a chance to set this up again.

There is another project that is more active that could be helpful in the future: https://hackaday.com/2023/07/18/modern-software-brings-back-the-timex-datalink/

If the Timex data link "serial device" is plugged in at startup of Windows 98 SE or 2000, it will briefly disconnect, throwing a non-critical error. This occurs in VirtualBox and VMWare Workstation. It has to be manually reconnected. In the case of VirtualBox, there is no way to do that, which is bad. In VMWare Workstation, it can be reconnected - or initially connected with that "Connected" checkbox.

If I try to replace the data link device (in reality my Pico) with a null modem emulator like com0com, there is a different result. In fact, it won't disconnect on boot up. There has to be SOMETHING causing this to disconnect, and I believe it to be the USB to serial device disconnects trying to get recognized when booting occurs, as Windows 98 SE or 2000 is looking for devices, the serial device gets confused, and crashes.

Worth nothing the Pico / Timex serial device lights up briefly before crashing, leading me to believe Windows is doing something to recognized and communicate the device, as it crashes at the same time on each boot. All I really know is the workaround is to connect the device later as I described above, so we skip this OS boot-up "looking for device" business that causes the serial device crash.

So the problem possibly lies with the Pico itself? Is my code crashing or is the Pico library crashing? It does seem to reset to bootloader mode on me when it reboots, instead of just rebooting to normal mode. Can I prevent bootloader mode somehow? If it crashed and just re-ran my code, it'd probably be fine. Maybe a modified bootloader could help work around this issue.

If it's not my code contributing to the crash when Timex software initializes the serial port, maybe this needs to be reported to the Pico team. Or maybe I need to somehow recognize and accept that input from the serial port in my code. I had serial monitoring software and didn't notice initialization issues in the Arduino version, but it uses a different library.

Ideally I would love to have a Win9x USB serial driver for the Pico so that we don't have to pass through serial communication via virtualization. This would allow older laptops to directly use it instead of sourcing all the parts for the Arduino serial version. I know this was a dumb idea with a predicable outcome, but I made some attempts at forcing what I thought might be similar 9x drivers to install with the Pico's hardware ID, but they would all BSOD. I thought they might be meant for the same serial USB chip.

@Igor22113377 As for making wrist apps, I am not very skilled. I am modifying existing apps that are open source, or making minor hex changes to the behavior of existing apps. The custom chime behavior is my primary use case, as no modern watch seems to have this ability. Those you mentioned would be beyond my skill set. I would encourage you to learn how to code these. If you do make apps, please share them on GitHub with us.

It is clearly the problem with the software. But you can troubleshoot it, check the cables, the port, you can solder it better, check the port in the computer, but it is CLEARLY the problem with the soft. You wrote the message that you'd like to program WristApps, but if its misunderstanding, then its ok. About the program fot the DataLink, I have it, it's old terminal program for linux. If you'd like to see it, i will get the link with youtube video that you can check, the link for the program is in the bio of the video. The linux soft uses library called "SVGALIB".

Igor22113377 commented 1 year ago

I also want to note that at no point during the process do I have to physically unplug the Pico. The way I do this is very the "Connected" check box. It's all virtual!

So, something bizzare happened. The software detected the adapter and i did the calibration but the watch did not beep. After that i did it one more time, but it says it didnt detect it, but the pico blinked.

You are VERY close. Now you have to get the LED correctly positioned. If you are using the inbuilt LED it like about 1/4 inch above the watch. If you are using an external white LED, it is like 1.5 inches above the watch. Make sure LED is right above the lens. It is very sensitive.

If the LED is blinking, you just need to align it now!

Thank you, without you it will be imposible. I did it after i wrote the last message, it detected it, but after the software got big brain moment and got the knowlege that it is not the orginal datalink adapter. I had to just reboot windows 98 and it works. Thanks a lot!

No problem @Igor22113377! Glad you got it working. @famiclone6502 issue is now closed. Feel free to take any of the materials I provided above and add them to your readme.md if desired.

Thank you so much @MuddledBox for your assistance! I have updated the readme.md with your instructions and credited you.

I'm not sure I want to close this yet, since I don't fully understand why VMware Workstation needs this workaround.

I'm sorry I couldn't explain it better, @Igor22113377 I didn't forget about you, but I've been unfortunately too busy lately and haven't had a chance to set this up again.

There is another project that is more active that could be helpful in the future: https://hackaday.com/2023/07/18/modern-software-brings-back-the-timex-datalink/

If the Timex data link "serial device" is plugged in at startup of Windows 98 SE or 2000, it will briefly disconnect, throwing a non-critical error. This occurs in VirtualBox and VMWare Workstation. It has to be manually reconnected. In the case of VirtualBox, there is no way to do that, which is bad. In VMWare Workstation, it can be reconnected - or initially connected with that "Connected" checkbox.

If I try to replace the data link device (in reality my Pico) with a null modem emulator like com0com, there is a different result. In fact, it won't disconnect on boot up. There has to be SOMETHING causing this to disconnect, and I believe it to be the USB to serial device disconnects trying to get recognized when booting occurs, as Windows 98 SE or 2000 is looking for devices, the serial device gets confused, and crashes.

Worth nothing the Pico / Timex serial device lights up briefly before crashing, leading me to believe Windows is doing something to recognized and communicate the device, as it crashes at the same time on each boot. All I really know is the workaround is to connect the device later as I described above, so we skip this OS boot-up "looking for device" business that causes the serial device crash.

So the problem possibly lies with the Pico itself? Is my code crashing or is the Pico library crashing? It does seem to reset to bootloader mode on me when it reboots, instead of just rebooting to normal mode. Can I prevent bootloader mode somehow? If it crashed and just re-ran my code, it'd probably be fine. Maybe a modified bootloader could help work around this issue.

If it's not my code contributing to the crash when Timex software initializes the serial port, maybe this needs to be reported to the Pico team. Or maybe I need to somehow recognize and accept that input from the serial port in my code. I had serial monitoring software and didn't notice initialization issues in the Arduino version, but it uses a different library.

Ideally I would love to have a Win9x USB serial driver for the Pico so that we don't have to pass through serial communication via virtualization. This would allow older laptops to directly use it instead of sourcing all the parts for the Arduino serial version. I know this was a dumb idea with a predicable outcome, but I made some attempts at forcing what I thought might be similar 9x drivers to install with the Pico's hardware ID, but they would all BSOD. I thought they might be meant for the same serial USB chip.

@Igor22113377 As for making wrist apps, I am not very skilled. I am modifying existing apps that are open source, or making minor hex changes to the behavior of existing apps. The custom chime behavior is my primary use case, as no modern watch seems to have this ability. Those you mentioned would be beyond my skill set. I would encourage you to learn how to code these. If you do make apps, please share them on GitHub with us.

So, here's the video. The soft is in the bio.

https://youtube.com/watch?v=0-3fFwqogcI&feature=shareb