Burgerman wrote:The issue with joysticks is not the hardware but the software. PG drives for e.g have decades worth of experience and updates to make them drive well, and be safe, as well as user programable to set them up correctly for each user/motor/powerchair and options.
So the real questions are:
How much power (amps?)
Are they USER programmable? So that different impedance motors from a different type of chair for e.g could be used?
And after all that are they any good?
And what are you trying to do with these? For e.g, do you have the ability to read the code, from the chip you show, if you plan to replace it?
They should use current sensing, temperature sensing, and roll back the power until in a safe zone. They do not sound either powerful enough to use properly or reliable / safe enough. But they are cheap.This is why. No impedance parameter? Then probably they dont have a positive feedback loop in the software or dont measure current at all. So they will be terrible to try and use on any powerchair. They wont drive properly.
snaker wrote:My old chair uses this joystick. The controller is called newVsi (a PG brand). It claims 50A rated but it's weaker than vr2 50A (I guess it's only 35A). I tried to connect it to PC through woodygb's cable and the PG software did recognize it. Its parameters are less than vr2 but include all essential ones.
snaker wrote:I donated that chair to an elder. The chair is a Chinese brand Wisking, the joystick (controller) is newVsi. You can google the world "newVsi".
https://www.google.com/search?q=%22newV ... 6&dpr=1.33
ex-Gooserider wrote:IIRC it is pretty easy and cheap to make the cable that talks to VSI and the programming software is accessible - so I'd think it worth trying to see what happens if you try using the PG software to talk to it....
Burgerman wrote:With EVERY modern sysem. Some also need a dongle to decode.
martin007 wrote:Burgerman wrote:With EVERY modern sysem. Some also need a dongle to decode.
Which don't require the dongle?
I'll try to stay away from the chinese.
R-Net is nicer but needs a quite expensive, and somewhat difficult to get Dongle in order to program it.
ex-Gooserider wrote:IIRC it is pretty easy and cheap to make the cable that talks to VSI and the programming software is accessible
fabrasil wrote:snaker wrote:You can google the world "newVsi".
Yep. You are right. Look that:
http://scooterland.com.au/wp-content/up ... manual.pdf
https://www.monsterscooterparts.com/pg- ... 61-01.html
even https://www.pridemobility.com/pdf/owner ... er_boi.pdf
ex-Gooserider wrote:martin007 wrote:The older and 'obsolete' Pilot + controllers from P&G don't need a dongle and can be programed with a fairly simple and inexpensively made cable (directions elsewhere on the forum, use the search) They are no longer manufactured, but can be purchased used on eBay. They aren't as flexible / capable as R-Net, which replaced them, but are quite usable on a basic chair
Some of the other P&G series controllers will also work with the Pilot+ software and cable, but I'm not sure offhand which ones.
R-Net is nicer but needs a quite expensive, and somewhat difficult to get Dongle in order to program it.
As mentioned previously, the Chinese products are a bit of an unknown. Some CLAIM to be possible P&G knockoffs, but it is unknown if the P&G software / cable would work with them. Given the low cost of making a Pilot cable I'd be inclined to give it a try as a cheap experiment.
ex-Gooserider
Burgerman wrote:And what control script or software do you use, and does it include essential load compensation etc?
slomobile wrote:Burgerman wrote:And what control script or software do you use, and does it include essential load compensation etc?
Software:
https://www.dimensionengineering.com/so ... ribe/html/
https://www.dimensionengineering.com/info/arduino
https://www.dimensionengineering.com/info/dotnet
It may do IR compensation, I don't know, read the software manual and see. You can tune the expo just like in RC. I greatly prefer its layout to Rnet software. I don't require IR compensation because I will use encoders with the Kangaroo add on which I think will afford a superior level of control to IR comp. I still only have the 2x25 and it is actually sufficient for most things. No kangaroo or 2x60 yet, but planned soon as I can afford. Encoders currently are read by the Arduino.
It is plenty drivable without either encoders or IR compensation. It just means when you get stuck on a threshold, you give it a little more stick to get over, then reduce on the other side. Turning in place on the 2x25 works fine, it just takes a lot of stick movement to get started, then need to reduce quickly. Often easier to just let go when pointing the desired direction to stop on a dime. Feels sluggish starting out because it takes a lot of power and it lets you feel it. That is a good thing if you need to manage your consumption to preserve range. A rolling turn is much easier on the batteries if you can manage it, and this gives you the feedback to understand it without an amp meter. And when you let go of the stick, it actually stops instead of carrying on a couple seconds. It does not have all the nanny safety stuff built in. You want protection from yourself, you'll have to implement it yourself, including the braking circuit, but thats just 1 switch mosfet and a couple lines of Arduino code. And you can set the brake timeout to any value you like, or monitor the encoders to only apply parking brake when the wheels are actually stopped. Avoiding being tossed on fast downhills which is a hazard with Rnet. Its accessible and open enough that a person can do just that. It isn't for everyone. But I bet that you specifically BM would like it if you tried it. If you absolutely have to have IR compensation it can be implemented by reading current in software.
In addition to using the DEScribe software, I write my own Arduino routines which I suppose are equivalent to Roboteq scripts. Except they are well understood by a large Arduino DIY community instead of being an obscure language understood by... Lenny? Anyone else?
MFR product claims:
"Peak currents of 120A per channel are achievable for a few seconds." Just like Rnet. 102A and 113A are less than 120A.
"Sabertooth 2X60 uses 0.8 milliohm MOSFETs in its bridge."
"Overcurrent and thermal protection means you'll never have to worry about killing the driver with accidental stalls or by hooking up too big a motor."
slomobile wrote:Burgerman wrote:And what control script or software do you use, and does it include essential load compensation etc?
Software:
https://www.dimensionengineering.com/so ... ribe/html/
https://www.dimensionengineering.com/info/arduino
https://www.dimensionengineering.com/info/dotnet
It may do IR compensation, I don't know, read the software manual and see. You can tune the expo just like in RC. I greatly prefer its layout to Rnet software. I don't require IR compensation because I will use encoders with the Kangaroo add on which I think will afford a superior level of control to IR comp. I still only have the 2x25 and it is actually sufficient for most things. No kangaroo or 2x60 yet, but planned soon as I can afford. Encoders currently are read by the Arduino.
It is plenty drivable without either encoders or IR compensation. It just means when you get stuck on a threshold, you give it a little more stick to get over, then reduce on the other side. Turning in place on the 2x25 works fine, it just takes a lot of stick movement to get started, then need to reduce quickly. Often easier to just let go when pointing the desired direction to stop on a dime. Feels sluggish starting out because it takes a lot of power and it lets you feel it. That is a good thing if you need to manage your consumption to preserve range. A rolling turn is much easier on the batteries if you can manage it, and this gives you the feedback to understand it without an amp meter. And when you let go of the stick, it actually stops instead of carrying on a couple seconds. It does not have all the nanny safety stuff built in. You want protection from yourself, you'll have to implement it yourself, including the braking circuit, but thats just 1 switch mosfet and a couple lines of Arduino code. And you can set the brake timeout to any value you like, or monitor the encoders to only apply parking brake when the wheels are actually stopped. Avoiding being tossed on fast downhills which is a hazard with Rnet. Its accessible and open enough that a person can do just that. It isn't for everyone. But I bet that you specifically BM would like it if you tried it. If you absolutely have to have IR compensation it can be implemented by reading current in software.
In addition to using the DEScribe software, I write my own Arduino routines which I suppose are equivalent to Roboteq scripts. Except they are well understood by a large Arduino DIY community instead of being an obscure language understood by... Lenny? Anyone else?
MFR product claims:
"Peak currents of 120A per channel are achievable for a few seconds." Just like Rnet. 102A and 113A are less than 120A.
"Sabertooth 2X60 uses 0.8 milliohm MOSFETs in its bridge."
"Overcurrent and thermal protection means you'll never have to worry about killing the driver with accidental stalls or by hooking up too big a motor."
Return to Everything Powerchair
Users browsing this forum: No registered users and 38 guests