Hi Randy,
A puzzle for you....
I am using my ISOPOD V1 for experiments or proof of concept...
I have a situation where there are odd things happening...
Things work as expected with the loaded code but when I shut the unit down for, lets say 30 minutes, the unit does not always behave as expected... It requires a second quick shut-down cycle of perhaps 15 seconds before it behaves properly... I am driving a couple of servo motors which do not folllow the comands until the second power-up. It occationally stops working with the misbaviour but is OK after a short off/on... Once it starts properly then is works without failure until I give up challenging it and shut down....
V1 talks ncely with an ISOPOD V2 through CAN which runs 8 filters...
This is most peculiar... Time for a ISOPOD V3?

Also, NMIterm freezes.... My laptop has no serial port so I use a couple of USB/Serial units. For whatever reason the NMITerms stops responding from time to time. Rather frustrating as I have to shut down the laptop (WindowsXPpro) when it happens... Never could find a solution for that. Some times I may have two NMI windows running as I experiment with two ISOPODs at the same time. In this configureation, One nay freeze while the other works...
THe USB drivers are, as far as I know, up to date...

Cheers,

Per.

The IsoPod(TM) has three versions now. V2 and V3 are nearly identical. The pinout differernce and slight form factor change occurfed between 1 and 2.

I'm wondering if you aren't describing a software difference. Are all the boards you are describing running the sma version of the IsoMax(TM)?

Finally, yes NMITerm sometimes hangs up, a purely PC side phenomina. I've noticed an action that often brings that lockup on. If you wiggle the USB dongle, and it looses power however breifly, the port gets lost to windows. When that happens, try re-establiching the properties (Files > Properties > Ok) (or menu button for Properties then Ok) and see if you don't recover communications.

Hi Randy.
Working Saturdays?
The PODs are all running the same latest Isomax version, 0.86.
I played with it this morning. Some startups causes what appears to be partial functioning. i.e. it the servo motor only turns in one direction or not at all.
A quick off/on return things to normal. So, for proper funtionality I some times need to do a double start up. Most peculiar as it stays fully functional after the second cycling...
As for V2 etc. I am designing a PCB as a host for the PODs etc. and plan to use v3 for that.
I mentioned the NMI Term simply as a feedback. The dongles do not move. It may be a driver problem but I am scratching my head. The program does not respond and does not terminate if left alone. I have gone the route of the task manger but I always have to shut down the computer. Oh well.

One added question. I will need to keep the value in a variable ( EEWORD) accessible for at startup. It is a simple 0 -1000 value for status. The named variable is of course available but what about its value?

Cheers,

Per

Saturday? Always working.

Have you tried reascerting the properties to the NMITerm when it happens? I'll be curious to see if that solves your problem. Usually by the time I suspect the NMITerm is what's locked up, I have already been beating on the 'Pod trying to get it to come back to life, getting desperate to get it going. I just close and re-open NMITerm, and see the 'Pod is alive, and feel great it isn't the 'Pod. Then I remember I should have tried to re-initialize the NMITerm properties. So I haven't caught it enough to be sure this is an every time cure. So additional feedback this is useful, or not, would be appreciated.


There are several variables having to do with startup. There's a user variable called CLD/WRM. Maybe it hasn't faded on a short power down, so the user area, etc., isn't reloaded, you only get a partial restore.

I have used the data flash to hold "variables" through power downs. Just remember it erases in pages. So it's pretty much a page per variable, or cluster of related variables.

Here's an example from my code

Hi Randy,
I have another puzzle for you...
Probably something you do not want on the forum...
On May 17th. I sent the first email regarding an error done with a shipment of my order which I still have not received. The invoice enclosed with the order stated just over $700 value for the two ISOPODS I had paid for... It resulted in a UPS brokerage and duty etc. COD charge of nearly $170... I did of course refuse the parcel. After some emails I got a question from Pam wondering if I would be willing to pay the $36 return charge and then the USPS postage for the originally requested shipping method. Hmm, I did not make the error causing the problem... I try to avoid UPS as the plague given their outrageous brokerage fees. As is was they would have charged me an additional $36 for a reassessment IF NMI faxed them a correct invoice... Yes, I did call UPS brokerage and the delivery was delayed 1 day before I finally refused it the next day.

I am not pleased with this by now to put it mildly. It has caused me a major headache and I was forced to do a rewire and embed my original V1 pod. Forget about the neat PCB for the V3 etc.

I am rather puzzled as the forum support has been excellent in contrast.
I no longer have an available unit to experiment with.

So, what is happening with this?

Per