PSC plugin compatib...
 
Notifications
Clear all

PSC plugin compatibility.

34 Posts
3 Users
0 Reactions
21 K Views
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago
Stgtech wrote:That's how I initially tested it. Just for some reason Vixen will not allow me to put in baud rate data.

It should be auto baud on the servo controller side. Leave Vixen at the default slower rate and verify the com port number and try again.

If that doesn't work remove the USB cable from the servo controller and reinsert it. Then launch Vixen and try it again. The servo controller uses the FT232 chipset which can "hang" if another app uses before another wants to use it.


Reply
Posts: 47
Topic starter
(@stgtech)
Trusted Member
Joined: 19 years ago

I tried unplugging, plugging it back in then starting Vixen and same issue applies.

" Parallax PSC: Could not determine the baud rate for the PSC unit. "

With it unplugged "Com 8 port does not exist"

So I have confirmed it is the correct COM port and restarted the board.

Is there any possibility that it has something to do with the propeller infrastructure of this board as opposed to the older model?

Here is a manual / spec sheet for the newer model. Maybe the (excuse my improper terminology) initial codes that talk to the board are different on this model even though the actual commands remain the same?

http://www.parallax.com/Portals/0/Downloads/docs/prod/prop/28830-PropServoControllerUSB-v1.0.pdf

Thank you,
Aaron


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago

So here is what I've done. I own a Propeller, so I grabbed the servo code from the parallax site and programmed my Prop with it.

I tried both the USB and the TTL interfaces with Vixen and got "no joy." There seems to be something a bit different in how the older serial servo controller worked and this new one. I suspect it has to do with the fact that the commands being sent to the controller aren't echoed back down the serial line since Tx and Rx are now separated. I would guess the Vixen plugin is expecting this but I can't be sure.

This is an incompatibility on Parallax's part. I will dig through the code and see if there is anything obvious but in the mean time see if Parallax can help.


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago

I have discussed this matter with KC (the developer of the plug-in). As it stands when he sends a command he then clears the receive buffer, under the assumption that what is in there is just and echo of what was sent. The new Propeller version doesn't echo so essentially he is throwing away a valid response, which explains the problem you are seeing.

I've asked him to update the code to stop this from occurring. I'm not sure when I will see this change or how well it will work (he tends to be very responsive). The alternative is to update the firmware on the PSC to echo back all commands it receives, thus mimicking the older serial PSC (I may try this if I have time tonight).

I will let you know as I have more. Any word from Parallax?


Reply
Posts: 47
Topic starter
(@stgtech)
Trusted Member
Joined: 19 years ago

Called Parallax. They said I could update the firmare to tell it to echo commands however I would need a USB to TTL serial level adapter which I don't have. Their suggestion was to wait for the plugin to be updated. Once again thank you very much for the effort you both have already put in. I'm going to go ahead and try to program my sequence "blind" in hope that the plugin will be ready by Thursday. Please keep me updated, thanks again,

Aaron


Reply
Page 2 / 7
Share: