PINNED - Info on PROGRAMMING PGDT and others

[Michalych1974]

No I cant. If you have a programmer you can change it back. Or to whatever better values you want. OR a manufacurer will send you the original (and crap!) that it shipped with. You will need the chair serial number.

"Good day. Question about the firmware: what is this firmware for (circled in red)? What will happen if you try to load it?"

[Michalych1974]

[quote="Burgerman"]

"Good day. Question about the firmware: what is this firmware for (circled in red)? What will happen if you try to load it?"

[Burgerman]

Where are you seeing that?

[Michalych1974]

This is located in the firmware folder, the file bm_16_041207.bin is version 16 of the firmware, bm_17_111208.bin is version 17 of the firmware, and the stroller is Meyra Optimus 2 with CAN Bus

[Burgerman]

I have no idea then. I think it may be to do with the meyra company customizations or myra specific modules?
It isnt for r-net parts.

Says in the TXT file:

This document explains the features and the operation of the PC Programmer for the MEYRA-CAN wheelchair control system. The PC Programmer consists of an interface cable and a CDROM containing the required software. Its available only from MEYRA by part number 1051871. PC system requirements are an IBM compatible PC running an operating systems Windows 98 SE / 2000 / XP. The PC needs to have a generic serial RS232 interface or a USB/Serial adapter installed.

Depending on older versions of the PC service software and the software installed on the modules of the MEYRA-CAN system not all functions may be available. The version information of the PC software can be found under the column „ information / about us ". The version numbers of software installed on the MEYRA-CAN modules is stated the column „ type select".
On MEYRA's homepage http://www.meyra.de the recent versions are directly available in the download area. On request a CDROM containing all software components will be send by mail. Please contact your national importer first or contact our service hotline at info@meyra.de.

- Connect the wheelchair to the PC.
- Turn on the wheelchair.
- Start the MEYRA-CAN wheelchair PC programmer.

Now the MEYRA-CAN PC programmer is automatically connecting to the wheelchair and the modules are addressed. This process can last approx. 1 minute.

[faico_26]

Hi,
I have received the cable to program my Quickie Q300R with VR2. Woodygb (rest in peace) very kindly made the cable for me and sent it to me.
I would like to share my experience in this forum and so other users with VR2 can benefit of it.
I haven’t started yet, not even connected it, I’m reading a lot in these posts to learn.
BM explained to me (thanks BM!) that I need virtual com port. I thought I had a physical port in my pc, but it was the vga port.
Ok, so I will activate the com port and assign it to the cable between 1 and 8 as Woodygb informed in previous posts.
I will keep you informed of the process.
Cheers,
Faico

[faico_26]

Hi,
I have received the cable to program my Quickie Q300R with VR2. Woodygb (rest in peace) very kindly made the cable for me and sent it to me.
I would like to share my experience in this forum and so other users with VR2 can benefit of it.
I haven’t started yet, not even connected it, I’m reading a lot in these posts to learn.
BM explained to me (thanks BM!) that I need virtual com port. I thought I had a physical port in my pc, but it was the vga port.
Ok, so I will activate the com port and assign it to the cable between 1 and 8 as Woodygb informed in previous posts.
I will keep you informed of the process.
Cheers,
Faico

For now I have "Coms Inactive" message.

[faico_26]

Hi,
I have received the cable to program my Quickie Q300R with VR2. Woodygb (rest in peace) very kindly made the cable for me and sent it to me.
I would like to share my experience in this forum and so other users with VR2 can benefit of it.
I haven’t started yet, not even connected it, I’m reading a lot in these posts to learn.
BM explained to me (thanks BM!) that I need virtual com port. I thought I had a physical port in my pc, but it was the vga port.
Ok, so I will activate the com port and assign it to the cable between 1 and 8 as Woodygb informed in previous posts.
I will keep you informed of the process.
Cheers,
Faico

For now I have "Coms Inactive" message.

I have tried 3 different software versions but I have always "Coms Inactive".
The software I tried was:
Setup_Mobility_OEM_Std_14_6_0
Setup_Mobility_Man_Std_14_4_3
Mobility_Manufacturing C_16_5_0

I have tried the USB Serial port to different COM ports (between 1 and 8) and the same in the software. I can run the program without any error message about serial com port, but it is always "INACTIVE".
I have the regular com port to COM3 and the USB com port to COM8. Should it be the same number in both??? I tried, I got an error message because the COM3 was already in use by Windows10 but I still forced it to COM8 but it didn't work eventually, the same "Coms Inactive" in the software.
Some help would be really appreciated!
Thanks,
faico

[Burgerman]

Cant read spanish...
Make sure you have correct driver for the cable installed. Then in DEVICE MANAGER tell it to show all HIDDED drivers.
Now delete (not disable) all of the greyed out ones, I mean everything that isnt currently attached! All greyed out drivers top to bottom.

Then reboot. Connect woody cable. Turn on chair. Look in device manager. See what it says... Make sure the driver that is a USB SERIAL driver is set to use an UNUSED com port between 1 and 8.

Then open any of the software. And look to see if you can make it active.

[faico_26]

Cant read spanish...
Make sure you have correct driver for the cable installed. Then in DEVICE MANAGER tell it to show all HIDDED drivers.
Now delete (not disable) all of the greyed out ones, I mean everything that isnt currently attached! All greyed out drivers top to bottom.

Then reboot. Connect woody cable. Turn on chair. Look in device manager. See what it says... Make sure the driver that is a USB SERIAL driver is set to use an UNUSED com port between 1 and 8.

Then open any of the software. And look to see if you can make it active.

I tried with a laptop and a PC with no success. I’ll follow your instructions this evening when I’m back home, thanks!

[Burgerman]

Its always the same. With dynamic, with R-Net (its easier) but still sometimes an issue.

[faico_26]

Its always the same. With dynamic, with R-Net (its easier) but still sometimes an issue.

I tried everything including the last FTDI drivers, but still the same "Comms Inactive" message.

[LROBBINS]

This virtual com port problem is widespread and not just with chair programmers. I have run into it with Arduino Nano clones, a veterinarian friend has run into it with sonography equipment etc. etc. Basic Arduino-type microcontrollers may have CH340 or FTDI USB to tx.rx chips that will often not connect. For the CH340, Windows 11-Intel Ultra keeps re-installing the latest driver, that often will not work and doesn't give you an option to roll back to an older one that does. I found a stand-alone CH340 driver installer that will overwrite with the older one.

For the FTDI, it does not seem to be a driver version problem, but corruption of the installed driver. Happens with Win10-LTSC as well as Win11. The driver installer (inf files etc.) is in the "driver store" and writes the driver to device manager. The cure that seems to work is to use device manager to show hidden devices with no virtual com port devices plugged in. Uninstall every one of the greyed out drivers AND when there is an option to "remove the driver" as well as the device, check the YES box too. The next time you plug in the USB device the OS is forced to re-write the driver from the store and it will most likely connect. (This may be related to an FTDI fix from years ago for blocking "fake" FTDI chips.)

My vet friend, even with the help of the equipment mfr's "expert" was never able to reliably reconnect (I don't know what they tried), and their only "cure" has been to, once it does connect, leave the device on 24/7.

[Burgerman]

Once I got my FTDI serial usb drivers working they have been fine though. That includes programmers, PL8 chargers, and a bunch of hobby stuff. But they can be a fight initially.

[faico_26]

This virtual com port problem is widespread and not just with chair programmers. I have run into it with Arduino Nano clones, a veterinarian friend has run into it with sonography equipment etc. etc. Basic Arduino-type microcontrollers may have CH340 or FTDI USB to tx.rx chips that will often not connect. For the CH340, Windows 11-Intel Ultra keeps re-installing the latest driver, that often will not work and doesn't give you an option to roll back to an older one that does. I found a stand-alone CH340 driver installer that will overwrite with the older one.

For the FTDI, it does not seem to be a driver version problem, but corruption of the installed driver. Happens with Win10-LTSC as well as Win11. The driver installer (inf files etc.) is in the "driver store" and writes the driver to device manager. The cure that seems to work is to use device manager to show hidden devices with no virtual com port devices plugged in. Uninstall every one of the greyed out drivers AND when there is an option to "remove the driver" as well as the device, check the YES box too. The next time you plug in the USB device the OS is forced to re-write the driver from the store and it will most likely connect. (This may be related to an FTDI fix from years ago for blocking "fake" FTDI chips.)

My vet friend, even with the help of the equipment mfr's "expert" was never able to reliably reconnect (I don't know what they tried), and their only "cure" has been to, once it does connect, leave the device on 24/7.

I did that as Burgerman told me, deleting everything in grey but nothing worked. I tried a couple of FTDI drivers too.
I will try the same in the laptop, we’ll see.
Thanks
Faico

[faico_26]

Once I got my FTDI serial usb drivers working they have been fine though. That includes programmers, PL8 chargers, and a bunch of hobby stuff. But they can be a fight initially.

Can you check what driver version is working for you?
Thanks

[Burgerman]

I just did PC screenshot. These are for the PLS chargers but its the same driver that windows not just uses for all these FTDI things. Dietz charge, programmers, servo testers, RC transmitter firmware upgrade and config tools, etc.

Depending on your VR2 age, only ONE of those bits of software will work. So test all 3.

Unplug the USB.
Go to DEVICE DAMAGER
Set SHOW HIDDEN.
Delete the USB/SERIAL FTDI drivers and TICK THE LITTLE BOX. Reboot.

Do it again, and again, until it cant find any more drivers...
THEN install the driver.

Reboot. Test.

[Burgerman]

If youu install several drivers and dont delete them all, windows always uses the newest one. Or the newest wrong one...

So you need to delete all. Reoot and check. Then install the driver.

I noticed another missing driver with an ! mark. That may be related. Fix that too.

[faico_26]

If youu install several drivers and dont delete them all, windows always uses the newest one. Or the newest wrong one...

So you need to delete all. Reoot and check. Then install the driver.

I noticed another missing driver with an ! mark. That may be related. Fix that too.

I have tried in 3 different computers with no success. I tried with a pc with Windows 7 which installed exactly the same version of the driver that Burgerman has but nothing worked.

[Burgerman]

I heard this a lot over the years. I dont know where you go from here. I feel sure I could get it to work.

Did you try all 3 versions?

[faico_26]

I heard this a lot over the years. I dont know where you go from here. I feel sure I could get it to work.

Did you try all 3 versions?

Yes, I tried the 3 versions. Tomorrow I will try with another old computer which has Windows Vista, just in case.

[faico_26]

New cable worked a charm.

Hi,
I currently have exactly the same problem. Could explain how did you fix the problem?
Many thanks,
faico

[takenaback]

Okay complete novice here but I am using Windows 11 64-bit Version 22H2. I haven't updated to the latest version and have no intention as it apparently interacts negatively with my voice recognition program.

After uninstalling the warning in the device manager regarding Windows 11 driver not being compatible et cetera, I installed this version of the driver PL2303_Prolific_DriverInstaller_v1.18.0 and Bob's your uncle. It wouldn't have happened without Woody making a decent cable for me, forever grateful to him. I have two other cables and one would come up with comms inactive whilst the other one would flick between active and inactive but nevertheless rendering it rather useless.

I am using PG Drives Technology PC Programmer 14.6.0 Of course once you have the right communication port selected you need to restart the program for it to work.

This is nothing you haven't been advised before so apart from a possible dodgy cable I am not sure but wish you the best of luck.

Cheers
Steve

[Burgerman]

But a prolific driver is for a prolific chip. Not the users FDTI one.

Yes swapping to a different brand of cable may well work.

Windows 11? Why punish yourself with that???

[jamess]

Hello. I am a beginner having a golden eagle scooter. It has a pg drive s-drive 140a controller that I am trying to program. I have the software downloaded but now I need a cable. Can somone help me with how to build a cable or where to purchase please. Thank you for any help you can provide me.

[alex1304]

Hello. Please tell me where to download the R-net OEM program?

[Burgerman]

PM me.

[alex1304]

PM me.

I wrote you a PM

[TriangleEnthusiast]

I had everything on hand to make a quick and dirty test cable. Dusted off a windows laptop and loaded up the software, checked drivers, ftdi vcp already present, remove hidden unused com ports filling up 1-8, select correct com port in software, connect cable to chair and turn on, coms active and stock file downloaded. I'd call that a success. This was very painless thanks to the collective efforts of all involved here. I think I'll try to make a wireless dongle this afternoon.

[Burgerman]

What component values?
Which FTDI cable?

Post here for others. Very neat board/soldering.