[2lostkiwis]

in reply to: osPID_FrontEnd #3872

@Brett wrote:

Ian, thanks so much for doing the leg work on this bug. I’ve just committed a change to github. I replaced the “\” with File.separator. at runtime the application should now choose the correct slash depending on the operating system.
of course I can only confirm that this works on Windows, but I’m pretty confident that this is the solution.

Hi Brett, no problems – thanks for your all your work too 🙂
osPID-osPID-Front-End-57b5854 works for me fine now.
Cheers, Ian.

[2lostkiwis]

in reply to: osPID_FrontEnd #3870

@Brett wrote:

I’m really scraping the bottom of the barrel here, but can you confirm that you’re using version 0.5.4 of the controlp5 library?

Hi Brett,

Just downloaded osPID-osPID-Front-End-69c3a6b.zip and had similar problems mentioned in this thread. Had to copy the profiles directory to the applications folder, not ideal but workable for the moment. Application still doesn’t run, so tried to debug under processing (first time I have used it). I can confirm I have v0.5.4 of the controlP5 library installed.

First problem is on line 114 of osPID_FrontEnd.pde:

ReadProfiles(curDir+"\profiles");

The ends up passing the path of /Applicationsprofiles to the function which is invalid on OS X. Changing the \profiles to /profiles got past this.

A similar problem exists on line 44 of SPProfile.pde:

profs = CreateProfile(directory+"\"+files); 

After making these changes the application now runs, and the graphs are updated. Not sure how to fix this to be cross platform though.

Cheers,
Ian.

[2lostkiwis]

in reply to: osPID_FrontEnd #3858

@Ron wrote:

I just received my osPID kit from Rocket Scream, assembled, powered up and uploaded updated firmware per the quick start guide. The only thing I had to go hunting for was the information on loading the serial port driver for Mac OSX. I’m now stuck on step of using the front end.

When I open the Mac OSX version of the osPID_FrontEnd the application starts but the only menu option at the top is the osPID_FrontEnd. Step 4 says ‘Select the osPID comm port and click connect” but there is no menu option for selecting a comm port. ❓

Hi Ron, can you confirm the driver is correctly loaded. With the osPID plugged in, on Lion go to the Apple Menu->About This Mac->More Info->System Report… Then go to Hardware->USB

There should be a USB device called FT232R USB UART as shown in the screen shot below:
[attachment=1:4d1w7ups]Screen Shot 2012-04-30 at 6.57.46 PM.png[/attachment:4d1w7ups]

Also if you go to Terminal, and issue the attached command to find all serial ports:
[attachment=0:4d1w7ups]Screen Shot 2012-04-30 at 7.03.53 PM.png[/attachment:4d1w7ups]

You can see the serial device file name includes the USB serial number, in my case AHVBFODT.

I guess also can you let us know what driver you installed from FTDI? Was it the following file:
http://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriver_v2_2_17.dmg
Linked from this page:
http://www.ftdichip.com/Drivers/VCP.htm

Kind regards,
Ian.

[2lostkiwis]

in reply to: Proportional control calculation #3785

@Brett wrote:

Hi Ian, when the pid is turned on (Manual -> Automatic) the current value of the Output is remembered as the baseline value. moving forward all output corrections are based off this value. so in your trend, you started pid with an output of 50. when the input crosses setpoint the proportional term is indeed 0, as you expected, it’s just being added to this starting value.

this is standard pid behavior, and it exist to allow for a “bumpless transfer” from manual to automatic.

Many thanks Brett, you’re totally correct. It’s been a long time since I was at Uni so I was relying on the distant past in my mind. If I start with an output of 0% before switching to automatic everything is great.

Kind regards,
Ian.

[Author]

Posts