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: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.

This isn't true. I check the schematic and code, the USB interface can also be used to reprogram the firmware. There is a jumper, when that is shorted you can then download new code.

Both firmware and software could be a solution lets see which "horse" wins. 😎


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

I updated the firmware to echo back everything it hears. I haven't tested it yet, however if you would like try it you will need to download and install the Propeller Tool. Once that is compete refer to the PSC user manual for programming instructions.

When I get home tonight I will give the code a spin (pun intended).

UPDATE: Firmware changes didn't help...trying some things right now.


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

Alright I give up for now.

There seems to be difference between how the PSCI app communicates and what the manual describes. I sent KC an email to get the strings he is using so I can compare those with the firmware.


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

So I found out from KC how he determines the baud rate.

He sends !SCVER? at 2400baud and waits for the version number response. If that fails he sends !SCVER? at 38.4K and waits for the version number response. If that fails he displays the baud rate error.

I've done some additional testing with both my older serial PSC and the Prop PSC. With a serial terminal I can't for the life of me get the propeller to respond to the !SCVER? command. Using the same setup with the older serial PSC attached I correctly receive the version number response.

Where this gets really weird is if I use the Parallax app I get a version number response but it appears to be just periods (I expect to see 1.0 based on the code). In sort there is something funky either with the firmware (which I digging through) or my setup.


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

That is odd. In both the PSCI app and the Propeller Tool Program when i query the version number I receive a version 1.0 response. Don't know if that helps you at all but let me know if there is anything I can do to assist you.


Reply
Page 3 / 7
Share: