Launchpad programming

[bacca5419]

Hi all. I am havind problems programming the launchpad. I get as far as where it pauses at break 69. I hit the reume button and it appears to do nothing except bringing up the launchpad model and tells me its running. The control panel shows a led power light but nothing else. I need help as I am a dumd arse with electronics and computers alike. Regards Noel from australia.

[JonWoellhaf]

Hi, Noel.

I'd like to help, but I don't yet understand what you're seeing.

You have Code Composer Studio running and were able to load James' code. Correct?

[bacca5419]

Hi. Yes I can get right up to to loading the launchpad to the first break point , when i hit resume nothing happens. It wont continue to load. So the control panel wont light up. This is where it stops. Pics show where it stops.I feel giving up.Its a new computer. Regards noel

Sent from my iPad

On 1 Sep 2020, at 6:43 pm, JonWoellhaf notifications@github.com wrote:

Hi, Noel.

I'd like to help, but I don't yet understand what you're seeing.

You have Code Composer Studio running and were able to load James' code. Correct?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

I don't understand what you mean by up to the first break point. When I load the code there is no break point. Please tell me step by step what you are doing.

[bacca5419]

Ok. I have loaded the studio code IDE version 9 from TI.com for the launchpad then I have loaded the code for the clough42 firmware. I get right up to loading the program onto the launchpad with the control panel. When loadind onto the launchpad it stops at the breakpoint in the program ,same as it does when james is loading the lanchpad , however when I click the resume button in the program it does not resume as it does when James loads it. I have followed the same proceedures as james. I dont know if you can see the pics I sent. That shows as far as I can get. I dont know if this helps for your understanding. Regards. Noel. Thanks for your assistance , it is apreciated.

Sent from my iPad

On 1 Sep 2020, at 7:59 pm, JonWoellhaf notifications@github.com wrote:

I don't understand what you mean by up to the first break point. When I load the code there is no break point. Please tell me step by step what you are doing.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

OK. I think I now understand. I reviewed James' ELS video Part 10, and at 24:00 he explains the program always stops in Main when in Debug.

This is the break point you're talking about, right? Where does the 69 come from?

[JonWoellhaf]

When you say "brings up the launchpad model and tells me it's running, do you mean that you see in the Debug window the text "Texas Instruments XDS110 USB Debug Probe/C28xx_CPU1 (Running)?"

[JonWoellhaf]

Don't give up, Noel,. I'm certain we -- all of us here -- can help you get it running.

[bacca5419]

That was the number at the break point. I have just tried deleting the firmware from my com and reloaded it , I loaded the updated version of the firmware code. Still get the same problem but the break point is 77. I guess there is more information on the latest update. I am starting to think there is a problem with the microcontroller launchpad. But I have no idea about electronics. Thats why I try to follow James setup. Regards.

Sent from my iPhone

On 1 Sep 2020, at 8:59 pm, JonWoellhaf notifications@github.com wrote:

 OK. I think I now understand. I reviewed James' ELS video Part 10, and at 24:00 he explains the program always stops in Main when in Debug.

This is the break point you're talking about, right? Where does the 69 come from?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

OK. Have you double checked the wiring from the boost board to the LED board?

[JonWoellhaf]

Mine stops a line number 91. Can someone else please check and see at what line number theirs stops?

[bacca5419]

I have checked but I am going to make up a new wire harnes tomorrow. I am sure that isnt it as I have continuity through each wire

Sent from my iPad

On 1 Sep 2020, at 9:12 pm, JonWoellhaf notifications@github.com wrote:

Mine stops a line number 91. Can someone else please check and see at what line number theirs stops?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[bacca5419]

Yes to the texas instrument debug probe running

Sent from my iPad

On 1 Sep 2020, at 9:12 pm, JonWoellhaf notifications@github.com wrote:

Mine stops a line number 91. Can someone else please check and see at what line number theirs stops?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

I think it's unlikely that your TI board is defective.

I'd like you to set a breakpoint in Main. This will let us prove the code is running.

Do you want to do that?

[JonWoellhaf]

I do not see any pictures you sent.

[bacca5419]

I will do anything to get this working. But how do i set a new break point ? I tell you I am as dumb as when it comes to this sort of thing. I am surprised I have gotten this far. Ok it musnt let me send pics.

Sent from my iPad

On 1 Sep 2020, at 9:26 pm, JonWoellhaf notifications@github.com wrote:

I do not see any pictures you sent.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

It's easy to set a breakpoint. When you hit the breakpoint at the top of Main, scroll down until you see the line that reads for(;;) {

Below that, you'll see userInterface.loop();

Mine is on line 143, but yours is probably different -- we can figure out why later, I don't think it's important now.

To set the breakpoint double click the line number. A dot will appear in the column to the left of the line number.

Now, with this breakpoint set, when you run in Debug, the program will stop at the start of Main -- like before -- and when you click Resume it will immediately stop again at the breakpoint you just set.

Clicking Resume again will let the program run through a pile of code until it returns to that point again. It'll look like it didn't do anything.

So the second time it hits the breakpoint, click the Step Into icon on the tool bar or press F5. This will let you step through the code a statement at a time.

If you are able to step through the code -- which I'm quite sure you will be able to do -- we will know a LOT is working!

To remove the breakpoint click Resume, then again double click the line number.

Do you have a volt meter?

[davidgleach]

Hi Jon, What was the outcome of your suggestion. I have exactly the same problem so will try your suggestion.

Thinking the issue was the LED indicating panel I purchased several new panels and fitted one of them with the same result.

In despair I buttoned up the whole system and behold it started to work correctly. It continued to do so for some weeks until I decided to make some improvements to my layout by making a new enclosure for the LED panel. Guess what - the indicating panel no longer functioned, only the LED on the on the PCB was alight. All connections checked out with continuity testing.

Once again I replaced the LED indicating panel with a new one - to no avail.

I've downloaded and replaced all the the Clough 42 files as well as a new version of Code Composer Studio.

Recompiled and reflashed the TI board - and still the program will not run.

[davidgleach]

I have carried out the steps you suggested and the program steps through the loops a few times until it stops again at line 71 WAIT_FOR_SERIAL Does this indicate a bad connection somewhere?

[davidgleach]

I shoudl have noted that it stopped at line 71 WAIT_FOR_SERIAL in the SPIBus.cpp file

[davidgleach]

Problem solved. It is dodgy connections. Too quick to blame the electronics!

[JonWoellhaf]

Hi, David.

I have not heard back from bacca5419.

You wrote, "I have carried out the steps you suggested and the program steps through the loops a few times until it stops again at line 71 WAIT_FOR_SERIAL. Does this indicate a bad connection somewhere?"

No. This is perfectly normal.

Please tell us what the problem with your connections was. That could help someone later.

Great that you solved the problem!

Regards,

Jan (Yan)

[bacca5419]

Hi guys. Still no go on the leadscrew. Checked all connections , no probs there that I can see. I have ordered a couple of new conntrol panels from China. Shipping is extremly slow. One thing I found on the control board that doesnt seem right to me is that with no wiring connected I am getting a continueity between the gnd and the DIO terminals. Dont know if that makes any sense. Will maybe know more when replacement control panel arrives. Will keep you informed as I learn more. Thanks guys.

Sent from my iPhone

On 21 Sep 2020, at 6:15 am, JonWoellhaf notifications@github.com wrote:

 Hi, David.

I have not heard back from bacca5419.

You wrote, "I have carried out the steps you suggested and the program steps through the loops a few times until it stops again at line 71 WAIT_FOR_SERIAL. Does this indicate a bad connection somewhere?"

No. This is perfectly normal.

Please tell us what the problem with your connections was. That could help someone later.

Great that you solved the problem!

Regards,

Jan (Yan)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

Hi, Noel.

How are you measuring continuity between GND and DIO on the control board?

I get 10 meg ohms.

Jan (Yan)

[JonWoellhaf]

What's your location, Noel?

I have several control boards I bought by mistake. I didn't realize I was ordering a set of two each when I ordered two the second time. So I now have five!

[davidgleach]

Hi Jan I noticed when I was stepping through the program that Code Composer was providing a number of messages (coloured red) that i took to be warnings. The messages were "Cannot load from non-primitive location".
The messages were all associated with statements from the SPIBus.cpp file relating to Input/Output data from the Clough42 board to the LED indicating panel. By trial and error I established that the plug positioned on the output pin DIO was not always making a good connection. Replacing the plug fixed the problem.

I appreciate your advice on how to step through the program as that was the key information that set me on the right path.

Cheers David

David Leach

Home: 03 5310 6313

Mob: 0416 119 381

------ Original Message ------ From: "JonWoellhaf" notifications@github.com To: "clough42/electronic-leadscrew" electronic-leadscrew@noreply.github.com Cc: "davidgleach" davidgleach@iinet.net.au; "Comment" comment@noreply.github.com Sent: 21/09/2020 6:15:37 AM Subject: Re: [clough42/electronic-leadscrew] Launchpad programming (#83)

Hi, David.

I have not heard back from bacca5419.

You wrote, "I have carried out the steps you suggested and the program steps through the loops a few times until it stops again at line 71 WAIT_FOR_SERIAL. Does this indicate a bad connection somewhere?"

No. This is perfectly normal.

Please tell us what the problem with your connections was. That could help someone later.

Great that you solved the problem!

Regards,

Jan (Yan)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/clough42/electronic-leadscrew/issues/83#issuecomment-695830994, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP3EHDKRCAA5EHRRERVMAQ3SGZPGTANCNFSM4QQDM4DA.

-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

[bacca5419]

Hi Jan. On the control panel ( led board ) with no wiring connected I start red lead + on vcc I move black lead - down the terminals gnd , stb , clk and dio. I use the buzzer set on my meter. Then I go down the line , red + on gnd , black - down the line of terminals. When I have the + on the gnd and - on the dio I am getting a continuity ( buzzer sounds ). Nothing on any other terminals. I do the same test on the clough42 board. I get no continuity on that board. If that makes any sense. I have 2 replacement boards coming from china to see it that is the problem. ( slow boat from china I think. )I am not in USA I live in Australia. Regards from Aust

Sent from my iPhone

On 21 Sep 2020, at 1:32 pm, davidgleach notifications@github.com wrote:

 Hi Jan I noticed when I was stepping through the program that Code Composer was providing a number of messages (coloured red) that i took to be warnings. The messages were "Cannot load from non-primitive location". The messages were all associated with statements from the SPIBus.cpp file relating to Input/Output data from the Clough42 board to the LED indicating panel. By trial and error I established that the plug positioned on the output pin DIO was not always making a good connection. Replacing the plug fixed the problem.

I appreciate your advice on how to step through the program as that was the key information that set me on the right path.

Cheers David

David Leach

Home: 03 5310 6313

Mob: 0416 119 381

------ Original Message ------ From: "JonWoellhaf" notifications@github.com To: "clough42/electronic-leadscrew" electronic-leadscrew@noreply.github.com Cc: "davidgleach" davidgleach@iinet.net.au; "Comment" comment@noreply.github.com Sent: 21/09/2020 6:15:37 AM Subject: Re: [clough42/electronic-leadscrew] Launchpad programming (#83)

Hi, David.

I have not heard back from bacca5419.

You wrote, "I have carried out the steps you suggested and the program steps through the loops a few times until it stops again at line 71 WAIT_FOR_SERIAL. Does this indicate a bad connection somewhere?"

No. This is perfectly normal.

Please tell us what the problem with your connections was. That could help someone later.

Great that you solved the problem!

Regards,

Jan (Yan)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/clough42/electronic-leadscrew/issues/83#issuecomment-695830994, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP3EHDKRCAA5EHRRERVMAQ3SGZPGTANCNFSM4QQDM4DA.

-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

Noel,

Based on your testing, I agree the control board is likely defective. That would explain everything. Hope the "slow boat from China" arrives soon. I, too, had to wait for one of those. :)

Are you using a digital VOM (volt/ohm meter) to make the measurements? If so, please try the same procedure again with the meter set to ohms. With the wires disconnected, short STB, CLK, and DIO to ground. This discharges the input filter capacitors. Then measure resistance from each of those inputs to ground. You should see a few kohms initially and then greatly increasing resistance, settling around 20 meg ohms or so. That's the effect of the capacitor charging.

If STB and CLK behave differently from DIO, it'll be another indication your board is defective.

Jan (Yan)

[bacca5419]

Hi Jan. Well the new control boards arrived today , plugged one into the microcontroller and low and behold , still nothing. Time to give up I think. Go back to the gears ( at least they work ) I pretty dissapointed. Regards. Noel from Australia.

Sent from my iPhone

On 22 Sep 2020, at 7:20 am, JonWoellhaf notifications@github.com wrote:

 Noel,

Based on your testing, I agree the control board is likely defective. That would explain everything. Hope the "slow boat from China" arrives soon. I, too, had to wait for one of those. :)

Are you using a digital VOM (volt/ohm meter) to make the measurements? If so, please try the same procedure again with the meter set to ohms. With the wires disconnected, short STB, CLK, and DIO to ground. This discharges the input filter capacitors. Then measure resistance from each of those inputs to ground. You should see a few kohms initially and then greatly increasing resistance, settling around 20 meg ohms or so. That's the effect of the capacitor charging.

If STB and CLK behave differently from DIO, it'll be another indication your board is defective.

Jan (Yan)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

Yeah, that’s disappointing, Noel.

Do you have an oscilloscope, or access to one?

If not, if shipping from Australia to Utah, USA is not outrageously expensive, I will be happy to look at your setup and get it working.

Jan

From: bacca5419 Sent: October 7, 2020 22:47 To: clough42/electronic-leadscrew Cc: JonWoellhaf ; Comment Subject: Re: [clough42/electronic-leadscrew] Launchpad programming (#83) Hi Jan. Well the new control boards arrived today , plugged one into the microcontroller and low and behold , still nothing. Time to give up I think. Go back to the gears ( at least they work ) I pretty dissapointed. Regards. Noel from Australia.

Sent from my iPhone

On 22 Sep 2020, at 7:20 am, JonWoellhaf notifications@github.com wrote:

 Noel,

Based on your testing, I agree the control board is likely defective. That would explain everything. Hope the "slow boat from China" arrives soon. I, too, had to wait for one of those. :)

Are you using a digital VOM (volt/ohm meter) to make the measurements? If so, please try the same procedure again with the meter set to ohms. With the wires disconnected, short STB, CLK, and DIO to ground. This discharges the input filter capacitors. Then measure resistance from each of those inputs to ground. You should see a few kohms initially and then greatly increasing resistance, settling around 20 meg ohms or so. That's the effect of the capacitor charging.

If STB and CLK behave differently from DIO, it'll be another indication your board is defective.

Jan (Yan)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[bacca5419]

Hi Jan. No I dont have a oscilloscope or access to one. Even if I did I wouldnt have a clue what to do with it. I am hopeless with electronics and thats on a good day. Thanks for the offer to get it working for me , however I think shipping costs and times would be outrageous. Regards. Noel.

Sent from my iPad

On 8 Oct 2020, at 2:55 pm, JonWoellhaf notifications@github.com wrote:

Yeah, that’s disappointing, Noel.

Do you have an oscilloscope, or access to one?

If not, if shipping from Australia to Utah, USA is not outrageously expensive, I will be happy to look at your setup and get it working.

Jan

From: bacca5419 Sent: October 7, 2020 22:47 To: clough42/electronic-leadscrew Cc: JonWoellhaf ; Comment Subject: Re: [clough42/electronic-leadscrew] Launchpad programming (#83) Hi Jan. Well the new control boards arrived today , plugged one into the microcontroller and low and behold , still nothing. Time to give up I think. Go back to the gears ( at least they work ) I pretty dissapointed. Regards. Noel from Australia.

Sent from my iPhone

On 22 Sep 2020, at 7:20 am, JonWoellhaf notifications@github.com wrote:

 Noel,

Based on your testing, I agree the control board is likely defective. That would explain everything. Hope the "slow boat from China" arrives soon. I, too, had to wait for one of those. :)

Are you using a digital VOM (volt/ohm meter) to make the measurements? If so, please try the same procedure again with the meter set to ohms. With the wires disconnected, short STB, CLK, and DIO to ground. This discharges the input filter capacitors. Then measure resistance from each of those inputs to ground. You should see a few kohms initially and then greatly increasing resistance, settling around 20 meg ohms or so. That's the effect of the capacitor charging.

If STB and CLK behave differently from DIO, it'll be another indication your board is defective.

Jan (Yan)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[davidgleach]

Hi Noel You might have seen my issues with the control board. In spite of being confident that every connection was secure, it turned out after much trial and tribulation there was one board connection that had poor contact. All the boards that I had classed as being defective were in fact okay. Based on that that experience it might be an idea to be very skeptical about the quality of every connection. It was a pain and took many hours of frustrating trials before the eureka moment!! Cheers

[bacca5419]

Thanks for the advise. I will check over everything tomorrow and see what happens. Cheers

Sent from my iPad

On 8 Oct 2020, at 8:34 pm, davidgleach notifications@github.com wrote:

Hi Noel You might have seen my issues with the control board. In spite of being confident that every connection was secure, it turned out after much trial and tribulation there was one board connection that had poor contact. All the boards that I had classed as being defective were in fact okay. Based on that that experience it might be an idea to be very skeptical about the quality of every connection. It was a pain and took many hours of frustrating trials before the eureka moment!! Cheers

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[bacca5419]

Hi all. Still no go here. I have decided to desolder the connectors on the clough42 board ( the connectors that connect the board to the microcontroller ) I really have no answers to this problem. I send my thanks to you all for the advise to get me up and running. Cheers Noel ( bacca5419 )

Sent from my iPad

On 8 Oct 2020, at 8:34 pm, davidgleach notifications@github.com wrote:

Hi Noel You might have seen my issues with the control board. In spite of being confident that every connection was secure, it turned out after much trial and tribulation there was one board connection that had poor contact. All the boards that I had classed as being defective were in fact okay. Based on that that experience it might be an idea to be very skeptical about the quality of every connection. It was a pain and took many hours of frustrating trials before the eureka moment!! Cheers

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[davidgleach]

Hi Noel, What a pain you are having. In my case the poor connection was the result of my bad workmanship when I soldered the 5 pin header to the Clough42 PCB. As I noted, it took me many hours to find the fault. Would you believe it was simply one pin, ie the DIO pin which resulted in an intermittent connection with its mating wire socket. Being 84 yrs old I decided maybe my eyesight was not good enough or the hand not steady enough. Fortunately all is cured and I have to say the system runs like a dream! I do hope you resolve your issue. Good luck. David

[Zymurgy42]

Where in Oz are you Noel?

[bacca5419]

Hi. I am on the north side of Brisbane.

Sent from my iPhone

On 10 Oct 2020, at 9:36 am, Zymurgy42 notifications@github.com wrote:

 Where in Oz are you Noel?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[Zymurgy42]

A tad far from Melbourne.

On Sat, 10 Oct 2020 at 12:41, bacca5419 notifications@github.com wrote:

Hi. I am on the north side of Brisbane.

Sent from my iPhone

On 10 Oct 2020, at 9:36 am, Zymurgy42 notifications@github.com wrote:

 Where in Oz are you Noel?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/clough42/electronic-leadscrew/issues/83#issuecomment-706465089, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADD2HK3TJWO7Y7IBLL6AJELSJ63UDANCNFSM4QQDM4DA .

--

Gordon Newell

[JonWoellhaf]

Yes, but not as far as from Utah, USA!

From: Zymurgy42 Sent: October 9, 2020 20:27 To: clough42/electronic-leadscrew Cc: JonWoellhaf ; Comment Subject: Re: [clough42/electronic-leadscrew] Launchpad programming (#83) A tad far from Melbourne.

On Sat, 10 Oct 2020 at 12:41, bacca5419 notifications@github.com wrote:

Hi. I am on the north side of Brisbane.

[bacca5419]

Yeah just a tad. I guess I will work it out. Frustrating , but achievable. Thanks Gordon. Stay safe down there.

Sent from my iPad

On 10 Oct 2020, at 12:27 pm, Zymurgy42 notifications@github.com wrote:

A tad far from Melbourne.

On Sat, 10 Oct 2020 at 12:41, bacca5419 notifications@github.com wrote:

Hi. I am on the north side of Brisbane.

Sent from my iPhone

On 10 Oct 2020, at 9:36 am, Zymurgy42 notifications@github.com wrote:

 Where in Oz are you Noel?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/clough42/electronic-leadscrew/issues/83#issuecomment-706465089, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADD2HK3TJWO7Y7IBLL6AJELSJ63UDANCNFSM4QQDM4DA .

--

Gordon Newell — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[bacca5419]

That is for sure true. Im going to try some resoldering today. I guess it will either work or it wont. Fingers crossed. Cheers

Sent from my iPad

On 10 Oct 2020, at 12:40 pm, JonWoellhaf notifications@github.com wrote:

Yes, but not as far as from Utah, USA!

From: Zymurgy42 Sent: October 9, 2020 20:27 To: clough42/electronic-leadscrew Cc: JonWoellhaf ; Comment Subject: Re: [clough42/electronic-leadscrew] Launchpad programming (#83) A tad far from Melbourne.

On Sat, 10 Oct 2020 at 12:41, bacca5419 notifications@github.com wrote:

Hi. I am on the north side of Brisbane. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[bacca5419]

Right. I think I found the problem. New board that connects to the microcontroller. I found the gnd terminal on the board has nothing for the solder to stick to the board. Solder only sticks to the pin on the connmector block. I will order a new board from James ans start again. I will try attaching a photo here , but I think it wont allow me to attach. At the end of the day I figure I just stuffed the board when trying to solder. All other connections I did are great. Another seniors moment in the life of bacca5419.

Sent from my iPhone

On 10 Oct 2020, at 12:40 pm, bacca5419 bacca5419@yahoo.com.au wrote:

 Yeah just a tad. I guess I will work it out. Frustrating , but achievable. Thanks Gordon. Stay safe down there.

Sent from my iPad

On 10 Oct 2020, at 12:27 pm, Zymurgy42 notifications@github.com wrote:

A tad far from Melbourne.

On Sat, 10 Oct 2020 at 12:41, bacca5419 notifications@github.com wrote:

Hi. I am on the north side of Brisbane.

Sent from my iPhone

On 10 Oct 2020, at 9:36 am, Zymurgy42 notifications@github.com wrote:

 Where in Oz are you Noel?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/clough42/electronic-leadscrew/issues/83#issuecomment-706465089, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADD2HK3TJWO7Y7IBLL6AJELSJ63UDANCNFSM4QQDM4DA .

--

Gordon Newell — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[davidgleach]

Hi Noel That sounds like the problem I had! For what its it is worth here is a picture of my final working set up.

[bacca5419]

Nice looking setup. Well done.

Sent from my iPad

On 11 Oct 2020, at 6:43 pm, davidgleach notifications@github.com wrote:

Hi Noel That sounds like the problem I had! For what its it is worth here is a picture of my final working set up.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[clough42]

FYI, I just added a continuity testing section to the troubleshooting documentation. It has a map of most of the pin connections and test points on the board that can be used to verify continuity. After many messages back and forth, when it turned out it was a lifted pad, I figured it was worth documenting for others who might run into similar trouble.

https://github.com/clough42/electronic-leadscrew/wiki/Continuity-Checks

[bacca5419]

Thank you for this information. This is very useful for someone like me ( hopeless with electronics ). I have ordered new boards from james. When the boards arrive I am confident all will be good. Regards to all and I thank you all for the help you have given. I will keep you informed.

Sent from my iPhone

On 13 Oct 2020, at 9:03 am, clough42 notifications@github.com wrote:

 FYI, I just added a continuity testing section to the troubleshooting documentation. It has a map of most of the pin connections and test points on the board that can be used to verify continuity. After many messages back and forth, when it turned out it was a lifted pad, I figured it was worth documenting for others who might run into similar trouble.

https://github.com/clough42/electronic-leadscrew/wiki/Continuity-Checks

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

Excellent! Thanks, James.

Jan (Yan)

From: clough42 Sent: October 12, 2020 17:03 To: clough42/electronic-leadscrew Cc: JonWoellhaf ; Comment Subject: Re: [clough42/electronic-leadscrew] Launchpad programming (#83) FYI, I just added a continuity testing section to the troubleshooting documentation. It has a map of most of the pin connections and test points on the board that can be used to verify continuity. After many messages back and forth, when it turned out it was a lifted pad, I figured it was worth documenting for others who might run into similar trouble. https://github.com/clough42/electronic-leadscrew/wiki/Continuity-Checks

[carneeki]

Hi Noel,

I'm in Sydney if you need some hands on help, and I have a spare ELS board I can lend / swap until your replacements arrive if it's time critical.

[bacca5419]

Hi Adam. Thanks for the offer. I have a couple of boards on the way. Time isnt a problem. Im retired and the lathe is a hobby to help keep my motorcycles on the track. I probably will need help with loading James new update to studio suite. Im not that clever with computers. Regards. Noel.

Sent from my iPhone

On 18 Oct 2020, at 4:16 pm, Adam notifications@github.com wrote:

 Hi Noel,

I'm in Sydney if you need some hands on help, and I have a spare ELS board I can lend / swap until your replacements arrive if it's time critical.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[bacca5419]

Hi all once again. Well the latest news , the new boards arrived from James (clough42), which he kindly assembled for me. New control panels from China. I reloaded the code composser from texas instruments , loaded the latest firmware , tested the continuity as per instructions from James ( all tested perfect ) plugged the launchpad into my computer , configured everything and whala , still nothing. I am at a complete lose of what to try next.

Sent from my iPad

On 18 Oct 2020, at 4:16 pm, Adam notifications@github.com wrote:

Hi Noel,

I'm in Sydney if you need some hands on help, and I have a spare ELS board I can lend / swap until your replacements arrive if it's time critical.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[JonWoellhaf]

Hi, Noel.

What a bummer!

Please take advantage of Adam’s offer to help.

I am dying to know what the problem is! Have you tried stepping through the code?

Jan

From: bacca5419 Sent: October 23, 2020 00:08 To: clough42/electronic-leadscrew Cc: JonWoellhaf ; Comment Subject: Re: [clough42/electronic-leadscrew] Launchpad programming (#83)

Hi all once again. Well the latest news , the new boards arrived from James (clough42), which he kindly assembled for me. New control panels from China. I reloaded the code composser from texas instruments , loaded the latest firmware , tested the continuity as per instructions from James ( all tested perfect ) plugged the launchpad into my computer , configured everything and whala , still nothing. I am at a complete lose of what to try next.

Sent from my iPad

On 18 Oct 2020, at 4:16 pm, Adam notifications@github.com wrote:

Hi Noel,

I'm in Sydney if you need some hands on help, and I have a spare ELS board I can lend / swap until your replacements arrive if it's time critical.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.